feat: Support Federated Identity Providers for service accounts #4427
JorTurFerci.yaml
on: pull_request
CI
3m 2s
Check GoReleaser config
12s
Code coverage report
0s
Annotations
5 errors and 1 warning
|
CI
Process completed with exit code 2.
|
|
CI:
stackit/internal/services/serviceaccount/federated_identity_provider/resource_test.go#L148
cannot use testutil.ServiceAccountCustomEndpoint (variable of struct type testutil.customEndpointConfig) as string value in argument to config.WithEndpoint (typecheck)
|
|
CI:
stackit/internal/services/serviceaccount/federated_identity_provider/resource_test.go#L144
invalid operation: testutil.ServiceAccountCustomEndpoint == "" (mismatched types testutil.customEndpointConfig and untyped string)
|
|
CI:
stackit/internal/services/serviceaccount/federated_identity_provider/resource_test.go#L136
undefined: testutil.ServiceAccountProviderConfig
|
|
CI:
stackit/internal/services/serviceaccount/federated_identity_provider/resource_test.go#L105
undefined: testutil.ServiceAccountProviderConfig
|
|
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/
|