Update cloudposse/github-action-deploy-argocd action to v0.13.0

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/github-action-deploy-argocd	action	minor	0.8.1 -> v0.13.0

---

Release Notes

cloudposse/github-action-deploy-argocd (cloudposse/github-action-deploy-argocd)

v0.13.0

Compare Source

feat: Support alternate token for sync mode @​milldr (#​66)

what

• Add option to specify a different token for sync mode

why

• We need permission to 2 different repo: the desire state repo (to update manifests) and the app repo (to send sync mode updates)

references

• n/a

🤖 Automatic Updates

Update .github/settings.yml @​osterman (#​63)

what

• Update .github/settings.yml
• Drop .github/auto-release.yml files

why

• Re-apply .github/settings.yml from org level
• Use organization level auto-release settings

references

• DEV-1242 Add protected tags with Repository Rulesets on GitHub

v0.12.0

Compare Source

Feature: break glass input `helm-args` and set globals for subcharts to use. @​Benbentwo (#​62)

what

• Added break glass input helm-args incase our set values do not suffice
• Added --set global.image.tag as the globals can be universally referenced (see references)

why

• break glass provided so this is highly extensible
• global added for subcharts. this way you can reuse your chart several times and override the image of a deployment with {{ $.Values.global.image.tag }}

references

• https://helm.sh/docs/chart_template_guide/subcharts_and_globals/#global-chart-values

v0.11.3

Compare Source

🐛 Bug Fixes

fix: use 'sudo' when installing the chamber binary @​korenyoni (#​61)

what

• use 'sudo' when installing the chamber binary

why

The test suite in this repo passed, but using this action in practice results in:

+ install chamber-v2.14.1-linux-amd64 /usr/local/bin/chamber
install: cannot create regular file '/usr/local/bin/chamber': Permission denied

references

• Follow up for #​60

v0.11.2

Compare Source

🐛 Bug Fixes

fix: install chamber directly instead of using a container (bypass Docker Hub rate limits) @​korenyoni (#​60)

what

• Install chamber directly instead of using a container
• Update localstack endpoint for chamber, now that chamber does not run in a container.

why

• Bypass Docker Hub rate limits

references

• N/A

v0.11.1

Compare Source

🚀 Enhancements

YQ Improvement: Only one url @​Benbentwo (#​59)

what

• yq ea reads multi documents, currently rendering as

  foo.net
  ---
  foo.com
  

This then fails the action.

This update enhances that action to remove the --- from rendering via -N. Furthermore it will only pick the first URL found.

v0.11.0

Compare Source

Change Dependency build to it's own step with flag to enable @​Benbentwo (#​58)

what

• separate step for helm dependency build

why

• We cannot assume that the credentials to deploy to EKS are the same as fetching chart dependencies, thus this should live as an optional step to build the chart before rendering

v0.10.0

Compare Source

Support dependencies @​Benbentwo (#​57)

what

• run helm dependency build before templating

why

• required if chart has dependencies

v0.9.0

Compare Source

🚀 Enhancements

feat: parameterize retry action inputs @​korenyoni (#​56)

what

• Parameterize inputs for nick-fields/retry action (keep previous values as defaults).

why

• Allow inputs such as max_attempts to be adjusted.

references

*N/A

🤖 Automatic Updates

Update release workflow to allow pull-requests: write @​osterman (#​55)

what

• Update workflow (.github/workflows/release.yaml) to have permission to comment on PR

why

• Add comment to PR when it is released

v0.8.2

Compare Source

Revert "Update action.yml" @​Benbentwo (#​54)

This reverts commit 668eb002b3a66511987fcc397b5baed7691d203c.

what

• Revert back to Dockerhub images

why

• While ECR image is nice for pull rates, we need to trust the source

`values_file` input - support array @​Benbentwo (#​50)

what

• values_file supports comma separated list

why

• allows multiple values files

🤖 Automatic Updates

Use GitHub Action Workflows from `cloudposse/.github` Repo @​osterman (#​53)

what

• Update workflows (.github/workflows/settings.yaml) to use shared workflows from .github repo

why

• Reduce nested levels of reusable workflows

Use GitHub Action Workflows from `cloudposse/.github` Repo @​osterman (#​52)

what

• Update workflows (.github/workflows/settings.yaml)

why

• Support new readme generation workflow.
• Generate banners

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.