Skip to content

TP_DOMAIN initialization in workshop doc is initialized ambiguously #203

@KulbhushanBhalerao

Description

@KulbhushanBhalerao
  1. In AKS Cluster setup, TP_DOMAIN is initialized as :

export TP_TOP_LEVEL_DOMAIN="azure.example.com" # top level domain of TP_DOMAIN
export TP_SANDBOX="dp1" # hostname of TP_DOMAIN

export TP_DOMAIN="${TP_SANDBOX}.${TP_TOP_LEVEL_DOMAIN}" # domain to be used

Ref: https://github.com/TIBCOSoftware/tp-helm-charts/blob/main/docs/workshop/aks/cluster-setup/README.md#export-required-variables

Following optional lines also needs to be commented otherwise it will overwrite previous value.

export TP_DOMAIN="services.dp1.azure.example.com" # domain to be used for services and capabilities
  1. And in CP Readme, TP_DOMAIN is initialized as,

export TP_TOP_LEVEL_DOMAIN="azure.example.com" # top level domain of TP_DOMAIN
export TP_SANDBOX="dp1" # hostname of TP_DOMAIN
export TP_MAIN_INGRESS_SANDBOX_SUBDOMAIN= "department" # sandbox subdomain to be used

export TP_DOMAIN="${TP_MAIN_INGRESS_SANDBOX_SUBDOMAIN}.${TP_SANDBOX}.${TP_TOP_LEVEL_DOMAIN}" # domain to be used

Ref: https://github.com/TIBCOSoftware/tp-helm-charts/tree/main/docs/workshop/aks/control-plane#export-required-variables

So, when you are running instructions and setting env variables in the same terminal, this variable gets overwritten and for both steps (cluster setup and CP setup) values are different.

Is this intented?

Thank you,
Kulbhushan

Metadata

Metadata

Labels

documentationImprovements or additions to documentation

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions