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

Enhancement: Introduce Vulnerability Policy And user defined gitops repo validation In feasibility #4879

Open
2 tasks done
Shivam-nagar23 opened this issue Apr 4, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@Shivam-nagar23
Copy link
Member

Shivam-nagar23 commented Apr 4, 2024

🔖 Feature description

  • Security Vulnerability should be included in feasibility Checker.
  • If deployment fails because of vulnerability policy, we should not create deployment history instead can be shown card msg on source info in case of auto deployment ,in case of manual will get direct response.
  • Also handle user defined gitops repo validation case without history

🎤 Pitch / Usecases

Would be overall consistent with feasibility, as in some cases we create history, consistent behaviour overall system will be good.

🔄️ Alternative

No response

👀 Have you spent some time to check if this issue has been raised before?

  • I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

AB#9133

@Shivam-nagar23 Shivam-nagar23 added the enhancement New feature or request label Apr 4, 2024
@Shivam-nagar23 Shivam-nagar23 changed the title Enhacement: Introduce Vulnerability Policy In feasibility Enhancement: Introduce Vulnerability Policy In feasibility Apr 5, 2024
@Shivam-nagar23 Shivam-nagar23 changed the title Enhancement: Introduce Vulnerability Policy In feasibility Enhancement: Introduce Vulnerability Policy And user defined gitops repo validation In feasibility Apr 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants