pgod.toml was envisioned to be manual edited (or generated), but not to be twiddled with from within a container.
should we allow an pgoctl endpoint to CRUD those environment values or just outsource to an external method? The latter is the current idea for pgo - have a user facing website where you can configure things, but there is some value of doing it from pgoctl.
downsides: need to pull envs out and into something that is easily updated by a program; should also have history pref,.
sounds like a lot of work and refactoring for not much gain?
miekg
commented
5 months ago
pgod.toml was envisioned to be manual edited (or generated), but not to be twiddled with from within a container.
should we allow an pgoctl endpoint to CRUD those environment values or just outsource to an external method? The latter is the current idea for pgo - have a user facing website where you can configure things, but there is some value of doing it from pgoctl.
downsides: need to pull envs out and into something that is easily updated by a program; should also have history pref,.
sounds like a lot of work and refactoring for not much gain?