Access requirements for platform resources are controlled by markings and organizations. Markings restrict access in an all-or-nothing fashion: to access a resource, a user must be a member of all markings applied to the resource. Additionally, markings are inherited through file hierarchies and direct dependencies. On the other hand, for organizations, users must be a member or guest member of at least one organization applied to a project to meet access requirements. Organizations are inherited via the file hierarchy and direct dependencies.
If you have the Remove marking
permission for a specific marking, you can now remove that inherited Marking from outputs in Pipeline Builder. This is equivalent to the stop_propagation
argument in Code Repositories.
Removing a marking on an output is equivalent to stopping the propagation of a marking from an input.
You must complete the following steps before you can remove markings or organizations using Pipeline Builder.
Navigate to the Security approvals tab and check the box next to Allow changes to security markings in this pipeline. You must have the Owner
role on the pipeline to complete this step.
Once you Allow changes to security markings in this pipeline, you cannot disable branch protection or remove code approval requirements. You must disable Allow changes to security markings in this pipeline to disable those features.
Once you remove a marking in a protected branch, you cannot disable the Allow changes to security markings in this pipeline from the Security approvals tab. You must undo the removal of the marking first to disable this setting.
Create a branch off of the protected branch.
Navigate to Pipeline outputs on the right side of your screen, and hover over the output with the markings(s) you want to remove. Then, select Edit.
The removed markings will now show up under the Markings removed section in the dialog.
Outputs inherit organizations from the project they are in. Move your output to a separate project if you need to remove an organization that is on the existing project.
The changes you applied to markings and organizations on outputs will not go into effect until the branch is merged successfully and deployed on the protected branch. If you try building the dataset on your branch, it will still show the original markings.
Organization removal only affects organizations that are present on the input at the time of the removal. If the organizations associated with the input have changed since your last removal, a warning icon will appear to indicate that the organizations for this input have been modified since the previous removal action.
You must have the Remove marking
permission to approve the change. Approvers for proposals to remove markings do not need to be pipeline owners and only require View
access to the proposal.
Every removed marking or organization will require a separate check, meaning that you could have multiple checks in one proposal. When you approve a marking removal, your approval will apply for every marking that you have permission to review.
Once all required approvals have been granted, the proposal is allowed to merge. Deploying that version will allow the marking removals to take effect.
To undo the removal of a marking, navigate to Pipeline outputs on the right side of your screen and hover over the output with the marking(s) you removed.
Select Edit.
Propose your changes to begin approval checks.
Once approved, deploy your pipeline.
Elevated permissions are not required to undo the removal of a marking, unlike the permissions required to remove a marking.
In a job group, markings from all inputs will be inherited by all outputs within the same job group. To view an example and learn more about job groups, review our documentation.
If there are marking removals on any branch, you must stop removing markings from all branches in the pipeline before protecting or unprotecting branches. When multiple branches are protected, marking removals will target all protected branches.
When security approval settings are enabled, you will not be able to change branch protection settings, including protecting or unprotecting branches.