Validation for Terraform Recipe Template Paths
Closed this issue · 4 comments
Overview of feature request
Current State/Problem
Currently, we support only Terraform registry and HTTP URLs as allowed module sources for Terraform recipe template paths. However, we lack a proper validation mechanism for when an incorrect source is given during either recipe registration or deployment. Consequently, when a deployment fails, the reason provided to users is ambiguous resulting into a poor user experience.
Proposed Solution
To address this, we should utilize Terraform's module parsing logic to verify the recipe template path when the recipe templateKind is provided as Terraform, at recipe registration stage.
Acceptance criteria
If an unsupported template path for a Terraform recipe is provided, the recipe registration should fail and return a detailed error message to the user.
👋 @kachawla Thanks for filing this feature request.
A project maintainer will review this feature request and get back to you soon.
We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.
For more information on our triage process please visit our triage overview
👍 We've reviewed this issue and have agreed to add it to our backlog. Please subscribe to this issue for notifications, we'll provide updates when we pick it up.
We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.
For more information on our triage process please visit our triage overview
We've prioritized work on this issue. Please subscribe to this issue for notifications, we'll provide updates as we make progress.
We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.
For more information on our triage process please visit our triage overview
Closing, we thought the initial issue was caused by Radius not supporting all module sources. This doesn't seem to be the case as Git, S3, etc are able to be used so there's no need for additional validation.