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
The HCL generation still has some errors and sometimes fails or produces wrong outputs (not right directions or nodes).
We do not have such issue on TFState (we use to but was fixed) but on HCL we have it.
We have to find why is it failing, most probably related on how the HCL->graph.Graph before any operation is done to the graph as reading the HCL it's not as easy as TFState(json).
This issues are "hard" to reproduce as they fail once in a while but not always, for example:
--- FAIL: TestFromHCL_FlexibleEngine (0.00s)
--- FAIL: TestFromHCL_FlexibleEngine/SuccessSG (0.00s)
helper_test.go:66:
Error Trace: helper_test.go:66
hcl_test.go:90
Error: Fail
Test: TestFromHCL_FlexibleEngine/SuccessSG
Messages: The Edge with Source "flexibleengine_compute_instance_v2.instance_two" and Target "flexibleengine_compute_instance_v2.instance_one" is present but in the other direction
FAIL
The text was updated successfully, but these errors were encountered:
The HCL generation still has some errors and sometimes fails or produces wrong outputs (not right directions or nodes).
We do not have such issue on TFState (we use to but was fixed) but on HCL we have it.
We have to find why is it failing, most probably related on how the HCL->
graph.Graph
before any operation is done to the graph as reading the HCL it's not as easy as TFState(json).This issues are "hard" to reproduce as they fail once in a while but not always, for example:
The text was updated successfully, but these errors were encountered: