Container Registry: add metadata database beta section
What does this MR do?
This MR adds a section describing the container registry metadata database beta feature, as described in the Container Registry Self-Managed Database Rollout Architecture Blueprint.
Related issues
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.
If you are a GitLab team member and only adding documentation, do not add any of the following labels:
~"frontend"
~"backend"
~"type::bug"
~"database"
These labels cause the MR to be added to code verification QA issues.
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 you aren't sure which tech writer to ask, use roulette or ask in the #docs Slack channel.
-
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 %16.4
added docsimprovement documentation maintenancerefactor typemaintenance labels
assigned to @hswimelar
3 Warnings c17df1df: The commit subject must start with a capital letter. For more information, take a look at our Commit message guidelines. 023de317: The commit subject must contain at least 3 words. For more information, take a look at our Commit message guidelines. 023de317: The commit subject must start with a capital letter. For more information, take a look at our Commit message guidelines. 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/packages/container_registry.md
(Link to current live version)
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
Danger-
added docs-only label
added headway-self-managed-registry-db label
- Resolved by Hayley Swimelar
- Resolved by Marcel Amirault
@trizzi could you take a look at this and see what you think? We'll likely expand on this in the near future, but this should be the basic scaffolding that we use going forward.
Setting label groupcontainer registry based on
@hswimelar
's group.added groupcontainer registry label
mentioned in merge request !130090 (closed)
Setting label(s) devopspackage sectionci based on groupcontainer registry.
added devopspackage sectionci labels
- Resolved by Hayley Swimelar
- Resolved by Hayley Swimelar
- Resolved by Hayley Swimelar
- Resolved by Hayley Swimelar
- Resolved by Marcel Amirault
@marcel.amirault could you please give this a review?
requested review from @marcel.amirault
- Resolved by Hayley Swimelar
- Resolved by Hayley Swimelar
- Resolved by Hayley Swimelar
- Resolved by Hayley Swimelar
- Resolved by Hayley Swimelar
- Resolved by Hayley Swimelar
- Resolved by Hayley Swimelar
- Resolved by Hayley Swimelar
- Resolved by Hayley Swimelar
- Resolved by Hayley Swimelar
added Technical Writing label
removed review request for @marcel.amirault
added 1 commit
- c17df1df - move known limitations and instructions sections
@marcel.amirault great suggestions, thank you!!
requested review from @marcel.amirault
- Resolved by Hayley Swimelar
- Resolved by Hayley Swimelar
- Resolved by Hayley Swimelar
- Resolved by Hayley Swimelar
removed review request for @marcel.amirault
mentioned in epic &5521
requested review from @marcel.amirault
- Resolved by Marcel Amirault
@hswimelar OK, thanks a lot, LGTM!
enabled an automatic merge when the pipeline for 432f27f7 succeeds
mentioned in commit eede54a5
added workflowstaging-canary 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 Category:Container Registry label
mentioned in merge request !131572 (merged)
added releasedcandidate label
added releasedpublished label and removed releasedcandidate label
mentioned in epic gitlab-org#5521