-
Notifications
You must be signed in to change notification settings - Fork 109
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
wip: new(prow): pigeon integration #1020
base: master
Are you sure you want to change the base?
wip: new(prow): pigeon integration #1020
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: cappellinsamuele The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
f0f058c
to
225e790
Compare
225e790
to
1e5a729
Compare
f786c44
to
4c9b0e1
Compare
command: | ||
- pigeon | ||
args: | ||
- --dry-run |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Love this!!!
…h pigeon Signed-off-by: cappellinsamuele <[email protected]>
…t job. Fixed image name and added example configuration. Signed-off-by: cappellinsamuele <[email protected]>
…ironment variables. Signed-off-by: cappellinsamuele <[email protected]>
4c9b0e1
to
04bbf88
Compare
@jasondellaluce @maxgio92 @LucaGuerra this LGTM! What do you think? /hold |
Issues go stale after 90d of inactivity. Mark the issue as fresh with Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with Provide feedback via https://github.com/falcosecurity/community. /lifecycle stale |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. Mark the issue as fresh with Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with Provide feedback via https://github.com/falcosecurity/community. /lifecycle stale |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. Mark the issue as fresh with Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with Provide feedback via https://github.com/falcosecurity/community. /lifecycle stale |
/remove-lifecycle stale |
@cappellinsamuele: The following tests failed, say
Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. I understand the commands that are listed here. |
Issues go stale after 90d of inactivity. Mark the issue as fresh with Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with Provide feedback via https://github.com/falcosecurity/community. /lifecycle stale |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. Mark the issue as fresh with Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with Provide feedback via https://github.com/falcosecurity/community. /lifecycle stale |
/remove-lifecycle stale |
LGTM I think @FedeDP this can be integrated. @cappellinsamuele are there other points missing from the PR as it's marked as WIP? |
@maxgio92 There were no other points left open at the time the PR was last reviewed |
Issues go stale after 90d of inactivity. Mark the issue as fresh with Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with Provide feedback via https://github.com/falcosecurity/community. /lifecycle stale |
/remove-lifecycle stale |
This PR introduces a new prow job enable gitops that synchronize among repositories the organization's secrets and environment variables, mainly used by github actions.
This avoids the manual settings of secrets and variables through the github interface, improving traceability and transparency.