Skip to content

chore(sqlserverflex): use new multi API version support SDK #4190

chore(sqlserverflex): use new multi API version support SDK

chore(sqlserverflex): use new multi API version support SDK #4190

Triggered via pull request April 7, 2026 19:31
Status Failure
Total duration 1m 10s
Artifacts

ci.yaml

on: pull_request
Check GoReleaser config
10s
Check GoReleaser config
Code coverage report
Code coverage report
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 1 warning
CI
Process completed with exit code 2.
CI: stackit/internal/services/sqlserverflex/instance/resource_test.go#L417
undefined: sqlserverflex.CreateInstancePayloadOptions (typecheck)
CI: stackit/internal/services/sqlserverflex/instance/resource_test.go#L413
undefined: sqlserverflex.CreateInstancePayloadStorage
CI: stackit/internal/services/sqlserverflex/instance/resource_test.go#L412
cannot use new("name") (value of type *string) as string value in struct literal
CI: stackit/internal/services/sqlserverflex/instance/resource_test.go#L411
cannot use new("flavor_id") (value of type *string) as string value in struct literal
CI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/