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
Describe the user need
Some customers only have 1 Github Org with many repos within this Org and do access control by using Github Teams to control access to repos within this single org. Currently, snyk-api-import will automatically map a Github org to a Snyk Org but any customer that wants to create a Snyk Org per Team (or Business Unit) they can do so, but during the import:data phase, they will need to manually map the OrgID and IntegrationID underneath each repo within json generated by snyk-api-import which could be time consuming. The ask here is if the customer has some mapping of Snyk org to Repo (coudl they use some type of config file/mapping file) to automatically assign the repos the right OrgID and IntegrationID
If you have an idea how you would like this to behave please share in as much detail as possible.
Potentially if a customer had a list of Team:Repo as a csv, if we can somehow make a utility to first map the Team:Repo to Orgslug:Repo (As Team would be the orgName) -> OrgID:Repo (Where we convert the OrgSlug into OrgID) -> OrgID + IntegrationID:Repo (Where based on the OrgID we can also pull the IntegrationID) -> somehow append this OrgID + IntegrationID into the json generated by snyk-api-import then customers would have a nice final json of Repo + OrgID + IntegrationID that is generated nicely without manual json manipulation
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Describe the user need
Some customers only have 1 Github Org with many repos within this Org and do access control by using Github Teams to control access to repos within this single org. Currently, snyk-api-import will automatically map a Github org to a Snyk Org but any customer that wants to create a Snyk Org per Team (or Business Unit) they can do so, but during the import:data phase, they will need to manually map the OrgID and IntegrationID underneath each repo within json generated by snyk-api-import which could be time consuming. The ask here is if the customer has some mapping of Snyk org to Repo (coudl they use some type of config file/mapping file) to automatically assign the repos the right OrgID and IntegrationID
If you have an idea how you would like this to behave please share in as much detail as possible.
Potentially if a customer had a list of Team:Repo as a csv, if we can somehow make a utility to first map the Team:Repo to Orgslug:Repo (As Team would be the orgName) -> OrgID:Repo (Where we convert the OrgSlug into OrgID) -> OrgID + IntegrationID:Repo (Where based on the OrgID we can also pull the IntegrationID) -> somehow append this OrgID + IntegrationID into the json generated by snyk-api-import then customers would have a nice final json of Repo + OrgID + IntegrationID that is generated nicely without manual json manipulation
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: