Skip to content

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

fix: Save cluster state after creating it in the API

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

Triggered via pull request November 19, 2025 08:56
Status Failure
Total duration 4m 21s
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>0aoYdaQAAAAABfzIztcxdQKs4cGWbOELrUEFPRURHRTA1MTcARWRnZQ==
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>0yIYdaQAAAAAWBV9zSAbKTbGj7RV8xdLzQ0hJMzBFREdFMDExNgBFZGdl
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>0y4YdaQAAAACX31bApcAeTY++FJBcWk6BUEhMMzBFREdFMDQxNwBFZGdl
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>004YdaQAAAADifMu171UoRqLMD0mLe120UEFPRURHRTA2MDcARWRnZQ==
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.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>0TIcdaQAAAACZOWU0+wHeRpOo6LB5bGz+UEhMMzBFREdFMDExMgBFZGdl
Terraform provider acceptance tests (1.0.*)
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>0S4cdaQAAAAAU1EIJE+v1RKOEqVFGYRVHUEFPRURHRTA1MTIARWRnZQ==
Terraform provider acceptance tests (1.4.*)
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>0T4cdaQAAAAD8JYk/UIQ5T7nQqR5mENoOUEhMMzBFREdFMDEyMABFZGdl
Terraform provider acceptance tests (1.3.*)
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>0T4cdaQAAAAB3gZYV4foBSoYAkyvFDdzFUEhMMzBFREdFMDExNwBFZGdl
Terraform provider acceptance tests (1.2.*)
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>0VIcdaQAAAABd8iSgzHbrTJh+hdvYsdZRREVOMzAxMDAwMTA2MDExAEVkZ2U=
Terraform provider acceptance tests (1.1.*)
Failed to restore: Cache service responded with 400