The following demo shows how to configure an two Okta/oidc resource types, one custom for specific application, and standard golden paths for okta, mongo and PVCs.
Terraform is used as echo
, as demo, to avoid any custom providers (Atlas and Okta), the need to configure credentials, tokens and have tenants in those 3rd party services.
Add your token and organization
cd humanitec
cp terraform.tfvars.example terraform.tfvars
terraform init && terraform apply -auto-approve
cd score
export HUMANITEC_ORG="myorg"
export HUMANITEC_TOKEN="mytoken"
export APP_ENV=development
export APP_NAME=sh-demo
score-humanitec delta \
--token $HUMANITEC_TOKEN \
--org $HUMANITEC_ORG \
--app $APP_NAME \
--env $APP_ENV \
-f score/workload1/score.yaml \
--extensions score/workload1/humanitec.score.yaml \
--deploy
export APP_ENV=prod
export APP_NAME=sh-demo
score-humanitec delta \
--token $HUMANITEC_TOKEN \
--org $HUMANITEC_ORG \
--app $APP_NAME \
--env $APP_ENV \
-f score/workload1/score.yaml \
--extensions score/workload1/humanitec.score.yaml \
--deploy
export APP_ENV=development
export APP_NAME=sh-demo2
score-humanitec delta \
--token $HUMANITEC_TOKEN \
--org $HUMANITEC_ORG \
--app $APP_NAME \
--env $APP_ENV \
-f score/workload2/score.yaml \
--extensions score/workload2/humanitec.score.yaml \
--deploy
export APP_ENV=prod
export APP_NAME=sh-demo2
score-humanitec delta \
--token $HUMANITEC_TOKEN \
--org $HUMANITEC_ORG \
--app $APP_NAME \
--env $APP_ENV \
-f score/workload2/score.yaml \
--extensions score/workload2/humanitec.score.yaml \
--deploy