Document Amazon Aurora incompatibility
What does this MR do?
Adds notes about the incompatibility of Amazon Aurora to our Reference Architectures.
Related issues
- Database load balancing does not work with a AW... (#220617 - closed)
- Research and evaluate database migration from A... (#342093 - closed)
Author's checklist
-
Optional. Consider taking the GitLab Technical Writing Fundamentals course. -
Follow the: -
If you're adding or changing the main heading of the page (H1), ensure that the product tier badge is added. -
If you are a GitLab team member, request a review based on: - The documentation page's metadata.
- The associated Technical Writer.
Reviewer's checklist
Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.
-
If the content requires it, ensure the information is reviewed by a subject matter expert. - Technical writer review items:
-
Ensure docs metadata is present and up-to-date. -
Ensure the appropriate labels are added to this MR. -
Ensure a release milestone is set. - If relevant to this MR, ensure content topic type principles are in use, including:
-
The headings should be something you'd do a Google search for. Instead of Default behavior
, say something likeDefault behavior when you close an issue
. -
The headings (other than the page title) should be active. Instead of Configuring GDK
, say something likeConfigure GDK
. -
Any task steps should be written as a numbered list. - If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
-
-
-
Review by assigned maintainer, who can always request/require the reviews above. Maintainer's review can occur before or after a technical writer review.
Merge request reports
Activity
changed milestone to %15.2
assigned to @mattkasa
Suggested Reviewers (beta)
The individuals below may be good candidates to participate in the review based on various factors.
You can use slash commands in comments to quickly assign
/assign_reviewer @user1
.Suggested Reviewers @marcel.amirault
,@cnorris
,@aqualls
,@axil
,@gitlab-bot
If you do not believe these suggestions are useful, please apply the label Bad Suggested Reviewer. You can also provide feedback for this feature on this issue:
https://gitlab.com/gitlab-org/gitlab/-/issues/357923
.Automatically generated by Suggested Reviewers Bot - an experimental ML-based recommendation engine created by ~"group::applied ml".
- Resolved by Fiona Neill
@alexives Could you please review as a subject matter expert?
@claytoncornell Could you please review for Technical Writing?
requested review from @alexives and @claytoncornell
1 Message This merge request adds or changes documentation files. A review from the Technical Writing team before you merge is recommended. Reviews can happen after you merge. Documentation review
The following files require a review from a technical writer:
doc/administration/reference_architectures/10k_users.md
doc/administration/reference_architectures/1k_users.md
doc/administration/reference_architectures/25k_users.md
doc/administration/reference_architectures/2k_users.md
doc/administration/reference_architectures/3k_users.md
doc/administration/reference_architectures/50k_users.md
doc/administration/reference_architectures/5k_users.md
doc/administration/reference_architectures/index.md
The review does not need to block merging this merge request. See the:
-
Metadata for the
*.md
files that you've changed. The first few lines of each*.md
file identify the stage and group most closely associated with your docs change. - The Technical Writer assigned for that stage and group.
- Documentation workflows for information on when to assign a merge request for review.
If needed, you can retry the
danger-review
job that generated this comment.Generated by
Dangermentioned in issue #342093 (closed)
requested review from @fneill
- Resolved by Matt Kasa
- Resolved by Matt Kasa
- Resolved by Matt Kasa
- Resolved by Matt Kasa
- Resolved by Matt Kasa
- Resolved by Matt Kasa
- Resolved by Matt Kasa
- Resolved by Matt Kasa
- Resolved by Matt Kasa
- Resolved by Matt Kasa
- Resolved by Matt Kasa
- Resolved by Matt Kasa
- Resolved by Matt Kasa
- Resolved by Matt Kasa
- Resolved by Matt Kasa
- Resolved by Matt Kasa
- Resolved by Matt Kasa
- Resolved by Matt Kasa
- Resolved by Matt Kasa
- Resolved by Matt Kasa
removed review request for @claytoncornell
added 402 commits
-
3ffc4e1e...2151d82a - 401 commits from branch
master
- a7b7991e - Document Amazon Aurora incompatibility
-
3ffc4e1e...2151d82a - 401 commits from branch
enabled an automatic merge when the pipeline for 973e0090 succeeds
mentioned in commit ebcf4c18
added workflowstaging-canary label and removed workflowin dev label
added workflowcanary label and removed workflowstaging-canary label
added workflowstaging label and removed workflowcanary label
added workflowproduction label and removed workflowstaging label
added workflowpost-deploy-db-staging label and removed workflowproduction label
added workflowpost-deploy-db-production label and removed workflowpost-deploy-db-staging label
added releasedcandidate label
added releasedpublished label and removed releasedcandidate label
added groupdatabase frameworks label and removed groupdatabase [DEPRECATED] label