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
helm_release and helm_template should be tracking the digest for OCI charts, but it appears that the sha hash is completely ignored. This means that there is no way to update to the latest version of a development chart with a static development tag like v0.0.0-latest
Even after using terraform state rm <helm_template_data_source> the provider fails to check if the digest for a given tag has changed.
Helm itself inexplicably also does not track the digest. However, regardless of Helm's deficiencies, two different SHAs mean two different manifests. That is drift regardless of whether helm acknowledges it or not and it needs to be tracked by the provider.
helm_release
andhelm_template
should be tracking the digest for OCI charts, but it appears that the sha hash is completely ignored. This means that there is no way to update to the latest version of a development chart with a static development tag likev0.0.0-latest
Even after using
terraform state rm <helm_template_data_source>
the provider fails to check if the digest for a given tag has changed.Example
Terraform, Provider, Kubernetes and Helm Versions
Affected Resource(s)
Affected Data Sources
The text was updated successfully, but these errors were encountered: