Spinnaker Operations: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
Line 39: | Line 39: | ||
<syntaxhighlight lang='bash'> | <syntaxhighlight lang='bash'> | ||
spin pipeline delete --name my-pipeline --application my-application | spin pipeline delete --name my-pipeline --application my-application | ||
</syntaxhighlight> | |||
==Insert a Stage into an Existing Pipeline== | |||
Use the JSON representation. Select the pipeline → Pipeline Actions → Edit as JSON → identity "stages" and introduce the JSON representation of the stage. | |||
<syntaxhighlight lang='json'> | |||
{ | |||
"name": "BreakPoint", | |||
"refId": "5", | |||
"requisiteStageRefIds": [ | |||
"4" | |||
], | |||
}, | |||
</syntaxhighlight> | </syntaxhighlight> | ||
Revision as of 04:12, 27 May 2022
Internal
CLI Access
Installation and Configuration
curl -LO https://storage.googleapis.com/spinnaker-artifacts/spin/$(curl -s https://storage.googleapis.com/spinnaker-artifacts/spin/latest)/darwin/amd64/spin
chmod +x spin
sudo mv spin /usr/local/bin/spin
Follow specific configuration instructions depending on the authentication method against the backend.
Options
-k|--insecure
Ignore certificate errors.
Operations
spin -k application list
Application Operations
Create an Application
Configure an Application
Pipeline Operations
List Pipelines
spin [-k] pipeline list --application my-application
Create a Pipeline
Delete a Pipeline
spin pipeline delete --name my-pipeline --application my-application
Insert a Stage into an Existing Pipeline
Use the JSON representation. Select the pipeline → Pipeline Actions → Edit as JSON → identity "stages" and introduce the JSON representation of the stage.
{
"name": "BreakPoint",
"refId": "5",
"requisiteStageRefIds": [
"4"
],
},
Blue-Green Deployments with Spinnaker
Running an Arbitrary Script
Log Management
TO INVESTIGATE: