You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 9, 2022. It is now read-only.
We're planning on using a centralized snyk-orgs.yaml file to drive the majority of our "snyk-sync" imports. Our GitHub repositories will have topics that act a bit like team/platform/application tags. We also currently tag our projects in Snyk so that our vulnerability management platform can integrate all of our data on a team-by-team basis.
I'd like the ability to specify one or more Snyk key-value tag pairs for each topic in the snyk-orgs.yaml file. For example:
Does an org match the topics for a repo? Yes -> include any tags specified for that org-topic match in the snyk-orgs.,yaml file.
Does an import.yaml file exist? Yes -> include any additional tags specified in the import.yaml file.
Bonus points if it doesn't add multiple tags for the same key, case-insensitive. This is a weird quirk of Snyk that is different than every other tagging system out there, and causes us quite a few headaches :)
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We're planning on using a centralized
snyk-orgs.yaml
file to drive the majority of our "snyk-sync" imports. Our GitHub repositories will have topics that act a bit like team/platform/application tags. We also currently tag our projects in Snyk so that our vulnerability management platform can integrate all of our data on a team-by-team basis.I'd like the ability to specify one or more Snyk key-value tag pairs for each topic in the
snyk-orgs.yaml
file. For example:Bonus points if it doesn't add multiple tags for the same key, case-insensitive. This is a weird quirk of Snyk that is different than every other tagging system out there, and causes us quite a few headaches :)
The text was updated successfully, but these errors were encountered: