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
There is an improvement to be made in teh documentation when detailing "Choose the cluster git repository based on the secrets backend"
Issue: when detailing the steps to set up JX3 using AWS Secret manager: based on the jx3-gitops-repositories/jx3-eks-asm
The documentation should instruct to se the following variables in the main.tf file:
Delete "vault_user" parameter
Set "use_vault" to false
Set "use_asm" to true
Set "create_asm_role" to true
If these variables are not set, the deployment fails, thus creating frustration and causing the user to do excessive research in order to figure out this simple fix.... it happened to me. The note will help new users and addopters of the platform by reducing initial set up pains.
I hope this helps improve the user experience
The text was updated successfully, but these errors were encountered:
Make sure to make the following modifications to the main.tf file:
Delete "vault_user" parameter
Set "use_vault" to false
Set "use_asm" to true
Set "create_asm_role" to true
There is an improvement to be made in teh documentation when detailing "Choose the cluster git repository based on the secrets backend"
Issue: when detailing the steps to set up JX3 using AWS Secret manager: based on the jx3-gitops-repositories/jx3-eks-asm
The documentation should instruct to se the following variables in the main.tf file:
Delete "vault_user" parameter
Set "use_vault" to false
Set "use_asm" to true
Set "create_asm_role" to true
If these variables are not set, the deployment fails, thus creating frustration and causing the user to do excessive research in order to figure out this simple fix.... it happened to me. The note will help new users and addopters of the platform by reducing initial set up pains.
I hope this helps improve the user experience
The text was updated successfully, but these errors were encountered: