chore(deps): bump argocd::devops-stack-module-argocd from 6.3.0 to 7.0.0 in /examples/eks

[dependabot[bot]]

Bumps argocd::devops-stack-module-argocd from 6.3.0 to 7.0.0.

Release notes

Sourced from argocd::devops-stack-module-argocd's releases.

v7.0.0

7.0.0 (2024-10-09)

⚠ BREAKING CHANGES

• point the Argo CD provider to the new repository (#133)

Features

• point the Argo CD provider to the new repository (#133) (86616d9)

Migrate provider source oboukili -> argoproj-labs

We've tested the procedure found here and we think the order of the steps is not exactly right. This is the procedure we recommend (note that this should be run manually on your machine and not on a CI/CD workflow):

1. First, make sure you are already using version 6.2.0 of the oboukili/argocd provider.

2. Then, check which modules you have that are using the oboukili/argocd provider.

$ terraform providers
Providers required by configuration:
.
├── provider[registry.terraform.io/hashicorp/helm] 2.15.0
├── (...)
└── provider[registry.terraform.io/oboukili/argocd] 6.2.0
Providers required by state:
(...)

provider[registry.terraform.io/oboukili/argocd]

provider[registry.terraform.io/hashicorp/helm]

3. Afterwards, proceed to point *ALL the DevOps Stack modules to the versions that have changed the source on their respective requirements. In case you have other personal modules that also declare oboukili/argocd as a requirement, you will also need to update them.

4. Also update the required providers on your root module. If you've followed our examples, you should find that configuration on the terraform.tf file in the root folder.

5. Execute the migration via terraform state replace-provider:

$ terraform state replace-provider registry.terraform.io/oboukili/argocd registry.terraform.io/argoproj-labs/argocd
Terraform will perform the following actions:
~ Updating provider:
- registry.terraform.io/oboukili/argocd
</tr></table>

... (truncated)

Changelog

Sourced from argocd::devops-stack-module-argocd's changelog.

7.0.0 (2024-10-09)

⚠ BREAKING CHANGES

• point the Argo CD provider to the new repository (#133)

Features

• point the Argo CD provider to the new repository (#133) (86616d9)

Migrate provider source oboukili -> argoproj-labs

We've tested the procedure found here and we think the order of the steps is not exactly right. This is the procedure we recommend (note that this should be run manually on your machine and not on a CI/CD workflow):

1. First, make sure you are already using version 6.2.0 of the oboukili/argocd provider.

2. Then, check which modules you have that are using the oboukili/argocd provider.

$ terraform providers
Providers required by configuration:
.
├── provider[registry.terraform.io/hashicorp/helm] 2.15.0
├── (...)
└── provider[registry.terraform.io/oboukili/argocd] 6.2.0
Providers required by state:
(...)

provider[registry.terraform.io/oboukili/argocd]

provider[registry.terraform.io/hashicorp/helm]

3. Afterwards, proceed to point *ALL the DevOps Stack modules to the versions that have changed the source on their respective requirements. In case you have other personal modules that also declare oboukili/argocd as a requirement, you will also need to update them.

4. Also update the required providers on your root module. If you've followed our examples, you should find that configuration on the terraform.tf file in the root folder.

5. Execute the migration via terraform state replace-provider:

$ terraform state replace-provider registry.terraform.io/oboukili/argocd registry.terraform.io/argoproj-labs/argocd
Terraform will perform the following actions:
~ Updating provider:
- registry.terraform.io/oboukili/argocd
+ registry.terraform.io/argoproj-labs/argocd
</tr></table>

... (truncated)

Commits

• 379bf0f chore: release 7.0.0 (#134)
• 86616d9 feat!: point the Argo CD provider to the new repository (#133)
• 000ba44 chore(deps): bump peter-evans/create-pull-request from 6 to 7 (#131)
• See full diff 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 merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show 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)