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

Renames examples rolebinding & clusterrolebinding #1210

Merged
merged 1 commit into from
Aug 31, 2021

Conversation

sm43
Copy link
Member

@sm43 sm43 commented Aug 30, 2021

As now we package roles required for eventlistener with release yaml
the references in examples/rbac.yaml has been updated with new
clusterroles.
But if a user has already applied older rbac on the cluster and then
try to install from upstream/main it would fail as the references
are changed.
So, this renames the binding names so that user doesn't face any issue
with the upcoming releases.

Ref. #1184

Signed-off-by: Shivam Mukhade [email protected]

Submitter Checklist

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

  • Includes tests (if functionality changed/added)
  • Includes docs (if user facing)
  • Commit messages follow commit message best practices
  • Release notes block has been filled in or deleted (only if no user facing changes)

See the contribution guide for more details.

Release Notes

@tekton-robot tekton-robot added the release-note Denotes a PR that will be considered when it comes time to generate release notes. label Aug 30, 2021
@tekton-robot tekton-robot requested review from dibyom and khrm August 30, 2021 17:37
@tekton-robot tekton-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Aug 30, 2021
As now we package roles required for eventlistener with release yaml
the references in examples/rbac.yaml has been updated with new
clusterroles.
But if a user has already applied older rbac on the cluster and then
try to install from upstream/main it would fail as the references
are changed.
So, this renames the binding names so that user doesn't face any issue
with the upcoming releases.

Signed-off-by: Shivam Mukhade <[email protected]>
@sm43 sm43 force-pushed the rename-bindings branch from 16e07af to 611aa59 Compare August 30, 2021 17:44
Copy link
Contributor

@savitaashture savitaashture 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 Aug 31, 2021
@tekton-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: savitaashture

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 Aug 31, 2021
@tekton-robot tekton-robot merged commit ef99bbd into tektoncd:main Aug 31, 2021
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. lgtm Indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. 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.

3 participants