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.

Sign up for GitHub

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

Jump to bottom

Replace argo-workflows with hera #1219

Open
fridex opened this issue Jan 19, 2022 · 7 comments
Open

Replace argo-workflows with hera #1219

fridex opened this issue Jan 19, 2022 · 7 comments
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/devsecops Categorizes an issue or PR as relevant to SIG DevSecOps.

Comments

@fridex
Copy link
Contributor

fridex commented Jan 19, 2022

Is your feature request related to a problem? Please describe.

See https://www.dynotx.com/hera-the-missing-argo-workflows-python-sdk/

We should stop using argo-workflows that are now archived and use hera instead.
@fridex fridex added the kind/feature Categorizes issue or PR as related to a new feature. label Jan 19, 2022
@goern
Copy link
Member

goern commented Jan 20, 2022

/priority important-soon
/help

@sesheta
Copy link
Member

sesheta commented Jan 20, 2022

@goern:
This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/priority important-soon
/help

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.

@sesheta sesheta added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. labels Jan 20, 2022
@fridex fridex mentioned this issue Feb 7, 2022
Closed
2 tasks
@sesheta
Copy link
Member

sesheta commented Apr 20, 2022

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 20, 2022
@codificat
Copy link
Member

/remove-lifecycle stale
/sig devsecops

@sesheta sesheta added sig/devsecops Categorizes an issue or PR as relevant to SIG DevSecOps. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels May 18, 2022
@sesheta
Copy link
Member

sesheta commented Aug 16, 2022

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 16, 2022
@sesheta
Copy link
Member

sesheta commented Sep 15, 2022

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

@sesheta sesheta added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Sep 15, 2022
@harshad16
Copy link
Member

/remove-lifecycle rotten
/lifecycle frozen

@sesheta sesheta added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels Oct 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/devsecops Categorizes an issue or PR as relevant to SIG DevSecOps.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@goern @codificat @fridex @harshad16 @sesheta