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
A successful plan run with "No changes. Infrastructure is up-to-date."
Actual Behavior
A failed plan because the provider does not handle 405 responses from the CIS API.
Error: Request failed with status code: 405, ServerErrorResponse: {"trace": "2a3abc35-1a99-4f2e-96bf-b9d5e9d9ff5e", "errors": [{"code": 405, "message": "This action is unavailable for the current plan: Standard"}]}
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
Create an instance using a standard plan, a basic domain and domain settings with defaults using a provider before 1.7.1 (1.5.2 used in this test)
Bump the provider version to 1.8.1
terraform init && terraform plan
Important Factoids
The way the provider checks for domain settings blindly iterates through the list of known settings but some settings are only available to Enterprise plans, trying to even check for them for a domain in a Standard CIS will get an HTTP 405 response.
Ideally the provider should handle HTTP 405 and move on, but these settings currently will cause this problem for Standard plan users:
Terraform Version
Affected Resource(s)
Terraform Configuration Files
Debug Output
https://gist.github.com/maristgeek/08e12be78af575d55bb557c89be75ad7
Expected Behavior
A successful plan run with "No changes. Infrastructure is up-to-date."
Actual Behavior
A failed plan because the provider does not handle 405 responses from the CIS API.
Error: Request failed with status code: 405, ServerErrorResponse: {"trace": "2a3abc35-1a99-4f2e-96bf-b9d5e9d9ff5e", "errors": [{"code": 405, "message": "This action is unavailable for the current plan: Standard"}]}
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
terraform init && terraform plan
Important Factoids
The way the provider checks for domain settings blindly iterates through the list of known settings but some settings are only available to Enterprise plans, trying to even check for them for a domain in a Standard CIS will get an HTTP 405 response.
Ideally the provider should handle HTTP 405 and move on, but these settings currently will cause this problem for Standard plan users:
References
The text was updated successfully, but these errors were encountered: