-
Notifications
You must be signed in to change notification settings - Fork 38
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
All plans suddenly failing on 1.0.92 #320
Comments
I can confirm this. This should be tackled with high priority. We are currently blocked by this. Thank you. |
Just tested again and all is working. I suspect whatever change was deployed to the API has been rolled back |
Thank you for notifying us about this issue. While the cause of the initial behavior might not be immediately clear, we’ll continue to review recent changes on our end to help prevent similar issues in the future. If you experience any further issues or have questions, please feel free to reach out. |
Deployment until yesterday worked, but currently I get the same error and no deployment possible. I'm using latest provider version as well as terraform.
|
@amirkkn We have identified an issue causing unexpected behavior in the EU data center and are actively investigating the root cause. In the meantime, we recommend attempting the deployment again, as it might succeed on subsequent attempts. Thank you for your patience while we work to resolve this. |
For the last two days I have been importing our existing Site24x7 infrastructure into Terraform.
Sometime between 11:04 UTC and 12:30 UTC today (12 November) all our Terraform plans have started failing. All plans for all resource types we create are failing with the same reason:
I'm interpreting this as the API is now returning
type: number
for these fields and the provider is expectingtype: string
.I can reproduce this with the following basic terraform:
The tag is created though:
The text was updated successfully, but these errors were encountered: