-
Notifications
You must be signed in to change notification settings - Fork 677
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
REQUEST: Need PullRequests
and Contents
write permissions for GITHUB_TOKEN
in CAPA GitHub workflows
#3562
Comments
Thanks for opening the PR @zeborg In summary, we want a github action to create a PR whenever a new Kubernetes release is out. We'd like to understand if at the organizational level @ameukam @palnabarun (as you commented on this in the previous meeting), do you know who could check the permissions at the kubernetes sigs level? |
I would recommend to create a new token from a pot (k8s-infra-ci-robot ?) and add it as secret for usage the kubernetes infrastructure. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
This request is still valid so: /remove-lifecycle stale |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
@ameukam - how would we go about doing that? |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
/remove-lifecycle rotten |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /close not-planned |
@k8s-triage-robot: Closing this issue, marking it as "Not Planned". In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/reopen |
@richardcase: Reopened this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/remove-lifecycle rotten |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle rotten |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
/remove-lifecycle rotten |
The kubernetes-sigs/cluster-api-provider-aws repository requires
PullRequests
andContents
write permissions forGITHUB_TOKEN
within the ami_periodic.yaml GitHub workflow that we've tested as being fully functional on my fork. We tried to manually elevate these permissions in an earlier version of this action here, but theGITHUB_TOKEN
secret would only reflect withread
permissions despite providing thepull-requests: write
andcontents: write
declarations in the workflow.The PR creation is currently being automated in my fork using a 3rd party GitHub application that I created in order to overcome this GitHub workflow restriction on the target repository, but ideally we would like to refrain from maintaining a custom GitHub application and would instead prefer to utilize
GITHUB_TOKEN
wherever possible.Following up on the discussion held in the GitHub Administration meeting held on 7th July 2022, we'd like to keep using GitHub actions for this purpose instead of Prow, at least for now, due to the following concerns:
image-builder
environment variables using a custom config file within the repository itselfRef: proposal: CAPA AMI GitHub Action
/cc @sedefsavas @richardcase @ameukam
The text was updated successfully, but these errors were encountered: