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
It is currently not possible to create a tfe_registry_module and the corresponding tfe_no_code_modulevariable_options definitions in a single apply.
When the tfe_no_code_module resource is created immediately after the tfe_registry_module but before a version has ingressed, the no-code module has no version to pin to and read the required input variables from. The variable_options do not actually get set on the no-code settings, even though the apply apparently succeeds. A second apply actually adds them.
Further, if you explicitly set the tfe_no_code_module.version_pin value, the apply will error:
│ Error: Error creating no-code module for registry module mod-tF5Ama5MJAsNPy6H: unprocessable entity
│
│ Validation failed: Provided version pin is not equal to latest or provided string does not represent an existing version of the module.
Attempted Solutions
I am only able to solve this by inserting a time_sleep resource between the tfe_registry_module and tfe_no_code_module resources, but this is arbitrary and subject to fail depending on the amount of time needed to ingress the first version.
Use-cases
It is currently not possible to create a tfe_registry_module and the corresponding
tfe_no_code_module
variable_options
definitions in a single apply.When the
tfe_no_code_module
resource is created immediately after thetfe_registry_module
but before a version has ingressed, the no-code module has no version to pin to and read the required input variables from. Thevariable_options
do not actually get set on the no-code settings, even though the apply apparently succeeds. A second apply actually adds them.Further, if you explicitly set the
tfe_no_code_module.version_pin
value, the apply will error:Attempted Solutions
I am only able to solve this by inserting a
time_sleep
resource between thetfe_registry_module
andtfe_no_code_module
resources, but this is arbitrary and subject to fail depending on the amount of time needed to ingress the first version.Proposal
I propose adding an optional
wait_for_ingress
(or similarly named) attribute to thevcs_repo
block intfe_registry_module
, as such:The new attribute would default to
false
to preserve existing behavior.The text was updated successfully, but these errors were encountered: