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
As an Automate developer, I want to upgrade automate-postgresql service which currently uses PG version 9.6 to PG version 13. This work as a part of the PG upgrade epic. These upgrade changes will be merged into a feature branch. Since the same service is upgraded, we need to take care that the older PG version 9.6's data does not get lost during the upgrade.
Acceptance Criteria
automate-postgresql should now be running successfully with PG version 13
Older data should be retained and new PG 13 should initialise using a different data directory
chef-automate dev psql commands should now be able to connect to PG version 13
The chef-automate default configs should now be using the PG 13 configs
All services should be working fine
All pipelines must be green
Implementation Details
Make changes to plan.sh file in automate-postgresql to now use PG version 13
Make changes to the configuration templates inside automate-postgresql service so that the Pg 13 config changes are accommodated.
Make changes to the config protobuffs so that the required PG 13 configuration is accommodated
Change the data directory used in Pg initialisation from pgdata to pgdata13. This is needed to retain the older data.
Changes to init config flow for showing the default configs
Testing if all clients and functionalities are working fine with new version of PG.
Definition of Done
All things specified in User Story Acceptance Criteria should be fulfilled.
All Exceptions are Handled Properly
Ensure logs have no unnecessary data.
Test coverage for the new feature is done to at least 70%
If needed raise Docs PR and tag documentation.
Swagger Documentation updated
Smoke Test done.
Ensure Build and Integration Pipelines are Green.
PR has 2 approvers.
All Code Review Comments are Resolved.
README doc should be updated, if needed.
The text was updated successfully, but these errors were encountered:
User Story
As an Automate developer, I want to upgrade automate-postgresql service which currently uses PG version 9.6 to PG version 13. This work as a part of the PG upgrade epic. These upgrade changes will be merged into a feature branch. Since the same service is upgraded, we need to take care that the older PG version 9.6's data does not get lost during the upgrade.
Acceptance Criteria
Implementation Details
Definition of Done
The text was updated successfully, but these errors were encountered: