Applying Changes in a stack
When a stack is deployed, it’s easy to modify the stack itself or only the configuration simply by doing modifications in git and pushing them to the repository.
To give an example: I want to change the instance type for my prod environment of my stack.
- Clone the config repository.
- Go in the terraform/prod sub directory of my stack.
- Modify the value
instance_type = 't2.micro'
- Commit the change
- Push it.
Then the pipeline should be triggered automatically by the push in git and you can follow each step in the pipeline. See Pipeline section.
Update a pipeline with Cycloid API from the template in git
If you are looking to use Cycloid API to update a running pipeline from the template in your git, this is an example of script to do it : update-pipeline.py
python refresh.py -u firstname.lastname@example.org -p mysecret -t pipeline.yml -v vars.yml -o my-organization --pipeline-name my-pipeline
my-organization: Is the organization cannonical than you can find in the console URL
my-pipeline: The name of the pipeline you want to update. Usually the pattern is
pipeline.yml: The pipeline template file located usually in the branch
pipelinein the git of the stack definition
vars.yml: The pipeline variables that you specified during the project creation using the wizard in the dashboard
I created a private stack but it is not displayed in the stack list
As described in Service catalog a stack is defined by a
Each time you add, remove or modify the
.cycloid.yml file of one of your stack, you have to go on your service catalogs page and hit the Refresh this repository button for the desired service catalog which contains this stack.