Integrate config.yaml into Provider and Extensions state management

Open lily-de opened this issue 11 months ago • 1 comments

With the move to config.yaml as a general source of truth, we need to redo the UI's state management to use these new endpoints that expose read/write operations to config.yaml

Feb 22 '25 20:02 lily-de

env (zshrc) config.yaml keychain

secrets / other secrets / other secrets only

priority=1 priority=2 priority=2

read only read/write/delete read/write/delete

edited directly by user updated via CLI, UI, and by user updated by CLI and UI

env (zshrc)	config.yaml	keychain
secrets / other	secrets / other	secrets only
priority=1	priority=2	priority=2
read only	read/write/delete	read/write/delete
edited directly by user	updated via CLI, UI, and by user	updated by CLI and UI

Feb 23 '25 18:02 lily-de