Configuration Management

[reluctantfuturist]

🚀 Describe the new functionality needed

• A 'sealing concept' to not allow reconfiguring of a setup via API endpoint (like the available tools)
• Allowing to disable any dynamic reconfiguration during runtime, keeping the 'source of truth' in the configuration files (this is important for GitOps-like automation for easy reproducability/recovery).
• Self-contained provider configuration for allowing flexibility for the storage location on the local filesystem.

💡 Why is this needed? What if we don't build it?

Needed for enterprise deployment reliability

Other thoughts

No response

[cdoern]

I have a similar issue here #993 and an RFC here #1359 I think these seem related? If so, I'd be happy to work on this!

[cdoern]

This seems like it overlaps with the above issues but is more "static", regardless -- I'd be happy to to collaborate or work on this

[nathan-weinberg]

@reluctantfuturist any thoughts on the above?

[github-actions]

This issue has been automatically marked as stale because it has not had activity within 60 days. It will be automatically closed if no further activity occurs within 30 days.