The Studio UI build pipeline doesn’t have a parameter for receiving the environment file from Trinity. If it did, I wouldn’t know how to send it from Trinity when triggering the pipeline.
Once the environment file is received from Trinity in the pipeline, I will be able to replace the environment.ts file after the branch is checked out.
We tend to rely on Angular’s built-in file replacement mechanism to inject environment-specific variables at build time. This means that it takes the environment.prod.ts file or environment.ts available in the codebase based on the configuration specified and compiles the application along with the environment variables into static files when the build pipeline from Trinity is triggered.
If while building UI applications, Trinity application can accept the environment file from the user, it would allow sending the environment file to the build pipeline where I could use Angular’s built-in file replacement to update the environment file and build with the intended environment configuration.
@shiv If you include the file during build time, you’ll need to create separate builds for each environment. With Trinity’s solution, you can eliminate this hassle—build once and deploy seamlessly across multiple environments.
The feature you’re requesting goes against the core principle of deploying the same build across multiple environments. As a result, we have no plans to implement it.
If you need any further clarification, feel free to reach out.
How would I set the SSD URL for UI apps based on the different environments that the same build gets deployed to? Making edits on Trinity’s Studio Environment variables has no effect, as much as I know, this has been an issue for UI apps deployed from Trinity.
During the deployment of the UI applications, you will have the option to update the environment values. These values will be used during the application’s runtime.