Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Customizing env.yaml #65

Open
allquixotic opened this issue May 4, 2022 · 0 comments
Open

Customizing env.yaml #65

allquixotic opened this issue May 4, 2022 · 0 comments
Assignees
Labels
bug Something isn't working p2 Priority 2 tasks

Comments

@allquixotic
Copy link
Contributor

allquixotic commented May 4, 2022

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.

@leelalagudu leelalagudu added bug Something isn't working p1 Priority 1 tasks labels May 24, 2022
@leelalagudu leelalagudu added p2 Priority 2 tasks and removed p1 Priority 1 tasks labels May 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working p2 Priority 2 tasks
Projects
None yet
Development

No branches or pull requests

3 participants