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
Thank you for opening an issue. Please note that we try to keep the Terraform issue tracker reserved for bug reports and feature requests. For general usage questions, please see: https://www.terraform.io/community.html.
Thank you for the report. Right now this provider only supports targets/projects using the Github/Github Enterprise integrations.
We don't have access to Bitbucket at the moment so I'm not sure if responses from the Snyk API when importing are the same with Bitbucket as they are with GitHub or not. I do know that the current API from Snyk is very very limited on what you can do with targets and that the provider does some things to make it work with Formstack's GitHub naming convention (although it works with my personal repositories so this might be universal)
Snyk has a beta API that has a lot more functionality and may allow us to improve this provider by a lot, but I haven't been able to get a release date out of them for that.
If for whatever reason Bitbucket isn't the issue here, there is another known scenario in which this provider crashes. If you try to import a repository and that repository doesn't have a supported Snyk dependency or code file that Snyk can scan, the import will fail and crash this provider.
I'll try to get both of these issue mentioned in the documentation on an upcoming release as I don't really have an ETA on when they will be addressed.
Hi there,
Thank you for opening an issue. Please note that we try to keep the Terraform issue tracker reserved for bug reports and feature requests. For general usage questions, please see: https://www.terraform.io/community.html.
Terraform Version
Terraform v1.2.9
on darwin_arm64
Affected Resource(s)
Terraform Configuration Files
Panic Output
Actual Behavior
Crashing
Steps to Reproduce
terraform apply
The text was updated successfully, but these errors were encountered: