Add missing regionendpoint documentation.
What does this MR do?
Add missing regionendpoint
documentation.
Related issues
Closes #57718 (closed)
Author's checklist
-
Apply the correct labels and milestone -
Crosslink the document from the higher-level index -
Crosslink the document from other subject-related docs -
Feature moving tiers? Make sure the change is also reflected in features.yml
-
Correctly apply the product badges and tiers -
Port the MR to EE (or backport from CE): always recommended, required when the ee-compat-check
job fails
Review checklist
-
Your team's review (required) -
PM's review (recommended, but not a blocker) -
Technical writer's review (required) -
Merge the EE-MR first, CE-MR afterwards
Merge request reports
Activity
added Community contribution label
added documentation + 1 deleted label
added Category:Container Registry label
cc/ @axil @joshlambert
assigned to @WarheadsSE
@WarheadsSE can you confirm?
@joshlambert We're spot on here.
For others' reference: charts/gitlab's
storage
block documentation and s3 storage driver documentation@lorac My only concern here is that this is not a required setting, and we should note that clearly. This is only required with S3 when chosen to do so, and when using S3-compatible APIs like Minio.
added 136 commits
-
9add6863...45927684 - 135 commits from branch
gitlab-org:master
- ac76d353 - add missing regionendpoint documentation.
-
9add6863...45927684 - 135 commits from branch
@WarheadsSE I pushed the new changes. If you want to change the sentence syntax go ahead.
- Resolved by Evan Read
added 1 commit
- ac918c2c - Apply suggestion to doc/administration/container_registry.md
mentioned in issue #61091 (closed)
@WarheadsSE @joshlambert, not sure if you had a chance to review the latest?
@rpaik I believe I can speak for @joshlambert here when I say that we're sorry this slipped through our fingers.
I will review once more.
assigned to @WarheadsSE
cc @eread
assigned to @eread
- Resolved by Evan Read
Thanks @WarheadsSE. Questions:
- The note is only relevant to omnibus installations or no? The docs imply the source installs get autogenerated configuration. I'm wondering if the note applies to both install types.
- The omnibus installation steps only give S3 driver config, and this would look different if using a different driver? Given the steps supplied are only for the S3 driver (by the looks of it), couldn't one assume an S3 compatible service is in play and not have the note at all?
Edited by Evan Read
assigned to @WarheadsSE
assigned to @eread
mentioned in commit 49607217
changed milestone to %11.11
mentioned in merge request !27928 (merged)
mentioned in issue gitlab-org/release/tasks#778 (closed)