Bump azure/arm-deploy from 1 to 2

[dependabot]

Bumps azure/arm-deploy from 1 to 2.

Release notes

Sourced from azure/arm-deploy's releases.

v2

Highlights

• Added tenant scope deployments for the ARM Deploy action by @​bearmannl in Azure/arm-deploy#125
• Upgrade to Node 20 by @​anthony-c-martin in Azure/arm-deploy#142

Full Changelog: Azure/arm-deploy@v1.0.8...v2

Releasing v1.0.9

What's Changed

• Updated node version from 12 to 16
• Updated @​actions/core to ^1.10.0

Releasing v1.0.8

[Fix] Spacing bug in additional params

Releasing v1.0.7

Removed additionalArguments while validation step

Releasing v1.0.6

Added additionalArguments input.

All the extra parameters can be passed as string using additionalArguments.

additionalArguments: "--what-if --what-if-exclude-change-types Create Ignore --rollback-on-error"

Releasing v1.0.5

1. Added failOnStdErr input Azure/arm-deploy#61

Releasing v1.0.4

1. Fixed az-cli compat issue
2. Updated test

Releasing v1.0.3 version

• Fixing io streams issue
• other readme changes

Releasing v1.0.2 version

No release notes provided.

arm-deploy@v1.0.1

A GitHub action to automate your workflow to deploy ARM templates.

Usage

Sample workflow to build and deploy a ARM template.

</tr></table> 

... (truncated)

Changelog

Sourced from azure/arm-deploy's changelog.

Releasing a new version

Semanting versioning is used to release different versions of the action. Following steps are to be followed :

1. Create a new branch for every major version.
   Example, releases/v1, releases/v2.
2. For every minor and patch release for a major version, update the corresponding release branch.
   Example, for releasing v1.1.1, update releases/v1.
3. Create tags for every new release (major/minor/patch).
   Example,v1.0.0. , v1.0.1, v2.0.1, etc. and also have tags like v1, v2 for every major version release.
4. On releasing minor and patch versions, update the tag of the corresponding major version.
   Example, for releasing v1.0.1, update the v1 tag to point to the ref of the current release.
   The following commands are to be run on the release\v1 branch so that it picks the latest commit and updates the v1 tag accordingly : (Ensure that you are on same commit locally as you want to release.)

• git tag -fa v1 -m "Update v1 tag"
• git push origin v1 --force

Commits

• a1361c2 Fix CI to use OIDC (#161)
• 732d82b Non-functional refactor to improve testability (#143)
• 07ed08a Bump @​zeit/ncc from 0.21.1 to 0.22.3 (#146)
• 1b55bd0 Bump actions/setup-node from 1 to 4 (#145)
• 9cb1ead Bump actions/checkout from 1 to 4 (#144)
• 7e7091d Add dependabot + other standard Bicep project config (#142)
• 95b309a Added tenant scope deployments for the ARM Deploy action (#125)
• ba158a2 Add changes
• 7fcad78 Correcting typescript version for @​types/node (#117)
• 8d99c72 Upgraded to node16 (#116)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)