You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First, thank you for the work on this module, it's been really helpful and the examples are very useful too.
I wanted to ask for some help on an issue that i'm running into. I'm currently following the AWS example, which leverages gitops-bridge to provide the metadata between TF and argo. What i'm noticing is that no matter what I do, the helm_release for argo and the kubernetes secret consistently want to update every single time I run TF apply. Here's the exact message:
# module.eks_cluster.module.gitops_bridge_bootstrap.helm_release.argocd[0] will be updated in-place
~ resource "helm_release" "argocd" {
id = "argo-cd"
~ metadata = [
- {
- app_version = "v2.8.2"
- chart = "argo-cd"
- name = "argo-cd"
- namespace = "argocd"
- revision = 6
- values = jsonencode(
{
- configs = {
- secret = {
- argocdServerAdminPassword = "(sensitive value)"
}
}
- server = {
- service = {
- type = "LoadBalancer"
}
}
}
)
- version = "5.45.0"
},
] -> (known after apply)
name = "argo-cd"
# (28 unchanged attributes hidden)
- set_sensitive {
# At least one attribute in this block is (or was) sensitive,
# so its contents will not be displayed.
}
# (1 unchanged block hidden)
}
Do you know which 2 changes is referring to?
Which example your using? this would help us reproduce it. Perharps the blue-green pattern here? for @allamand to take a look
Hey all,
First, thank you for the work on this module, it's been really helpful and the examples are very useful too.
I wanted to ask for some help on an issue that i'm running into. I'm currently following the AWS example, which leverages gitops-bridge to provide the metadata between TF and argo. What i'm noticing is that no matter what I do, the helm_release for argo and the kubernetes secret consistently want to update every single time I run TF apply. Here's the exact message:
Is there a way to avoid this consistently changing?
The text was updated successfully, but these errors were encountered: