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
Benefit/Result/Outcome
As an end-user with no prior knowledge of the underlying technologies that support MissionLZ, it'd be nice if the Terraform remote state was also set up for me should I choose the UI-driven path.
Today, if I deploy the UI without touching the rest of the codebase the UI returns the failed logs of apply_tf.sh: Applying saca-hub (1/5)... Config Resource Group rg-tf-sacahub-[deploymentkey] does not exist...validate config.vars file and re-run script before giving up.
Description
Create the terraform state related resources and RBAC assignments for those resources in setup_ezdeploy so that when the UI is launched for the first time, all of the backing stores are available too.
Acceptance Criteria
setup_ezdeploy.sh creates the terraform resource groups for the given subscriptions
this works for 1:M subscriptions the user provides
The text was updated successfully, but these errors were encountered:
Benefit/Result/Outcome
As an end-user with no prior knowledge of the underlying technologies that support MissionLZ, it'd be nice if the Terraform remote state was also set up for me should I choose the UI-driven path.
Today, if I deploy the UI without touching the rest of the codebase the UI returns the failed logs of apply_tf.sh:
Applying saca-hub (1/5)... Config Resource Group rg-tf-sacahub-[deploymentkey] does not exist...validate config.vars file and re-run script
before giving up.Description
Create the terraform state related resources and RBAC assignments for those resources in setup_ezdeploy so that when the UI is launched for the first time, all of the backing stores are available too.
Acceptance Criteria
The text was updated successfully, but these errors were encountered: