For multi-tenant environments, the application root context might be used to differentiate the deployments in an environment.
Currently, we hard-code the application root context to "prweb". This prevents load balancers from using the root context for traffic routing.
As part of a the configuration of a helm deployment, a user should have the ability to override the default application root context.
Passing an environment variable with the custom application root context name into the docker image will allow this override.
NOTE: This requires a change to the docker-pega-web-ready project as well to consume this environment variable.
For multi-tenant environments, the application root context might be used to differentiate the deployments in an environment.
Currently, we hard-code the application root context to "prweb". This prevents load balancers from using the root context for traffic routing.
As part of a the configuration of a helm deployment, a user should have the ability to override the default application root context.
Passing an environment variable with the custom application root context name into the docker image will allow this override.
NOTE: This requires a change to the docker-pega-web-ready project as well to consume this environment variable.