You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This will probably be more of an epic. This is a stream of conciousness
All operator-user configuration should be accessible via environment variables
BONNY_POD_NAMESPACE
BONNY_POD_SERVICE_ACCOUNT
Bonny.Config.labels
Bonny.Config.cluster_name
Devise a consistent naming pattern for configuration to separate operator author from operator user. eg group name is an author config, pod namespace is a user config
A few env vars are set that are metadata for the cluster, delineate those. (BONNY_POD_NAME, BONNY_POD_IP)
BONNY_POD_NAMESPACE is confusing, its controls the namespace bonny watches
"BONNY" shouldn't be something an end-user of an operator should be concerned with, support an env var prefix for each operator
Split Bonny.Config into ~Bonny.Config.EndUser and ~Bonny.Config.Author (names are hard)
Splitting may be as simple as all author config is compile time config, so do it via config/prod.exs and all user config is runtime, so use env vars.
The text was updated successfully, but these errors were encountered:
This will probably be more of an epic. This is a stream of conciousness
Splitting may be as simple as all author config is compile time config, so do it via config/prod.exs and all user config is runtime, so use env vars.
The text was updated successfully, but these errors were encountered: