Skip to content
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

Upgrade automate-postgresql service from PG version 9.6 to PG version 13 #6554

Open
vivekshankar1 opened this issue Jan 13, 2022 · 0 comments
Assignees
Labels
Team: S.H.I.E.L.D. This Label is used on S.H.I.E.L.D. Operations (Tasks / Stories)

Comments

@vivekshankar1
Copy link
Collaborator

vivekshankar1 commented Jan 13, 2022

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

  • 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.
@vivekshankar1 vivekshankar1 added the Team: S.H.I.E.L.D. This Label is used on S.H.I.E.L.D. Operations (Tasks / Stories) label Jan 13, 2022
@vivekshankar1 vivekshankar1 self-assigned this Jan 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team: S.H.I.E.L.D. This Label is used on S.H.I.E.L.D. Operations (Tasks / Stories)
Projects
None yet
Development

No branches or pull requests

1 participant