George

Thanks for the suggestion @piclemx ! My main concern here is that this can lead to confusion if you e.g. miss-spell or miss-reference a flag by mistake. This could easily...

This is a bit of a fiddly one. Definitely shines a light on a subtle bit of the evaluator that needs some thought. I don't think anything is necessarily broken...

This is a great idea! Makes sense from the security perspective. There is always mechanisms like CODEOWNERS in GitHub, but its a bit of a blunt instrument for this kind...

Something like the following could also be preferable: https://github.com/solo-io/wasm/blob/master/spec/spec-compat.md This is the solo.io WASM format, that is compatible with docker build and push. That would make the tooling a lot...

This is a great shout @thepabloaguilar 🙌 I spoke to someone in person a year back who suggested something like this. So this is extra validating! It touches a handful...

@thepabloaguilar all yours for the taking dude 🚀

💯 we already extensively used custom decoder hooks. So it could be added here: https://github.com/flipt-io/flipt/blob/19a5acc55ad771fb6e906423f0541c33a7f5b0b6/internal/config/config.go#L21-L30 It could likely be implemented as one that maps from string to string.

Thanks for raising this @piclemx this is more validation that folks want the UI and writes to the declarative backends. I guess it could be argued this is a duplicate...

@piclemx thanks for the feedback! Agreed that a new management API is desireable. In general we have some limitations with the current mutating APIs that impede some future feature goals....

When you say Operator, are you thinking K8s operator / controller / CRD? One thing we could do r.e. k8s operator is simply drop the database / object store components...