Skip to content

postgresql 13 to 16 in readme and docker yml#4628

Draft
james-at-kc wants to merge 1 commit intomasterfrom
ftr/dev-14479-postgresql-16
Draft

postgresql 13 to 16 in readme and docker yml#4628
james-at-kc wants to merge 1 commit intomasterfrom
ftr/dev-14479-postgresql-16

Conversation

@james-at-kc
Copy link
Copy Markdown

Description:

Upgrading postgreSQL from 13.x to 16

Technical Details:

Required due to db restore using PG version 16

Requirements for PR Merge:

  1. Unit & integration tests updated
  2. API documentation updated (examples listed below)
    1. API Contracts
    2. API UI
    3. Comments
  3. Data validation completed (examples listed below)
    1. Does this work well with the current frontend? Or is the frontend aware of a needed change?
    2. Is performance impacted in the changes (e.g., API, pipeline, downloads, etc.)?
    3. Is the expected data returned with the expected format?
  4. Appropriate Operations ticket(s) created
  5. Jira Ticket(s)
    1. DEV-0

Explain N/A in above checklist:

@aguest-kc
Copy link
Copy Markdown
Contributor

I'm not sure if anyone went over our PR flow. For normal tickets, like this one, you should base your branch off of qat and then open the PR into qat. Hotfixes are based off of the staging branch and go into staging first.

I just wanted to mention that, because this PR is open into master.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants