(fix) Allow CRD missing error when computing manifest

[MockyJoke]

Description

• This PR aims to fix an issue related to the experimental manifest feature

Issue

When the experimental manifest feature is enabled and deploying two charts with a CRD dependency between them (e.g., Chart A installs a new CRD in its manifest, and Chart B declares objects of that CRD), performing terraform plan raises an error. The error occurs in Chart B, stating that the CRD is not yet installed, thus unable to compute its final manifest.

This is not inherently an issue, as the two charts can be installed successfully as long as Chart A is installed before Chart B. This dependency can be managed by setting the depends_on property for Chart B.

Proposed Solution

• Modify the handling of errors when the manifest feature is enabled to allow such errors to not break the planning process.

References

• Related Issues
  • Experiments Feature Breaking the helm_release asking for CRD to install First
• Applying CRD and chart on same TF

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

[hashicorp-cla-app]

All committers have signed the CLA.

[hashicorp-cla-app]

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement

Learn more about why HashiCorp requires a CLA and what the CLA includes

_{Have you signed the CLA already but the status is still pending? Recheck it.}

[MockyJoke]

Any updates?