Skip to content

Stop bundling environment.ts files (treat as a loose asset) #6688

Closed
@ghost

Description

Bug Report or Feature Request (mark with an x)

- [ ] bug report -> please search issues before submitting
- [x] feature request

Versions.

N/A

Repro steps.

N/A

The log given by the failure.

N/A

Desired functionality.

We frequently add environment variables to the environment.ts file ... surprise!. We use the standard development and production builds but either can be deployed to any number of sites: Company A host, Company B host... and each host may have its own environment settings.

Mention any other details that might be useful.

Each site has its own environment settings (for example each site may point to a different host for API calls). Since the environment files are bundled we either have to rebuild and specify another environment file for each build (not going to do that) or perform variable substitutions on bundle files (holding our noses and doing that). The environment files should be loose (not bundled) so tools like Ansible or your own shell scripts can more safely and efficiently change the values as part of the deployment.

Metadata

Metadata

Assignees

Labels

P5The team acknowledges the request but does not plan to address it, it remains open for discussionfeatureIssue that requests a new featureseverity2: inconvenient

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions