Docs change: Limit CI/CD job token disabled by default
What does this MR do and why?
Describe in detail what your merge request does and why.
Aligns the documentation for Limit GitLab CI/CD Job Token Access with the current functionality.
I have checked that the structure.sql schema for GitLab sets the default value of project_ci_cd_settings.job_token_scope_enabled
to false
. This was as a result of the database migration to change the default value to false
. This was part of the following Merge Request: !69502 (merged). There is some context in the Merge Request that outlines the justification for changing the value back to false by default.
There is an open issue to Enable job token scope by default for new projects in the future.
Screenshots or screen recordings
These are strongly recommended to assist reviewers and reduce the time to merge your change.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.