[bitnami/postgresql-repmgr] Support running scripts on primary node when container starts #70737
Conversation
Change sql-mysql.sh script to use default moodle environment variables to connect to database bitnami#68054 Signed-off-by: Thomas Lønskov Luther <rasmussen.thomas@gmail.com>
Signed-off-by: Thomas Lønskov Luther <rasmussen.thomas@gmail.com>
…is started (bitnami#70606) Signed-off-by: Thomas Lønskov Luther <rasmussen.thomas@gmail.com>
|
Thank you for initiating this pull request. We appreciate your effort. Just a friendly reminder that it's important to sign your commits. Adding your signature certifies that you either authored the patch or have the necessary rights to contribute the changes. You can find detailed information on how to do this in the “Sign your work” section of our contributing guidelines. Feel free to reach out if you have any questions or need assistance with the signing process. |
|
@carrodher hmm... don't know why the other commits got to be a part of this PR :-( Apparently I mistankenly merged in another branch into this one... is it possible for me to remove these commits? |
|
Hi, It seems the PR is including changes for Moodle, which I believe they are not expected. Could you check it? |
javsalgar
changed the title
…is started (bitnami#70606) Signed-off-by: Thomas Lønskov Luther <rasmussen.thomas@gmail.com>
…is started (bitnami#70606) Signed-off-by: Thomas Lønskov Luther <rasmussen.thomas@gmail.com>
…smussen/bitnami-containers into feature/postgres-repmgr_scripts
…smussen/bitnami-containers into feature/postgres-repmgr_scripts
|
This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution. |
|
Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary. |
bitnami-bot
added
stale
Description of the change
This PR will add support for putting scripts in /docker-entrypoint-startdb.d/ and have these executed every time the container starts (limited to the PRIMARY node). Works the same way that /docker-entrypoint-initdb.d however this is limited to only running when database is initialized.
Benefits
Run validationscripts or other generic scripts every time the database container starts
Possible drawbacks
If scripts are not idempotent then this may impact the database.
Applicable issues
Additional information