Repository navigation
[Feature]: allow adding to podman secret postgres_multiple_databases #70
Description
Describe the feature
he OpenCHAMI bootstrap script /usr/libexec/openchami/bootstrap_openchami.sh is usually executed only once, at the time of the package installation.
Since it is idempotent, re-running it would not hurt. Where the script creates podman secrets, it checks before if a secret with that name already exists, and if so, skips the creation of a new secret.
When adding microservices like PCS to an existing setup, it is reasonable to re-use the bootstrap script by adding content there and re-running it. This ensures uniformity of implementation, makes use of the sanity checks that already exist in the script, and keeps everything in one places, which makes the system easier to debug.
However, when the content of the variable "POSTGRES_MULTIPLE_DATABASES" is extended with new information, the corresponding podman secret "postgres_multiple_databases" will not reflect this change: Since it already exists, its creation will be skipped and the additional content of "POSTGRES_MULTIPLE_DATABASES" not added there.
Why do you want this feature?
Simplifies adding new microservices to existing installation by using the standardized way.
Alternatives you've considered
The alternative would be to add this function in the bootstrap script on the local system. This would open up possible issues with updates.
Additional context
No response
Code of Conduct
- I agree to follow this project's Code of Conduct
Activity
darkmatterdawn commentedon Aug 13, 2026
The pragmatic solution is: in each run of the bootstrap script, check if the podman secret "postgres_multiple_databases" exists already. If so, delete it so it can be recreated. Since it's just a string of other secrets, this does not affect the content of existing secrets, but may add a new one - which is a desired change.
The podman secret ID will change each time. But since OpenCHAMI quadlets reference podman secrets by their name, this is not an issue.