https://github.com/cycloidio/bootstrap-stacks
Collection of stack templates to be used by customer to create simple functioning stack
https://github.com/cycloidio/bootstrap-stacks
Last synced: about 1 year ago
JSON representation
Collection of stack templates to be used by customer to create simple functioning stack
- Host: GitHub
- URL: https://github.com/cycloidio/bootstrap-stacks
- Owner: cycloidio
- Archived: true
- Created: 2023-03-22T13:25:37.000Z (about 3 years ago)
- Default Branch: master
- Last Pushed: 2024-05-20T12:52:47.000Z (about 2 years ago)
- Last Synced: 2025-02-28T17:54:43.797Z (over 1 year ago)
- Language: HCL
- Size: 47.9 KB
- Stars: 1
- Watchers: 4
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# boostrap-stacks
This is a collection of stack templates the users can use to create a small stacks to start using Cycloid.
## How does a template work
The difference from a normal stacks are the following:
- a template stack has in the `.config.yml` the field `template: true`
- you can use `pongo2` templates to conditionally alter the resulting stack
When the user creates a stack from template the BE will pass the following parameters:
- stack_usecase
- stack_author
- stack_canonical
- stack_path
- scs_canonical
- scs_cred_path
- scs_cred_type
- api_url
The relevant files will be rendered with the passed parameters and added to a resulting stack.
The relevant files are the following
- `.config.yml`, `.forms.yml` and `README.md` files
- all the files (not directories) under the `terraform`, `pipeline`, and `ansible` directories
- all the files that have the `stack_usecase` in their path
For example if the `stack_usecase` is `aws` the file `terraform-sample/terraform/aws/variables.tf` is rendered and included in the resulting stack.
While `terraform-sample/terraform/gcp/aws-migation.tf` will not since it is not directly under the `terrafor` directory and the usecase do not appear it the path to the file but in the filename.