-
Notifications
You must be signed in to change notification settings - Fork 763
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
vulnerability-alerts 404 #716
Comments
Workaround after failed
|
I have the same issue. Thanks for posting a workaround. |
This endpoint is actually documented as being available in GHES 2.22, but we ran into the same thing and have confirmed with GitHub support that this is an error in the documentation. Looks like this is probably means there's a missing test-case from the GHES compatibility tests from #404 as well. It's a slightly weird one in how it crops up as the defaults are different for public and private repos, but I believe running a refresh on a repository resource will always trigger it. #444 was the change which introduced this, so another workaround is to use |
The workaround to use the version 3.0.0 from the provider doesn't seem to be available anymore and even the most recent version of the github enterprise doesn't support this feature yet. Any plan for a fix? |
Seeing the same behavior. Workaround worked:
|
This is a massive pain and not a great workaround. Any plans for fix? |
this was the fix for me, similar to @colltoaction, but with the resource name instead of the repo name in the first 2 spots.
|
👋 Hey Friends, this issue has been automatically marked as |
this bug is quite a pain, it prevents proper creation of new repositories via terraform. The workarounds are merely a "recovery" measure not something that gets the provider running. In our case this also leads to subsequent errors. where autolink references are only partially created. Any references created before this error are there, any references created afterwards are reported as:
|
👋 Hey Friends, this issue has been automatically marked as |
Terraform Version
Affected Resource(s)
github_repository
Terraform Configuration Files
../../modules/tf-repo/main.tf
(pseudo code):.terraform.lock.hcl
:Debug Output
Panic Output
Expected Behavior
If the GHE instance doesn't support
vulnerability-alerts
end-point andvulnerability_alerts = null
orvulnerability_alerts = false
then the provider should not panic when404
is returned by the API.Actual Behavior
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
terraform apply
Important Factoids
References
The text was updated successfully, but these errors were encountered: