Draft: Enable GitLab pages access control by default
What does this MR do?
Enable GitLab pages access control by default
Any reason not to enable it? Possibly gitlab#230584 (closed)?
As of 14.1 chroot
is disabled by default which I believe was the blocker.
After:
-
Update https://docs.gitlab.com/ee/administration/pages/index.html#access-control to state when set to enabled by default
Related issues
Checklist
See Definition of done.
For anything in this list which will not be completed, please provide a reason in the MR discussion
Required
-
Merge Request Title, and Description are up to date, accurate, and descriptive -
MR targeting the appropriate branch -
MR has a green pipeline on GitLab.com -
Pipeline is green on dev.gitlab.org if the change is touching anything besides documentation or internal cookbooks -
trigger-package
has a green pipeline running against latest commit
Expected (please provide an explanation if not completing)
-
Test plan indicating conditions for success has been posted and passes -
Documentation created/updated -
Tests added -
Integration tests added to GitLab QA -
Equivalent MR/issue for the GitLab Chart opened
Edited by Ben Bodenmiller