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

investigate on integrating the thamos advise task into DevSecOps procedure #100

Open
harshad16 opened this issue Mar 22, 2021 · 4 comments
Labels
kind/demo This is an Issue or PR someone want to give a demo or request a demo. 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/pipelines Categorizes an issue or PR as relevant to SIG Pipelines (CI/CD) triage/needs-information Indicates an issue needs more information in order to work on it.

Comments

@harshad16
Copy link
Member

Is your feature request related to a problem? Please describe.
Investigate on integrating the thamos advise task into the method of DevSecOps explained https://cer6erus.medium.com/devsecops-with-tekton-and-openshift-cd95e299dbbd

Following the discussion here: https://chat.google.com/room/AAAAlBw51BQ/mwN9Fqhq7BY

Describe the solution you'd like
TBD

@goern
Copy link
Member

goern commented May 27, 2021

/kind feature
/kind demo
/priority important-soon
/sig pipelines
/triage needs-information

@sesheta sesheta added kind/feature Categorizes issue or PR as related to a new feature. kind/demo This is an Issue or PR someone want to give a demo or request a demo. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/pipelines Categorizes an issue or PR as relevant to SIG Pipelines (CI/CD) triage/needs-information Indicates an issue needs more information in order to work on it. labels May 27, 2021
@sesheta
Copy link
Contributor

sesheta commented Oct 15, 2021

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 Oct 15, 2021
@sesheta
Copy link
Contributor

sesheta commented Nov 14, 2021

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 Nov 14, 2021
@harshad16
Copy link
Member Author

/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 Nov 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/demo This is an Issue or PR someone want to give a demo or request a demo. 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/pipelines Categorizes an issue or PR as relevant to SIG Pipelines (CI/CD) triage/needs-information Indicates an issue needs more information in order to work on it.
Projects
None yet
Development

No branches or pull requests

3 participants