fix(namespace): set location as top-level attribute on azapi_resource #131
matt-FFFFFFpr-check.yml
on: pull_request
run managed workflow
/
subscriptions
7s
run managed workflow
/
checksetup
3s
check
4s
run managed workflow
/
Unit Test Run
1m 10s
run managed workflow
/
pr-check
4m 0s
run managed workflow
/
Integration Test Run
1m 45s
Matrix: run managed workflow / testexamples
run managed workflow
/
testexamplescomplete
0s
run managed workflow
/
globalteardown
0s
Deployment protection rules
Reviewers, timers, and other rules protecting deployments in this run
| Event | Environments |
|---|---|
matt-FFFFFF
deleted by matt-FFFFFF
|
|
azure-verified-modules[bot]
deleted by azure-verified-modules[bot]
|
(Environment deleted) |
|
azure-verified-modules[bot]
deleted by azure-verified-modules[bot]
|
(Environment deleted) |
|
azure-verified-modules[bot]
deleted by azure-verified-modules[bot]
|
(Environment deleted) |
|
azure-verified-modules[bot]
deleted by azure-verified-modules[bot]
|
(Environment deleted) |
|
azure-verified-modules[bot]
deleted by azure-verified-modules[bot]
|
(Environment deleted) |
|
azure-verified-modules[bot]
deleted by azure-verified-modules[bot]
|
(Environment deleted) |
|
azure-verified-modules[bot]
deleted by azure-verified-modules[bot]
|
(Environment deleted) |
|
azure-verified-modules[bot]
deleted by azure-verified-modules[bot]
|
(Environment deleted) |
Annotations
9 errors and 4 warnings
|
run managed workflow / pr-check
Process completed with exit code 2.
|
|
run managed workflow / private
The deployment was rejected or didn't satisfy other protection rules.
|
|
run managed workflow / waf-aligned
The deployment was rejected or didn't satisfy other protection rules.
|
|
run managed workflow / automatic-private
The deployment was rejected or didn't satisfy other protection rules.
|
|
run managed workflow / default
The deployment was rejected or didn't satisfy other protection rules.
|
|
run managed workflow / stateful-workloads
The deployment was rejected or didn't satisfy other protection rules.
|
|
run managed workflow / namespaces
The deployment was rejected or didn't satisfy other protection rules.
|
|
run managed workflow / automatic
The deployment was rejected or didn't satisfy other protection rules.
|
|
run managed workflow / create-before-destroy
The deployment was rejected or didn't satisfy other protection rules.
|
|
run managed workflow / getexamples
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683. 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/
|
|
run managed workflow / Integration Test Run
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, docker/setup-docker-action@efe9e3891a4f7307e689f2100b33a155b900a608. 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/
|
|
run managed workflow / pr-check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, docker/setup-docker-action@efe9e3891a4f7307e689f2100b33a155b900a608. 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/
|
|
run managed workflow / checkteardown
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683. 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/
|