Working on the postgresql charm a bit, and I'm wondering if there is a way to supply overrides for default values in a "juju-way".
In my charm that will be consuming the services provided by postgresql, I was thinking I could override things like the database name, or the name of the super_user created. If I stick something like this in the relation-joined:
I'm having an issue where the postgres/db-admin-relation-changed can actually run before the consumer joins runs (or finishes running at least).
Eventually, the postgresql/db-admin-relation-changed will run and get my data, but if it runs too quickly, I could wind up with 2 superusers.
TL;DR: Is there a way to guarantee that default configuration is overridden in a service on the provides side of the relationship?