v6.0.0
Breaking Changes
The provider no longer supports Terraform versions <1.x
as we now make use of the terraform-plugin-framework
has been introduced, and the provider has been upgraded to make use of Terraform Plugin Protocol Version 6. Consumers must make use of Terraform >=1.x
when using the provider. This change also introduced some changes to the validation of the provider configuration, which may result in some existing configuration combinations being flagged as invalid. Known changes are listed below but feel free to reach out if you have any other issues.
- Remove
server_addr
configuration when any of the following attributes are set:port_forward
,port_forward_with_namespace
,use_local_config
,core
. E.g:provider "argocd" { - server_addr = "foo" use_local_config = true # context = "foo" # Use explicit context from ArgoCD config instead of `current-context`. }
What's Changed
- Implement provider using
terraform-plugin-framework
and upgrade to TF Plugin Protocol Version V6 (#301) - New resources:
- New data sources:
argocd_application
(#302)- Note: this data source has been implemented using features exposed by Terraform Plugin Protocol Version 6, so accessing attributes on the data source will differ slightly compared to the
argocd_application
resource. E.g. usedata.argocd_application.this.status.reconciled_at
instead ofdata.argocd_application.this.status.0.reconciled_at
- Note: this data source has been implemented using features exposed by Terraform Plugin Protocol Version 6, so accessing attributes on the data source will differ slightly compared to the
Changelog
- 08682d2 Add
argocd_gpg_key
resource (#315) - cced478 Add
argocd_application
data source (#302) - 6ae499d build(deps): bump k8s.io/kubernetes from 1.24.14 to 1.24.15 (#316)
- aeeb731 Implement provider using
terraform-plugin-framework
and upgrade to TF Plugin Protocol Version V6 (#301)