Skip to content

Customizing env.yaml #65

@allquixotic

Description

@allquixotic

Per the workshop, customizing the Environment requires updating both the file name of config/env.yaml, and the variable Environment in the file.

The workshop does not provide any instructions for how to change things when changing the App variable.

I tried changing both of these and had no end of errors, especially with the yarn commands, which seem to assume that the Environment and App are set to default.

Also the pipeline itself is not aware of changes to the Environment variable, and fails on something like No such file or directory: config/env.yaml. So in essence, these values must be hard coded to their original values, or the IaC and the yarn scripts fail. This seems to conflict with the intended purpose of having configurable variables for them.

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingp2Priority 2 tasks

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions