Skip to content

fix: Save cluster state after creating it in the API #1664

fix: Save cluster state after creating it in the API

fix: Save cluster state after creating it in the API #1664

Triggered via pull request November 18, 2025 09:56
Status Failure
Total duration 4m 19s
Artifacts

test.yml

on: pull_request
Matrix: Terraform provider acceptance tests
Fit to window
Zoom out
Zoom in

Annotations

1 error and 19 warnings
Verify docs
Process completed with exit code 1.
Verify code generation
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>06UIcaQAAAADaI8me42a2RJSX2bNsuBRKUEFPRURHRTA1MjAARWRnZQ==
Verify code generation
Failed to restore: Cache service responded with 400
Lint
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0RkMcaQAAAABK29jfa16cTLSrjnsdJRtbUEFPRURHRTA1MTQARWRnZQ==
Lint
Failed to restore: Cache service responded with 400
Build
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0SEMcaQAAAACUSh3EW67CQaJKYvCGWzGIUEhMMzBFREdFMDEwNwBFZGdl
Build
Failed to restore: Cache service responded with 400
Unit tests
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0TkMcaQAAAAAF1Z76eiOWS5Eg310lZMMPUEFPRURHRTA2MTQARWRnZQ==
Unit tests
Failed to restore: Cache service responded with 400
Verify docs
Failed to restore: Cache service responded with 400
Terraform provider acceptance tests (1.4.*)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0x0McaQAAAAAYO0ttSdlYSJWgsE4gQoaeUEhMMzBFREdFMDIyMQBFZGdl
Terraform provider acceptance tests (1.4.*)
Failed to restore: Cache service responded with 400
Terraform provider acceptance tests (1.1.*)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0xkMcaQAAAADS4uBjL+esR4h4wQDOT0LKQ0hJMzBFREdFMDExNwBFZGdl
Terraform provider acceptance tests (1.1.*)
Failed to restore: Cache service responded with 400
Terraform provider acceptance tests (1.2.*)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0yEMcaQAAAACgAWJ8wwDaQ4kGnohARVm4UEhMMzBFREdFMDEwOABFZGdl
Terraform provider acceptance tests (1.2.*)
Failed to restore: Cache service responded with 400
Terraform provider acceptance tests (1.3.*)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0yUMcaQAAAADFOQlg5W1YQZ5oavu+WyezUEFPRURHRTA1MTkARWRnZQ==
Terraform provider acceptance tests (1.3.*)
Failed to restore: Cache service responded with 400
Terraform provider acceptance tests (1.0.*)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0z0McaQAAAAAe2wj0TO7pQZ+IreeT6w7MUEhMMzBFREdFMDExMgBFZGdl
Terraform provider acceptance tests (1.0.*)
Failed to restore: Cache service responded with 400