Feature request: Expanded config view for instances

[vosdev]

Heyhey,

I make a lot of use of profiles. It's the proper way to work with LXD. Unfortunately I do not see some of my profile's config on my instances in the UI because not all options have a UI option. I have to resort back to the cli to see this. Also it's very nice to see the full config in a single view.

On the cli you would issue lxc config show microk8s -e to obtain the full config of an instance, this is including all the config inherited from profiles.

I would like to request this feature also made possible in the UI.

Version 0.13 has a toggle switch at the bottom to show the YAML editor. Perhaps the YAML Configuration option can be put back to the config menu and a toggle switch at the bottom show us the full expanded config of an instance.

[edlerd]

Hello and thanks for the request. Please help me understand the user need a bit better. I understood you want to find out the active instance configuration, including values inherited from profiles. Do I understand that correct, or is it about something else?

If yes, I would say we should add any missing and relevant config values to the UI. Because there, we already solve the resolution of profile inherited values generically. And I think the display of that works pretty well. Which config keys are you looking for and can't access? The boot.* ones from #994? Or are there others that are missing as well?

I am hesitant to add two code editors. It might be an option in the YAML view to add an option that allows switching between the editable config and the applied/inherited config. But any way I can imagine this -- two editors or one editor with switch -- sounds UX wise confusing. Maybe adding the configuration values directly to the UI is the better option after all.

[vosdev]

It might be an option in the YAML view to add an option that allows switching between the editable config and the applied/inherited config.

I think that would be lovely. The GUI is very nice but I personally do miss the simplicity of a yaml view from time to time. Almost all my instance config comes from profiles (As it should be, right?) meaning the current implementation isn't useful in that perspective.

But any way I can imagine this -- two editors or one editor with switch -- sounds UX wise confusing.

I will leave that up to you :)