Couple of questions
- Dominant language
- Go
- Stars
- 2
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Hi there,
I have a couple of questions around how aztfpreflight works in practice.
Given that aztfpreflight evaluates a Terraform plan output, does this mean our Terraform configuration can use providers beyond azurerm—for example, azapi? Or is aztfpreflight effectively limited to plans generated specifically with the azurerm provider?
Additionally, I understand that the azapi provider supports a preflight capability and can be used with terraform test (in both plan and apply modes), allowing for fairly deep validation.
In comparison, since aztfpreflight operates purely on the Terraform plan output, it seems there may be gaps in what it can validate. For example:
- cases where a policy deny only triggers at deployment time
- scenarios involving values that are “known after apply”
- situations requiring runtime or cross-resource evaluation
Is this an inherent limitation of the tool, or is there a way to address or mitigate these gaps?
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.