support `--api-versions`

[FalcoSuessgott]

Description

Im installing ArgoCD using the helm TF provider in a blank kubernetes cluster.
The ArgoCD Helm Chart evaluates based on .Capabilities.APIVersions.Has whether the ServiceMonitor CRD should be installed. If the CRD does not exist yet, because ArgoCD installs those CRDs once deployed, the ServiceMonitor CRD will not be created.

As a workaround one can set --api-versions=monitoring.coreos.com/v1 to force the creation of said CRD.

Currently the helm provider does not allow setting any api-versions.

It would be nice, to allow setting these options by having a api_versions of list(string argument in the helm_release resource & data source

Potential Terraform Configuration

# Copy-paste your Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file. For
# security, you can also encrypt the files using our GPG public key.

References

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

[FalcoSuessgott]

Wait I just realised that the --api-versions arg only works for helm template .... This issue does not make sense then. However, does someone have a workaround to archive using the helm provider, rather than fallback to the null_resource?

[FalcoSuessgott]

Alright one can set apiVersionOverrides in the helm chart to bypass my issue. Closing it then :)