Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add comment linking configmap names in deployments to names in role #2400

Merged
merged 1 commit into from Apr 16, 2020
Merged

Add comment linking configmap names in deployments to names in role #2400

merged 1 commit into from Apr 16, 2020

Conversation

ghost
Copy link

@ghost ghost commented Apr 15, 2020

Changes

If a user wants to change the names of the configmaps that Tekton's
controller and webhook use then they'll also need to update the
Roles associated with those deployments. The Roles explicitly name
the ConfigMaps that these deployments can access.

This PR just adds a comment to help remind people that if they're
changing the ConfigMap names they'll need to also update the Roles.

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

See the contribution guide for more details.

Double check this list of stuff that's easy to miss:

Reviewer Notes

If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.

If a user wants to change the names of the configmaps that Tekton's
controller and webhook use then they'll also need to update the
Roles associated with those deployments. The Roles explicitly name
the ConfigMaps that these deployments can access.

This PR just adds a comment to help remind people that if they're
changing the ConfigMap names they'll need to also update the Roles.
@googlebot googlebot added the cla: yes Trying to make the CLA bot happy with ppl from different companies work on one commit label Apr 15, 2020
@tekton-robot tekton-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Apr 15, 2020
@ghost
Copy link
Author

ghost commented Apr 15, 2020

Originally mentioned here: #2346 (comment)

Copy link
Member

@vdemeester vdemeester left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Apr 15, 2020
@tekton-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vdemeester

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 15, 2020
@dibyom
Copy link
Member

dibyom commented Apr 15, 2020

/lgtm

/test pull-tekton-pipeline-integration-tests

@vdemeester
Copy link
Member

/test pull-tekton-pipeline-integration-tests

@tekton-robot tekton-robot merged commit 7cb3f48 into tektoncd:master Apr 16, 2020
@afrittoli afrittoli added the kind/documentation Categorizes issue or PR as related to documentation. label Apr 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cla: yes Trying to make the CLA bot happy with ppl from different companies work on one commit kind/documentation Categorizes issue or PR as related to documentation. lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants