-
Notifications
You must be signed in to change notification settings - Fork 12
Refactor pgstacbootstrap job and ConfigMaps to use Helm hooks for execution order #207
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.
Comments suppressed due to low confidence (2)
helm-chart/eoapi/templates/pgstacboostrap/job.yaml:16
- [nitpick] There is an inconsistency between the folder name 'pgstacboostrap' and the job name 'pgstacbootstrap'. Consider renaming the folder to 'pgstacbootstrap' for consistency.
name: pgstacbootstrap
.github/workflows/helm-tests.yml:181
- [nitpick] The log extraction command uses 'svc/vector', which deviates from the naming pattern seen elsewhere (e.g., using the release name). Verify whether this is intentional or if it should align with the other service naming conventions.
pytest .github/workflows/tests/test_vector.py || kubectl logs svc/vector
sunu
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! thanks @emmanuelmathot!
pantierra
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very nice!
Implement Helm hooks to manage the execution order of the pgstacbootstrap job and its ConfigMaps, eliminating the need for initContainers in the deployment. This change ensures proper initialization of the PostgreSQL database during installation and upgrades.
related issues: #203, #206