We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I suggest there should be a .boilerplate folder in the root of the repository. This contains packages.yml.
.boilerplate
packages.yml
Example of content in packages.yml:
"/.github/workflows": { <packages> } "/stacks/dev": { <packages> } "/stacks/prod": { <packages> }
All packages can be installed by navigating to an output folder:
/stacks/dev
/stacks/dev/app-chainlit
/stacks
/
../../../..
"repo1": "/.github/workflows": { <packages> } "repo2": "/stacks/dev": { <packages> } "repo2": "/stacks/prod": { <packages> }
.boilerplate/dev_terraform.yml
.boilerplate/prod_terraform.yml
.boilerplate/dev_github_actions.yml
The text was updated successfully, but these errors were encountered:
@haavardeide suggested having a shared super config file between IaC and App repo.
Sorry, something went wrong.
No branches or pull requests
I suggest there should be a
.boilerplate
folder in the root of the repository. This containspackages.yml
.Example of content in
packages.yml
:All packages can be installed by navigating to an output folder:
/stacks/dev
, everything in/stacks/dev
is installed or updated./stacks/dev/app-chainlit
, only that stack is installed or updated./stacks
or/
, everything will be installed or updated.Why
../../../..
in output paths.Other idea
Packages config files
.boilerplate/dev_terraform.yml
.boilerplate/prod_terraform.yml
.boilerplate/dev_github_actions.yml
The text was updated successfully, but these errors were encountered: