Skip to content

fix: use openstack as hcp metadata provider name #250

fix: use openstack as hcp metadata provider name

fix: use openstack as hcp metadata provider name #250

Triggered via pull request December 2, 2025 15:02
Status Success
Total duration 1m 39s
Artifacts

go-validate.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

10 warnings
Gofmt check
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>0pv8uaQAAAADwW7tQKf1xQJkk2jv2sdR+RE0yRURHRTA4MTkARWRnZQ==
Gofmt check
Failed to restore: Cache service responded with 400
Go Mod Tidy
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>0vf8uaQAAAADWroVg0k+FQZSjh+v0ie8IUEFPRURHRTA1MjEARWRnZQ==
Go Mod Tidy
Failed to restore: Cache service responded with 400
Lint check
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>01f8uaQAAAADbMeNBgw4IRZC2CT+4gwOCUEhMMzBFREdFMDIwNwBFZGdl
Lint check
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>00f8uaQAAAABxgA1NdS5VQqH7Rv2HmCWVUEhMMzBFREdFMDEyMgBFZGdl
Lint check
Failed to restore: Cache service responded with 400
Lint check
Failed to restore: Cache service responded with 400
Generate check
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>03/8uaQAAAABV73ZV+1zgS6N1t0I/YZ8aUEhMMzBFREdFMDQxMABFZGdl
Generate check
Failed to restore: Cache service responded with 400