Print a deprecation notice for postgres upgrades if <11
Closes #5095 (closed).
Merge request reports
Activity
changed milestone to %12.10
added deprecation devopssystems groupdistribution labels
1 Warning You’ve made some changes in the cookbooks, but didn’t add any tests.
That’s OK as long as you’re refactoring existing code,
but please consider adding the ~backstage label in that case.1 Message Please leave the merge request unassigned. Merge requests are handled according to the workflow documented in our handbook and should receive a response within the limit documented in our First-response SLO.
If you don’t receive a response, please mention
@gitlab-org/distribution
, or one of our Project MaintainersGenerated by
DangerEdited by 🤖 GitLab Bot 🤖added backstage [DEPRECATED] label
mentioned in issue #5095 (closed)
added workflowready for review label
- Resolved by DJ Mountney
- Resolved by DJ Mountney
- Resolved by DJ Mountney
@dustinmm80 I believe the issue wants us to also emit a warning if user had skipped pg upgrade - https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/files/gitlab-ctl-commands/upgrade.rb#L68
- Resolved by DJ Mountney
@dustinmm80 Few comments/questions. Back to you.
removed workflowready for review label
added 1 commit
- 799a9bd9 - move deprecation notice to correct command, factor out to common function
added 1 commit
- 45701847 - Add a warning when skipping pg upgrade and pg version < 11
assigned to @balasankarc and unassigned @dustinmm80