Users, contributors, and advocates solve together in the Spinnaker community. Explore our community pages to engage.
-
-{{< /blocks/cover >}}
-{{< blocks/section color="dark" >}}
-{{% blocks/feature icon="fa-comment-smile" title="Get Help" url="http://www.spinnaker.io/community/get-help" %}}
-Joining a community group or channel to get answers when you have a question or hit a snag.
-{{% /blocks/feature %}}
-{{% blocks/feature icon="fab fa-hands-helping" title="Get Involved!" url="http://www.spinnaker.io/community/get-involved" %}}
-Contribute to our global community by writing code or documentation, creating content, and speaking at or attending events.
-{{% /blocks/feature %}}
-{{% blocks/feature icon="fab fa-megaphone" title="Stay Informed!" url="http://www.spinnaker.io/community/stay-informed" %}}
-Hear about the latest Spinnaker releases and stats, and subscribe to our newsletter.
-{{% /blocks/feature %}}
-{{< /blocks/section >}}
diff --git a/content/en/community/get-help/governance/_index.md b/content/en/community/get-help/governance/_index.md
deleted file mode 100644
index 410f6cf8..00000000
--- a/content/en/community/get-help/governance/_index.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: "Governance"
-linkTitle: "Governance"
-weight: 2
-description:
----
diff --git a/content/en/community/get-involved/_index.md b/content/en/community/get-involved/_index.md
deleted file mode 100644
index e69de29b..00000000
diff --git a/content/en/community/get-involved/contributing/code/build-statuses/index.md b/content/en/community/get-involved/contributing/code/build-statuses/index.md
deleted file mode 100644
index 24dfd2bc..00000000
--- a/content/en/community/get-involved/contributing/code/build-statuses/index.md
+++ /dev/null
@@ -1,91 +0,0 @@
----
-title: Build Statuses
-sidebar:
- nav: community
-
-services:
- core:
- - clouddriver
- - deck
- # - deck-kayenta
- - echo
- - fiat
- - front50
- - gate
- - igor
- - kayenta
- - kork
- - orca
- - rosco
- - spinnaker-monitoring
- supporting:
- - halyard
- - keel
- - keiko
- - spin
- - spinnaker.github.io
- - spinnaker-gradle-project
- - swabbie
-
-
----
-
----
-title: "Build Statuses"
-linkTitle: "Build Statuses"
-weight: 2
-description: ""
-branches:
-- master
-- release-1.20.x
-- release-1.19.x
-- release-1.18.x
----
-
-[Build Cop Rotation History](https://github.com/spinnaker/spinnaker/issues?utf8=%E2%9C%93&q=is%3Aissue+label%3Abuild-cop-rotation)
-
-[Build Cop List of Responsibilities](https://www.spinnaker.io/community/contributing/nightly-builds/#build-cop)
-
-## Nightly and Release Integration Tests
-
-> You must be a member of the `build-cops` GitHub Team to access nightly and release integration tests.
-
-{% for branch in page.branches %}
- {%- capture subject -%}{{branch | capitalize}}{%- endcapture -%}
- {%- if branch == "master" -%}
- {%- capture job -%}Flow_BuildAndValidate{%- endcapture -%}
- {%- else -%}
- {%- capture job -%}Flow_BuildAndValidate_{{branch | remove: "release-" | replace: ".", "_"}}{%- endcapture -%}
- {%- endif -%}
-* [![{{branch}} Build Status](https://builds.spinnaker.io/buildStatus/icon?job={{job}}&subject={{subject}}){:style="height: 25px"}](https://builds.spinnaker.io/job/{{job}}/)
-{% endfor %}
-
-
-## Core Services
-
-Service | Branch | Status
-------- | ------ | ------
-{% for svc in page.services.core %}
- {%- for branch in page.branches -%}
- {%- if branch == "master" -%}
- {%- capture svcCol -%}**{{ svc | capitalize }}**{%- endcapture -%}
- {%- else -%}
- {%- capture svcCol -%}{%- endcapture -%}
- {%- endif -%}
- {%- capture altTxt -%}{{ svc | capitalize }} Build Status{%- endcapture -%}
- {%- capture githubStatusImg -%}https://github.com/spinnaker/{{svc}}/workflows/Branch%20Build/badge.svg?branch={{branch}}{%- endcapture -%}
- {%- capture githubLink -%}https://github.com/spinnaker/{{svc}}/actions?query=workflow%3A%22Branch+Build%22+branch%3A{{branch}}{%- endcapture -%}
-
- {{svcCol}} | `{{branch}}` | [![{{altTxt}}]({{githubStatusImg}}){:style="height: 25px"}]({{githubLink}})
-{% endfor %}{% endfor %}
-
-
-## Optional and Supporting Services
-
-{% for svc in page.services.supporting %}
- {% capture altTxt %}{{ svc | capitalize }} Build Status{% endcapture %}
- {% capture githubStatusImg %}https://github.com/spinnaker/{{svc}}/workflows/Branch%20Build/badge.svg{% endcapture %}
- {% capture githubLink %}https://github.com/spinnaker/{{svc}}/actions?query=workflow%3A%22Branch+Build%22+branch%3Amaster{% endcapture %}
-
- * {{svc | capitalize }} [![{{altTxt}}]({{githubStatusImg}}){:style="height: 25px"}]({{githubLink}})
-{% endfor %}
diff --git a/content/en/community/get-involved/gardening/Spinnaker-Garden-1C.jpg b/content/en/community/get-involved/gardening/Spinnaker-Garden-1C.jpg
deleted file mode 100644
index ee4c7339..00000000
Binary files a/content/en/community/get-involved/gardening/Spinnaker-Garden-1C.jpg and /dev/null differ
diff --git a/content/en/community/get-involved/gardening/_index.md b/content/en/community/get-involved/gardening/_index.md
deleted file mode 100644
index 1653b127..00000000
--- a/content/en/community/get-involved/gardening/_index.md
+++ /dev/null
@@ -1,32 +0,0 @@
----
-title: "Spinnaker Gardening Days #communityHack"
-linkTitle: "Spinnaker Gardening Days #communityHack"
-weight: 2
-description:
----
-
-_Welcome to the command center for Spinnaker Gardening Days, a community celebration and hackathon._
-{{< figure src="./Spinnaker-Garden-1C.jpg" >}}
-
-## Register
-[Register for Spinnaker Gardening Days](https://www.eventbrite.com/e/spinnaker-gardening-days-communityhack-tickets-97845696111) on Eventbrite to reserve your tickets.
-
-## Jump In!
-To attend Spinnaker Gardening Days, you'll need Zoom. See Zoom's ["Joining a Meeting" documentation](https://support.zoom.us/hc/en-us/articles/201362193-Joining-a-Meeting) to learn how to join.
-
-* Join the [__Gardening Central__ Zoom Room](https://armory.zoom.us/j/6807216019) to enter Spinnaker Gardening Days
-* Join [Spinnaker Slack](https://join.spinnaker.io) to chat in [event & team channels](slack-map.md). Visit __#gardening-general__, our main event channel.
-* [Master schedule](schedule.md)
-* [Slack map](slack-map.md)
-* [What to hack](what-to-hack.md)
-* [Hackathon logistics](hack-logistics.md)
-* [Development environments](dev-environment.md)
-* [Developing plugins](developing-plugins.md)
-* [Read about prizes](prizes.md)
-* [Spinnaker-hackathon Github organizaion](https://github.com/spinnaker-hackathon)
-* [Spinnaker Gardening repository](https://github.com/spinnaker-hackathon/gardening)
-
-
-## Guidelines
-1. No hate speech, put-downs, or sexual content allowed in hackathon meetings or channels. Keep it classy and remember, we all have the same intrinsic value.
-2. Don't be afraid to share your thoughts, ask for help in __#gardening-ineedhelp__, or try something new. This is a safe space!
diff --git a/content/en/community/get-involved/gardening/dev-environment.md b/content/en/community/get-involved/gardening/dev-environment.md
deleted file mode 100644
index 68bdcda9..00000000
--- a/content/en/community/get-involved/gardening/dev-environment.md
+++ /dev/null
@@ -1,226 +0,0 @@
----
-layout: single
-title: "Development Environments for Spinnaker Gardening Days"
-sidebar:
- nav: community
----
-
-## Overview
-
-What's the best environment Spinnaker development? How can you set up your workstation to debug a Spinnaker service? It depends! Consider these constraints when choosing your strategy:
-
-* __Locally available computing resources__: hosting Spinnaker services is memory intensive.
-* __Access and cost management for public clouds__: Spinnaker can be hosted in the cloud, where you'll pay for resources.
-* __Familiarity with Kubernetes__: you may use Kubernetes tools to manage your Spinnaker environment if you prefer.
-
-## Install Spinnaker
-First things first, to develop Spinnaker, you'll need a Spinnaker instance. To get that, you have options:
-* Install [Minnaker](https://github.com/armory/minnaker), a POC Spinnaker instance that runs in a Linux VM on your local machine, or in the cloud.
-* [Clone and install each Spinnaker service locally.](#classic-local-installation-method)
-* [Install Spinnaker to your Kubernetes cluster](#kubernetes-installation-methods), running in your cloud provider or private cloud of choice. Read more about the [Kubernetes & Docker method](#kubernetes-and-docker-method) below.
-
-## Minnaker method
-If you're not sure which method to choose, we suggest following [these instructions to install Minnaker](https://github.com/armory/minnaker) in your chosen environment. This simplifies installation steps, and uses lightweight Kubernetes [(K3S)](https://k3s.io/) under the hood. Install in a cloud VM or a local Ubuntu 18.04 VM.
-
-### Developing for Spinnaker With Minnaker (15m 26s)
-
-
-
-_Learn how to install Minnaker, set up remote SSH, and connect to the local VM instance via local Spinnaker service configuration. Use kubectl port forwarding to connect a local clone of Orca to Redis and Front50 in Minnaker. Test and debug Orca by setting a break point in the stage task and running the stage._
-
-### Set up local development environment
-1. Install your IDE. These instructions target [IntelliJ IDEA](https://www.jetbrains.com/idea/download/#section=mac).
-2. Git clone the [Spinnaker service(s)](https://github.com/spinnaker) you will debug or extend.
-3. Open the project in your IDE: File > Open > Select project folder > Click 'OK'.
-4. Build the project:
- - Open the 'Gradle' window and double-click the 'Build' task under Tasks > Builds. (If you don't see the 'Gradle' window, select View > Tool Windows > Gradle to open it.)
-
-#### __Next steps IF your Minnaker instance is running in the cloud__
-
-5. [Install NGROK](https://ngrok.com/download), a tunneling service. Run it to create a tunnel from the service to the Spinnaker instance:
- - Consult the [port mappings reference](/docs/reference/architecture/#port-mappings) to determine which ports to forward. Create tunnels for the service(s) you're running locally.
- - Execute `ngrok http ` e.g. `ngrok http 8089` for echo.
- - Copy the URL in the `Forwarding` output lines.
-6. Configure your Spinnaker instance to use the forwarded NGROK address(es).
- - Create a `.hal/default/profiles/spinnaker-local.yml` file.
- - Add service settings, or copy settings from `.hal/default/staging/spinnaker.yml` and delete unnecessary services. Read more on [custom service settings](/docs/reference/halyard/custom/#custom-service-settings).
- - Change the `baseURL` for the service to the copied NGROK endpoint.
-7. Configure the local service to communicate with the Spinnaker instance.
- - Copy the kubeconfig from Spinnaker `/etc/spinnaker/.kube/config` to your local machine (e.g. `/tmp/kubeconfig-minnaker`)
- - Update the kubeconfig clusters.cluster.server address to point to the external endpoint URL as in this snippet:
-
- ```
- apiVersion: v1
- clusters:
- - cluster:
- server: ec2-34-223-57-141.us-west-2.compute.amazonaws.com:6443
- ...
- ```
- - Make sure the security group on your VM allows port 6443.
- - Use `kubectl port-forward` to forward the services required. For example, if running echo locally, you'll need it to communicate with orca and front50:
- ```
- kubectl --kubeconfig config-minnaker -n spinnaker port-forward spin-orca-5f47b76f84-bvh98 8083:8083
- kubectl --kubeconfig config-minnaker -n spinnaker port-forward spin-front50-64ddf796bf-gznqj 8080:8080
- ```
-8. __Now you're ready to run and debug the service or services!__
-
-#### __Next steps IF your Minnaker instance is running locally__
-5. [Create a kubeconfig for your machine reference](http://docs.shippable.com/deploy/tutorial/create-kubeconfig-for-self-hosted-kubernetes-cluster/).
- - Create a skeleton kubeconfig and get the certificate for the cluster:
- `kubectl config view --flatten --minify`
- - Create a service account for the namespace: `serviceaccount`
- - Copy the token for the secret associated with the serviceaccount `kubectl describe secret`
- - Grant the service account - cluster-admin access `clusterrolebinding`
- - Update the `users.user` section of the `kubeconfig` by replacing `users.user.password` and `users.user.username` to `users.user.token`, where the token value is the secret value associated with the ServiceAccount.
- - Update the kubeconfig `clusters.cluster.server` address to point to the IP address of Minnaker on local machine: e.g. `192.168.123.128:6443`
- - Consult this example `kubeconfig` for reference:
- ```
-
- apiVersion: v1
- clusters:
- - cluster:
- certificate-authority-data:
- server: https://192.168.1.128:6443
- name: plugin.example.net
- contexts:
- - context:
- cluster: plugin.example.net
- user: spinnaker-sa
- name: plugin.example.net
- current-context: plugin.example.net
- kind: Config
- preferences: {}
- users:
- - name: spinnaker-sa
- user:
- token:
- ```
-6. Configure your Minnaker instance to forward ports to your local machine (gateway) via spinnaker-local.yml configuration.
- - Create a `.hal/default/profiles/spinnaker-local.yml` file.
- - Add service settings, or copy settings from `.hal/default/staging/spinnaker.yml` and delete unnecessary services. Read more on [custom service settings](/docs/reference/halyard/custom/#custom-service-settings).
- - Change the `baseURL` for the service to the default gateway IP Address including the port, e.g. `http://192.168.123.1:8083` for orca.
- - Consult the [port mappings reference](/docs/reference/architecture/#port-mappings) to determine which ports to forward.
-7. Configure the local service to communicate with the Spinnaker instance.
- - The `kubeconfig` you just created does part of the configuration.
- - Use `kubectl port-forward` to forward the services required. For example, if running Echo locally, you'll need it to communicate with Orca and Front50:
- - Option 1: Forward via Service:
- `kubectl` `--``kubeconfig config-minnaker -n spinnaker port-forward svc/spin-orca 8083:8083 &`
- `kubectl --kubeconfig config-minnaker -n spinnaker port-forward svc/spin-front50 8080:8080 &`
- - Option 2: Forward via Pod:
- `kubectl --kubeconfig config-minnaker -n spinnaker port-forward spin-orca-5f47b76f84-bvh98 8083:8083`
- `kubectl --kubeconfig config-minnaker -n spinnaker port-forward spin-front50-64ddf796bf-gznqj 8080:8080`
-8. __Now you're ready to run and debug the service or services!__
-
-## Classic local installation method
-Follow the [Getting Set Up](https://www.spinnaker.io/guides/developer/getting-set-up/) guide to install Spinnaker locally.
-
-## Kubernetes and Docker method:
-
-### Kubernetes installation methods
-_The instructions for this method are in beta. Pull requests welcome!_
-
-1. Install Spinnaker to a Kubernetes cluster. There are several ways to do this:
- - [Install Halyard in Docker](/docs/setup/install/halyard/#install-halyard-on-docker)
- - In your `docker run` command, mount the `.kube` directory to the container to allow you to modify `.kube` config files on your local machine and persist the changes inside the container:
- ```
- docker run -p 8084:8084 -p 9000:9000 \
- --name halyard --rm \
- -v ~/.hal:/home/spinnaker/.hal \
- -v ~/.kube:/home/spinnaker/.kube \
- -it \
- us-docker.pkg.dev/spinnaker-community/docker/halyard:stable
- ```
- - Use the [Spinnaker for Google Cloud Engine](https://cloud.google.com/docs/ci-cd/spinnaker/spinnaker-for-gcp) solution, which installs Spinnaker to Google Kubernetes Engine.
- - Consult the installation guide for [Amazon Kubernetes Service](https://aws.amazon.com/blogs/opensource/continuous-delivery-spinnaker-amazon-eks/)
- - Use the new [Spinnaker Operator](https://docs.armory.io/spinnaker/operator/#install-operator) to quickly install with `kubectl` commands.
- - Install the Operator in [cluster mode](https://docs.armory.io/spinnaker/operator/#installing-operator-in-cluster-mode)
- - Front50 won't start up successfully until you point Spinnaker to persistent storage, such as an S3 bucket. Update `deploy/spinnaker/basic/SpinnakerService.yml` as in this snippet:
- ```
- ...
- spinnakerConfig:
- config:
- persistentStorage:
- persistentStoreType: s3
- s3:
- bucket: mybucket
- rootFolder: front50
- version: 2.18.0
- ...
- ```
-
-2. Open a bash shell in the location where Halyard is installed.
- - If Halyard is running in Docker, run `docker exec -it halyard bash` to enter a shell.
-3. Edit the Kubernetes block of your .hal/config with your namespace and kubeconfig file location to enable a Kubernetes install, as in this snippet:
- ```
- ...
- kubernetes:
- enabled: true
- accounts:
- name: kubernetes
- requiredMembership: []
- permissions: []
- dockerRegistries: []
- configureImagePullSecrets: true
- cacheThreads: 1
- namespaces:
- -
- omitNamespaces: []
- kinds: []
- omitKinds: []
- customResources: []
- cachingPolicies: []
- kubeconfigFile:
- oAuthScopes: []
- onlySpinnakerManaged: false
- primaryAccount: kubernetes
- ...
- ```
-4. Port-forward the externally-hosted Spinnaker services to your local machine
- - You may use [NGROK](https://ngrok.com/download)
- - Or, try this Fish function: `pf-spinnaker` loops through all of the Spinnaker services in your Kubernetes namespaces and forwards their ports to your local machine. Try it:
- ```
- function pf-spinnaker
- set -l services (string split , -- \
- (kubectl get services -o json \
- | jq -r '.items[] | [.metadata.name, .spec.ports[0].port] | @csv'))
- set -l service_length (count $services)
- set -l current_service 1
- while test $current_service -lt $service_length
- set -l service (string replace --all '"' '' -- $services[$current_service])
- set -l port $services[(math $current_service + 1)]
- command kubectl port-forward "service/$service" $port &
- set current_service (math "$current_service+2")
- end
- end
- function kill-background
- jobs | tail -n"+1" | awk -F\ '{print $2}' | xargs -I"{}" kill "{}"
- end
- ```
- To tear down these port forwards (for example, when restarting a service), run this function from the same terminal that issued `pf-spinnaker`:
- ```
- function kill-background
- jobs | tail -n"+1" | awk -F\ '{print $2}' | xargs -I"{}" kill "{}"
- end
- ```
-5. Git clone the [Spinnaker service(s)](https://github.com/spinnaker) you will debug or extend.
-6. Hack!
-7. When you're ready to run integration tests, create a docker image with your local build. Read more [in this blog](https://aetas.pl/posts/2019-11-21-docker-image-with-gradle/).
-8. Tag the image and push it to Docker Hub, Artifactory, Docker Registry, or another artifact store.
-9. Edit the [service settings](https://www.spinnaker.io/reference/halyard/custom/#custom-service-settings) for your profile, in `~/.hal//service-settings/.yml`, e.g. `~/.hal/default/service-settings/echo.yml` to pull the container image into your Spinnaker instance:
- ```
- artifactId:
- kubernetes:
- imagePullSecrets:
- - artifactory-creds
- ```
- Include image pull secrets if the container is in a private repository like Artifactory.
-10. Run `hal deploy apply` inside the Halyard container to deploy your modified version of the service.
- - If using the `pf-spinnaker` Fish function to port-forward, run the `kill-background` function and then re-reun `pf-spinnaker` each time you restart a service.
-
-__Now you're ready to run and debug the service or services!__
-
-## Additional references
-* [This repository](https://github.com/robzienert/spinnaker-oss-setup) installs all Spinnaker dependencies besides the JDK to your machine running OSX. With a few tweaks and a package manager swap, you could also use it to automate dependency setup on Linux.
-
-## Help us improve the contributor experience
-This page is beta! Please submit a Pull Request.
diff --git a/content/en/community/get-involved/gardening/developing-plugins.md b/content/en/community/get-involved/gardening/developing-plugins.md
deleted file mode 100644
index d34c89c7..00000000
--- a/content/en/community/get-involved/gardening/developing-plugins.md
+++ /dev/null
@@ -1,37 +0,0 @@
----
-layout: single
-title: "Plugin Development at Spinnaker Gardening Days"
-sidebar:
- nav: community
----
-The Spinnaker plugin framework simplifies loading and managing third-party extensions. This makes it easier to extend and integrate with Spinnaker, and to share and evolve those extensions throughout their lifecycles. At this stage, the new plugin framework has a growing list of well-defined extension points. It's time for the community to begin leveraging those extension points to add functionality to Spinnaker, and to explore development of new extension points.
-
-## Intro to plugins assignment at Spinnaker Gardening Days
-
-To jump into Spinnaker plugins, start by creating a custom stage plugin. This will help you become familiar with the framework. For your first plugin project, we recommend that you use the new `SimpleStage` extension point to add your custom pipeline stage to Spinnaker. Read more in the [Plugin Creators Guide](https://www.spinnaker.io/guides/developer/plugin-creators/overview/).
-
-__Consult these guides to get started. Check this page for more plugin training videos, to be added soon!__
-
-### How to build a Plugin: Creating a Spinnaker-native custom stage (16m 55s)
-
-
-
-_The Spinnaker plugin framework leverages PF4J. This video focuses on extending functionality via stable, well-defined extension points. It demonstrates using the Orca stage extension point to add an example custom stage that waits a random amount of time as part of a Spinnaker pipeline. It also shows how to set up IntelliJ to debug plugins._
-
-### How to build a Plugin: Building the frontend for a Spinnaker-native custom stage (8m 56s)
-
-
-
-_This video focuses on creating a presentation layer for Deck using TypeScript and React. It discusses the frontend-backend interaction in a Spinnaker plugin and demonstrates what a native custom stage looks like in the Spinnaker UI._
-
-### How to build a PLUGIN: The build process for a Spinnaker plugin (4m 53s)
-
-
-
-This video focuses on the Gradle build process for packaging plugin development projects, using the custom stage plugin as an example.
-
-### How to build a PLUGIN: Delivering a plugin to your Spinnaker environment (10m 53s)
-
-
-
-This video focuses on delivering a plugin to a running Spinnaker instance for integration testing and beyond. It uses the custom stage plugin as an example.
diff --git a/content/en/community/get-involved/gardening/hack-logistics.md b/content/en/community/get-involved/gardening/hack-logistics.md
deleted file mode 100644
index 1fc8c36a..00000000
--- a/content/en/community/get-involved/gardening/hack-logistics.md
+++ /dev/null
@@ -1,26 +0,0 @@
----
-layout: single
-title: "Hackathon Logistics at Spinnaker Gardening Days"
-sidebar:
- nav: community
----
-Here's how we'll garden and hack together. Following these guidelines keeps you eligible for prizes and charitable donations, and sets us up for for maximum community impact.
-
-### Create a team Slack channel
-_Even if you're starting solo_, create a team channel for your project in [Spinnaker Slack](https://join.spinnaker.io). Use the format __#gardening-team-__+_projectString_ with a project string that describes your project and matches your repo name, if applicable.
-
-### Join project matchmaking
-The [Project Matchmaking session](https://armory.zoom.us/j/6807216019) at 8:40 AM PST on Thursday 4/9 will give teams and individuals the opportunity to pitch a project/task and recruit team members. Each spokesperson can take 90 seconds to pitch an idea and invite attendees to a Slack channel to discuss and organize.
-
-### Create repositories
-Starting fresh with some new plugin code, or writing a tutorial? Create all new project repositories in [Spinnaker-Hackathon](https://github.com/spinnaker-hackathon). Name your repo with a descriptive project string that you'll use in your Slack channel name. _Note: Your GitHub handle will be added as a member to the Spinnaker-Hackathon organization after check in. You must check in to receive repository creation privileges. Get the check-in link by joining the [Gardening Central](https://armory.zoom.us/j/6807216019) Zoom room._
-
-### Fork Spinnaker repositories
-Need to fork an existing Spinnaker project(s) to hack? Fork into the [Spinnaker-Hackathon](https://github.com/spinnaker-hackathon):
-![where to fork](/org-fork.png)
-When it's time to submit a pull request, do so from your fork. Read more on [best practices in fork & pull request workflows](https://gist.github.com/Chaser324/ce0505fbed06b947d962).
-
-### Use a Spinnaker staging environment
-When developing a Spinnaker plugin, it's useful to do integration testing in a running Spinnaker instance. This allows you to interact with the frontend. For this event, Armory will provide Spinnaker staging instances running in AWS for project teams to use as needed.
-
-_Look out for more details on how to gain access to a staging instance._
diff --git a/content/en/community/get-involved/gardening/org-fork.png b/content/en/community/get-involved/gardening/org-fork.png
deleted file mode 100644
index cb49c79d..00000000
Binary files a/content/en/community/get-involved/gardening/org-fork.png and /dev/null differ
diff --git a/content/en/community/get-involved/gardening/prizes.md b/content/en/community/get-involved/gardening/prizes.md
deleted file mode 100644
index c51fe55e..00000000
--- a/content/en/community/get-involved/gardening/prizes.md
+++ /dev/null
@@ -1,18 +0,0 @@
----
-layout: single
-title: "Prize Information"
-sidebar:
- nav: community
----
-_This page is under construction. Look out for more details soon as we validate our contribution data collection strategy!_
-
-Here's the prizing structure (we reserve the right to add mystery prizes to sweeten the deal!):
- - [Mavic Mini Fly More Kit](https://store.dji.com/product/mavic-mini?vid=84651), a fully-equipped lightweight camera drone
- - Enter a drawing to win by submitting a PR to a Spinnaker service or project while participating in Spinnaker Gardening
- - [Click 'N Grow Smart Garden 9](https://www.clickandgrow.com/products/the-smart-garden-9), plus seed quilts, for optimal urban or pandemic gardening
- - Win by leading a project team and recruiting team members from the community (hint: [start here](https://github.com/spinnaker-hackathon/gardening/wiki/Project-Ideas))
- - [Sphero Mini](https://www.sphero.com/sphero-mini) programmable robotic ball
- - Brand-new contributors, win by joining a project team, participating in the demo, and creating one or more contributions (PR/issue comments and issues count!) while participating in Spinnaker Gardening
- - Win a mystery prize by participating in a project demo : )
- - Win free lunch delivery, swag, and unlimited smiles
- - Win by showing up to Spinnaker Gardening
diff --git a/content/en/community/get-involved/gardening/schedule.md b/content/en/community/get-involved/gardening/schedule.md
deleted file mode 100644
index 1fdb14e3..00000000
--- a/content/en/community/get-involved/gardening/schedule.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-layout: single
-title: "Master Schedule for Spinnaker Gardening Days #communityHack"
-sidebar:
- nav: community
----
-## Schedule
-_This schedule is under construction. Look out for more activities to be added! Everyone is welcome to host an activity for 10 minutes or more. All times and topics that adhere to our guidelines are welcome! Ping in_ __#gardening-general__ _to be added to the schedule._
-
-
diff --git a/content/en/community/get-involved/gardening/slack-map.md b/content/en/community/get-involved/gardening/slack-map.md
deleted file mode 100644
index 33a4ff22..00000000
--- a/content/en/community/get-involved/gardening/slack-map.md
+++ /dev/null
@@ -1,30 +0,0 @@
----
-layout: single
-title: "Slack Channels @ Spinnaker Gardening Days"
-sidebar:
- nav: community
----
-## Slack Map
-Your guide to all the Gardening Slack channels in [Spinnaker Slack](https://join.spinnaker.io)
-
-
-|Slack Channel|Description|
-|-----|-----------------------|
-|[#gardening-general](https://spinnakerteam.slack.com/archives/CV4A90DPF)|General event chat|
-|[#gardening-ineedhelp](https://spinnakerteam.slack.com/archives/CURFZGL2E)|Event helpdesk|
-|#gardening-team-[projectString]|Team channels. projectString = repo name|
-|#gardening-idea-[projectString]|Brainstorming channels. projectString = repo name|
-|[#gardening-training](https://spinnakerteam.slack.com/archives/C011CAW95SP)|Training questions and discussion|
-|[#gardening-stackoverflow](https://spinnakerteam.slack.com/archives/C011CBGM2HH)|Share stackoverflow links for answer credit|
-|[#gardening-LOLs](https://spinnakerteam.slack.com/archives/C011W0LRLQY)|Share jokes and media to make each other laugh|
-|[#gardening-gamers](https://spinnakerteam.slack.com/archives/C011BMZ75LP)|Gamer chat|
-|[#gardening-rave](https://spinnakerteam.slack.com/archives/C011CCM24LT)|Dance party|
-|[#gardening-karaoke](https://spinnakerteam.slack.com/archives/C011MAKLSE8)|Karaoke!|
-|[#gardening-yoga-mindfulness](https://spinnakerteam.slack.com/archives/C011BMZFMKR)|Scheduled yoga & mindfulness breaks|
-|[#gardening-anonymous](https://spinnakerteam.slack.com/archives/C011BMZCS15)|Anonymous feedback|
-|[#spinnaker-tips](https://spinnakerteam.slack.com/archives/C011HAWD3M3)|Share Spinnaker tips for Spinnaker.io & Twitter mention |
-|[#spinnaker-news](https://spinnakerteam.slack.com/archives/C011W1CNW8Y)|Share Spinnaker news & blog content for April newsletter|
-|[#sig-documentation](https://spinnakerteam.slack.com/archives/CMPS49682)|Documentation SIG-hosted activities and chatter|
-|[#sig-kubernetes](https://spinnakerteam.slack.com/archives/C748G8U9J)|Kubernetes SIG-hosted chatter|
-|[#sig-ui](https://spinnakerteam.slack.com/archives/CH3FMKA3U)|UI SIG-hosted chatter|
-|[#sig-ci](https://spinnakerteam.slack.com/archives/CQJP8H05P)|CI SIG-hosted chatter|
diff --git a/content/en/community/get-involved/gardening/what-to-hack.md b/content/en/community/get-involved/gardening/what-to-hack.md
deleted file mode 100644
index 4d99084d..00000000
--- a/content/en/community/get-involved/gardening/what-to-hack.md
+++ /dev/null
@@ -1,39 +0,0 @@
----
-layout: single
-title: "Hackathon Activities at Spinnaker Gardening Days #communityHack"
-sidebar:
- nav: community
----
-
-## What to hack
-
-Not sure where to get started contributing to Spinnaker? May we suggest:
-
-* Join the [Project Matchmaking session](https://armory.zoom.us/j/6807216019) at 8:40 AM PST on Thursday 4/9, right after kickoff. Teams and individuals will take 90 seconds to pitch an idea and invite attendees to a Slack channel to organize.
-
-* Review the [Project Ideas Wiki](https://github.com/spinnaker-hackathon/gardening/wiki/Project-Ideas)for inspiration, then hop over Slack to discuss.
-
-* Visit the [list of beginner-friendly Spinnaker issues](https://github.com/spinnaker/spinnaker/issues?q=is%3Aopen+is%3Aissue+label%3A%22beginner+friendly%22+). Each issue has a Slack channel referencing the issue number (e.g. #gardening-team-issue-5357). Check the channel to collaborate.
-
-* Create a custom-stage plugin and familiarize yourself with using the framework. This uses the new SimpleStage extension point to add your custom pipeline stage to Spinnaker. Read more in the [Plugin Creators Guide](https://www.spinnaker.io/guides/developer/plugin-creators/).
-
-* Help make Spinnaker documentation easier to use. Participate in a spinnaker.io card sorting exercise asynchronously. Start [here](https://www.provenbyusers.com/cs.php?c=26cc8242). Stop by the #sig-documentation Slack channel if you have questions or want to chat!
-
-* Add quality answers to [questions tagged "Spinnaker" on StackOverflow](https://stackoverflow.com/questions/tagged/spinnaker). End your answers with the suggestion that users [join Spinnaker Slack](https://join.spinnaker.io). To have your answers counted as contributions, share question links in the __#gardening-stackoverflow__ channel and indicate your username.
-
-* Share a tip in #spinnaker-tips on [Spinnaker Slack](https://join.spinnaker.io) for a strong chance to be featured on our home page. Include your twitter handle for a mention!
-
-* Share a Spinnaker news item, tutorial, or tweet link in #spinnaker-news on [Spinnaker Slack](https://join.spinnaker.io) to help us build the next edition of [Flying, the Spinnaker Newsletter](/news/latest/). [Sign up for the newsletter](/news/), too!
-
-* Create a video or tutorial on something you know how to do in Spinnaker, even if it's really small. We have a great need for more short (1-5 minutes) training videos for Spinnaker, especially on the basics. [Cloudapp](https://www.getcloudapp.com/) is really useful for quickly making training videos.
-
-* Open issues, comment on issues and PRs to provide context, and review PRs in [the Spinnaker organization](https://github.com/spinnaker).
-
-* Set up a Spinnaker development environment as described [here](/community/gardening/dev-environment/) or using another method. Help us improve this documentation by opening issue(s) or submitting PRs to the [page](/community/gardening/dev-environment/).
-
-* Update library version dependencies. Ask in the #gardening-ineedhelp channel on [Spinnaker Slack](https://join.spinnaker.io) for guidance.
-
-* Run through a [Spinnaker codelab](/docs/guides/tutorials/codelabs/). Document and file any issues you encounter [here](https://github.com/spinnaker/spinnaker.github.io/issues/) when you come across them.
-
-* Drop in to `#sig-` channels and ask what they are working on to learn more.
-
diff --git a/content/en/community/stay-informed/_index.md b/content/en/community/stay-informed/_index.md
deleted file mode 100644
index e69de29b..00000000
diff --git a/content/en/community/stay-informed/releases/_index.md b/content/en/community/stay-informed/releases/_index.md
deleted file mode 100644
index 8bf6f91e..00000000
--- a/content/en/community/stay-informed/releases/_index.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: "Releases"
-linkTitle: "Releases"
-weight: 2
-description:
----
diff --git a/content/en/community/stay-informed/releases/next-release-preview/index.md b/content/en/community/stay-informed/releases/next-release-preview/index.md
deleted file mode 100644
index f2946efa..00000000
--- a/content/en/community/stay-informed/releases/next-release-preview/index.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: "Next Release Preview"
-linkTitle: "Next Release Preview"
-weight: 2
-description:
----
-
-Please make a pull request to describe any changes you wish to highlight
-in the next release of Spinnaker. These notes will be prepended to the release
-changelog.
-
-## Coming Soon in Release 1.23
-
-### (Breaking Change) Spinnaker Kubernetes manifest image overwriting with a bound artifact
-
-Spinnaker will now overwrite images in a manifest with a bound artifact if the
-input manifest's image has a tag on it. The previous behavior was that Spinnaker
-would only overwrite images in a manifest if the image did not have a tag.
-
-https://github.com/spinnaker/spinnaker/issues/5948
-
-### Kubernetes accounts no longer use the liveManifestCalls flag
-
-As of this release, Kubernetes accounts no longer read the value of the
-`liveManifestCalls` flag. Instead of using this flag, Spinnaker now decides
-whether to read from the cache or directly from the Kubernetes cluster based on
-the context of the request.
-
-From a practical perspective this means that:
-
-- Users who had `liveManifestCalls` enabled will see the same fast deploys as
- always but will no longer experience
- [bugs with dynamic target selection](https://github.com/spinnaker/spinnaker/issues/5607).
-- Users who had `liveManifestCalls` disabled will notice significantly faster
- deployments.
-
-Users may wish to remove the `liveManifestCalls` flag from their account
-configuration, though this is not required and any configured value for this
-setting will be ignored by Spinnaker.
-
-### Java 11 is Required
-
-Spinnaker now requires a Java 11 (or greater) runtime:
-- If you use the community Docker containers, these have been using Java 11 for several releases now. No changes are required.
-- If you are using the community Debian packages, you need to make sure a Java 11 runtime is available on your system.
-- If you're building your own Spinnaker binaries from source, you will need to use a Java 11 JDK.
\ No newline at end of file
diff --git a/content/en/docs/community/_index.md b/content/en/docs/community/_index.md
index e98409cf..4b57a8e0 100644
--- a/content/en/docs/community/_index.md
+++ b/content/en/docs/community/_index.md
@@ -1,38 +1,35 @@
---
-title: "Community"
-linkTitle: "Community"
+title: 'Community'
+linkTitle: 'Community'
weight: 2
description: >
The Spinnaker OSS project was started at Netflix. Now, it thrives on the contributions of the broader DevOps community who have adopted it as their Continuous Delivery tool.
---
-The Spinnaker OSS project was started at Netflix. Now, it thrives on the contributions of the broader DevOps community who have adopted it as their Continuous Delivery tool.
-
## Engage the community and get support
Here are some ways to engage the Spinnaker community and find help—join us!
### [Slack](http://join.spinnaker.io)
-Start here! Many Spinnaker contributors and users are active on the Spinnaker Slack. It's a great place to get answers to questions or start a discussion about a feature or topic. Good places to begin on Slack include the following channels:
+Start here! Many Spinnaker contributors and users are active on the Spinnaker Slack. It's a great place to get answers to questions or start a discussion about a feature or topic. Good places to begin on Slack include the following channels:
-* A Special Interest Group (SIG) channel if there is a relevant one. SIGs are groups that focus on specific topics, such as `#sig-security` or `#sig-documentation`. All SIG Slack channels start with the prefix `sig`.
-* A narrowly focused channel, such as #auth
-* [#general](https://spinnakerteam.slack.com/archives/C091CCWRJ) for general questions and discussion
-* [#dev](https://spinnakerteam.slack.com/archives/C0DPVDMQE) for help contributing to Spinnaker
-
+- A Special Interest Group (SIG) channel if there is a relevant one. SIGs are groups that focus on specific topics, such as `#sig-security` or `#sig-documentation`. All SIG Slack channels start with the prefix `sig`.
+- A narrowly focused channel, such as #auth
+- [#general](https://spinnakerteam.slack.com/archives/C091CCWRJ) for general questions and discussion
+- [#dev](https://spinnakerteam.slack.com/archives/C0DPVDMQE) for help contributing to Spinnaker
### [GitHub](https://github.com/spinnaker)
The Spinnaker org with repos for all the services and documentation. Come here to contribute to Spinnaker!
-
-After engaging with the community to work through a problem, we encourage you to help us improve Spinnaker. File an issue if appropriate or even submit a fix. Reasons you might file an issue include the following:
-* Your problem is due to a bug or limitation that is not documented
-* The documentation is confusing or missing
-* The behavior of a feature or field is unclear
+After engaging with the community to work through a problem, we encourage you to help us improve Spinnaker. File an issue if appropriate or even submit a fix. Reasons you might file an issue include the following:
+
+- Your problem is due to a bug or limitation that is not documented
+- The documentation is confusing or missing
+- The behavior of a feature or field is unclear
-You can file an issue [here](https://github.com/spinnaker/spinnaker/issues).
+You can file an issue [here](https://github.com/spinnaker/spinnaker/issues).
## Project Governance
@@ -42,120 +39,4 @@ You can read more about how you can get involved through project SIGs, roles, an
## Who's using Spinnaker?
-
-
- {% include spinnaker_user id="adevinta_user" %}
- {% include spinnaker_user id="airbnb_user" %}
- {% include spinnaker_user id="alto_user" %}
-
-
-
- {% include spinnaker_user id="armory_user" %}
- {% include spinnaker_user id="avast_user" %}
- {% include spinnaker_user id="box_user" %}
-
-
-
- {% include spinnaker_user id="capsilon_user" %}
- {% include spinnaker_user id="centeredge_user" %}
- {% include spinnaker_user id="cerner_user" %}
-
-
-
- {% include spinnaker_user id="chartboost_user" %}
- {% include spinnaker_user id="chime_user" %}
- {% include spinnaker_user id="cisco_user" %}
-
-
-
- {% include spinnaker_user id="clarivate_user" %}
- {% include spinnaker_user id="cleartax_in_user" %}
- {% include spinnaker_user id="cloudera_user" %}
-
-
-
- {% include spinnaker_user id="comcast_user" %}
- {% include spinnaker_user id="contaazul_user" %}
- {% include spinnaker_user id="dins_user" %}
-
-
-
- {% include spinnaker_user id="ep_user" %}
- {% include spinnaker_user id="getyourguide_user" %}
- {% include spinnaker_user id="gogo_user" %}
-
-
-
- {% include spinnaker_user id="google_user" %}
- {% include spinnaker_user id="glovo_user" %}
- {% include spinnaker_user id="grab_user" %}
-
-
-
- {% include spinnaker_user id="groundtruth_user" %}
- {% include spinnaker_user id="grubhub_user" %}
- {% include spinnaker_user id="informatica_user" %}
-
-
-
- {% include spinnaker_user id="jpmc_user" %}
- {% include spinnaker_user id="kenzan_user" %}
- {% include spinnaker_user id="launchdarkly_user" %}
-
-
-
- {% include spinnaker_user id="lookout_user" %}
- {% include spinnaker_user id="makerbot_user" %}
- {% include spinnaker_user id="mercari_user" %}
-
-
-
- {% include spinnaker_user id="mulesoft_user" %}
- {% include spinnaker_user id="nearpod_user" %}
- {% include spinnaker_user id="nest_user" %}
-
-
-
- {% include spinnaker_user id="netflix_user" %}
- {% include spinnaker_user id="opsmx_user" %}
- {% include spinnaker_user id="optimizely_user" %}
-
-
-
- {% include spinnaker_user id="patreon_user" %}
- {% include spinnaker_user id="plaid_user" %}
- {% include spinnaker_user id="plangrid_user" %}
-
-
-
- {% include spinnaker_user id="purestorage_user" %}
- {% include spinnaker_user id="redbox_user" %}
- {% include spinnaker_user id="smartthings_user" %}
-
-
-
- {% include spinnaker_user id="sap_user" %}
- {% include spinnaker_user id="schibsted_user" %}
- {% include spinnaker_user id="scopely_user" %}
-
-
-
- {% include spinnaker_user id="skuid_user" %}
- {% include spinnaker_user id="target_user" %}
- {% include spinnaker_user id="transunion_user" %}
-
-
-
- {% include spinnaker_user id="underarmour_user" %}
- {% include spinnaker_user id="uneeq_user" %}
- {% include spinnaker_user id="waze_user" %}
-
-
-
- {% include spinnaker_user id="weatherbug_user" %}
- {% include spinnaker_user id="xiaohongshu_user" %}
-
-
-
-
-
+{{< logos >}}
diff --git a/content/en/community/get-involved/contributing/_index.md b/content/en/docs/community/contributing/_index.md
similarity index 91%
rename from content/en/community/get-involved/contributing/_index.md
rename to content/en/docs/community/contributing/_index.md
index 9ae21a70..b712e9e0 100644
--- a/content/en/community/get-involved/contributing/_index.md
+++ b/content/en/docs/community/contributing/_index.md
@@ -1,7 +1,6 @@
---
-title: "Contributing"
-linkTitle: "Contributing"
-weight: 2
+title: 'Contributing'
+weight: 1
description:
---
@@ -23,4 +22,4 @@ For more details about the patch submission process, look at [How to submit a pa
Running Spinnaker locally on your machine is a great option for testing changes before submitting a pull request.
-Follow the [guide to setting up a dev environment](/docs/guides/developer/getting-set-up/) to get up and running.
+Follow the [guide to setting up a dev environment](/docs/guides/user/get-started/) to get up and running.
diff --git a/content/en/community/get-involved/contributing/code-of-conduct.md b/content/en/docs/community/contributing/code-of-conduct.md
similarity index 82%
rename from content/en/community/get-involved/contributing/code-of-conduct.md
rename to content/en/docs/community/contributing/code-of-conduct.md
index 0df8d236..8865d692 100644
--- a/content/en/community/get-involved/contributing/code-of-conduct.md
+++ b/content/en/docs/community/contributing/code-of-conduct.md
@@ -1,9 +1,8 @@
---
layout: single
-title: "Code Of Conduct"
-sidebar:
- nav: community
-aliases:
+title: 'Code Of Conduct'
+
+aliases:
- /docs/code-of-conduct
---
@@ -25,21 +24,21 @@ orientation.
Examples of behavior that contributes to creating a positive environment
include:
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
+- Using welcoming and inclusive language
+- Being respectful of differing viewpoints and experiences
+- Gracefully accepting constructive criticism
+- Focusing on what is best for the community
+- Showing empathy towards other community members
Examples of unacceptable behavior by participants include:
-* The use of sexualized language or imagery and unwelcome sexual attention or
-advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic
+- The use of sexualized language or imagery and unwelcome sexual attention or
+ advances
+- Trolling, insulting/derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or electronic
address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
+- Other conduct which could reasonably be considered inappropriate in a
professional setting
## Our responsibilities
diff --git a/content/en/docs/community/contributing/code/_index.md b/content/en/docs/community/contributing/code/_index.md
new file mode 100644
index 00000000..1f583bae
--- /dev/null
+++ b/content/en/docs/community/contributing/code/_index.md
@@ -0,0 +1,5 @@
+---
+title: 'Code'
+weight: 2
+description:
+---
diff --git a/content/en/community/get-involved/contributing/code/back-end-code.md b/content/en/docs/community/contributing/code/back-end-code.md
similarity index 100%
rename from content/en/community/get-involved/contributing/code/back-end-code.md
rename to content/en/docs/community/contributing/code/back-end-code.md
diff --git a/content/en/docs/community/contributing/code/build-statuses/index.md b/content/en/docs/community/contributing/code/build-statuses/index.md
new file mode 100644
index 00000000..689abec1
--- /dev/null
+++ b/content/en/docs/community/contributing/code/build-statuses/index.md
@@ -0,0 +1,52 @@
+---
+title: 'Build Statuses'
+linktitle: 'Build Statuses'
+weight: 1
+
+services:
+ core:
+ - clouddriver
+ - deck
+ # - deck-kayenta
+ - echo
+ - fiat
+ - front50
+ - gate
+ - igor
+ - kayenta
+ - kork
+ - orca
+ - rosco
+ - spinnaker-monitoring
+ supporting:
+ - halyard
+ - keel
+ - keiko
+ - spin
+ - spinnaker.github.io
+ - spinnaker-gradle-project
+ - swabbie
+
+branches:
+ - master
+ - release-1.26.x
+ - release-1.25.x
+ - release-1.24.x
+---
+
+[Build Cop Rotation History](https://github.com/spinnaker/spinnaker/issues?utf8=%E2%9C%93&q=is%3Aissue+label%3Abuild-cop-rotation)
+
+[Build Cop List of Responsibilities](../nightly-builds/#build-cop)
+
+## Nightly and Release Integration Tests
+
+> You must be a member of the `build-cops` GitHub Team to access nightly and release integration tests.
+> {{< buildStatus >}}
+
+## Core Services
+
+{{< coreServices >}}
+
+## Optional and Supporting Services
+
+{{< supportingServices >}}
diff --git a/content/en/community/get-involved/contributing/code/developer-guides/_index.md b/content/en/docs/community/contributing/code/developer-guides/_index.md
similarity index 50%
rename from content/en/community/get-involved/contributing/code/developer-guides/_index.md
rename to content/en/docs/community/contributing/code/developer-guides/_index.md
index f9b86e89..c2f62193 100644
--- a/content/en/community/get-involved/contributing/code/developer-guides/_index.md
+++ b/content/en/docs/community/contributing/code/developer-guides/_index.md
@@ -1,7 +1,6 @@
---
-title: "Developer How Tos"
-linkTitle: "Developer How Tos"
-weight: 2
+title: 'Developer How Tos'
+linkTitle: 'Developer How Tos'
description: >
Guides for developers and plugin creators.
---
diff --git a/content/en/community/get-involved/contributing/code/developer-guides/dev-env/_index.md b/content/en/docs/community/contributing/code/developer-guides/dev-env/_index.md
similarity index 100%
rename from content/en/community/get-involved/contributing/code/developer-guides/dev-env/_index.md
rename to content/en/docs/community/contributing/code/developer-guides/dev-env/_index.md
diff --git a/content/en/community/get-involved/contributing/code/developer-guides/dev-env/getting-set-up.md b/content/en/docs/community/contributing/code/developer-guides/dev-env/getting-set-up.md
similarity index 100%
rename from content/en/community/get-involved/contributing/code/developer-guides/dev-env/getting-set-up.md
rename to content/en/docs/community/contributing/code/developer-guides/dev-env/getting-set-up.md
diff --git a/content/en/community/get-involved/contributing/code/developer-guides/dev-env/kork-library.md b/content/en/docs/community/contributing/code/developer-guides/dev-env/kork-library.md
similarity index 100%
rename from content/en/community/get-involved/contributing/code/developer-guides/dev-env/kork-library.md
rename to content/en/docs/community/contributing/code/developer-guides/dev-env/kork-library.md
diff --git a/content/en/community/get-involved/contributing/code/developer-guides/dev-env/provider-setups/_index.md b/content/en/docs/community/contributing/code/developer-guides/dev-env/provider-setups/_index.md
similarity index 100%
rename from content/en/community/get-involved/contributing/code/developer-guides/dev-env/provider-setups/_index.md
rename to content/en/docs/community/contributing/code/developer-guides/dev-env/provider-setups/_index.md
diff --git a/content/en/community/get-involved/contributing/code/developer-guides/dev-env/provider-setups/aws-dev-setup.md b/content/en/docs/community/contributing/code/developer-guides/dev-env/provider-setups/aws-dev-setup.md
similarity index 100%
rename from content/en/community/get-involved/contributing/code/developer-guides/dev-env/provider-setups/aws-dev-setup.md
rename to content/en/docs/community/contributing/code/developer-guides/dev-env/provider-setups/aws-dev-setup.md
diff --git a/content/en/community/get-involved/contributing/code/developer-guides/extending/_index.md b/content/en/docs/community/contributing/code/developer-guides/extending/_index.md
similarity index 100%
rename from content/en/community/get-involved/contributing/code/developer-guides/extending/_index.md
rename to content/en/docs/community/contributing/code/developer-guides/extending/_index.md
diff --git a/content/en/community/get-involved/contributing/code/developer-guides/extending/crd-extensions.md b/content/en/docs/community/contributing/code/developer-guides/extending/crd-extensions.md
similarity index 100%
rename from content/en/community/get-involved/contributing/code/developer-guides/extending/crd-extensions.md
rename to content/en/docs/community/contributing/code/developer-guides/extending/crd-extensions.md
diff --git a/content/en/community/get-involved/contributing/code/developer-guides/extending/new-stage.md b/content/en/docs/community/contributing/code/developer-guides/extending/new-stage.md
similarity index 100%
rename from content/en/community/get-involved/contributing/code/developer-guides/extending/new-stage.md
rename to content/en/docs/community/contributing/code/developer-guides/extending/new-stage.md
diff --git a/content/en/community/get-involved/contributing/code/developer-guides/plugin-creators/_index.md b/content/en/docs/community/contributing/code/developer-guides/plugin-creators/_index.md
similarity index 100%
rename from content/en/community/get-involved/contributing/code/developer-guides/plugin-creators/_index.md
rename to content/en/docs/community/contributing/code/developer-guides/plugin-creators/_index.md
diff --git a/content/en/community/get-involved/contributing/code/developer-guides/plugin-creators/overview.md b/content/en/docs/community/contributing/code/developer-guides/plugin-creators/overview.md
similarity index 100%
rename from content/en/community/get-involved/contributing/code/developer-guides/plugin-creators/overview.md
rename to content/en/docs/community/contributing/code/developer-guides/plugin-creators/overview.md
diff --git a/content/en/community/get-involved/contributing/code/developer-guides/plugin-creators/project-config.md b/content/en/docs/community/contributing/code/developer-guides/plugin-creators/project-config.md
similarity index 100%
rename from content/en/community/get-involved/contributing/code/developer-guides/plugin-creators/project-config.md
rename to content/en/docs/community/contributing/code/developer-guides/plugin-creators/project-config.md
diff --git a/content/en/community/get-involved/contributing/code/developer-guides/plugin-creators/stage-plugin-walkthrough.md b/content/en/docs/community/contributing/code/developer-guides/plugin-creators/stage-plugin-walkthrough.md
similarity index 100%
rename from content/en/community/get-involved/contributing/code/developer-guides/plugin-creators/stage-plugin-walkthrough.md
rename to content/en/docs/community/contributing/code/developer-guides/plugin-creators/stage-plugin-walkthrough.md
diff --git a/content/en/community/get-involved/contributing/code/developer-guides/service-overviews/_index.md b/content/en/docs/community/contributing/code/developer-guides/service-overviews/_index.md
similarity index 100%
rename from content/en/community/get-involved/contributing/code/developer-guides/service-overviews/_index.md
rename to content/en/docs/community/contributing/code/developer-guides/service-overviews/_index.md
diff --git a/content/en/community/get-involved/contributing/code/developer-guides/service-overviews/orca.md b/content/en/docs/community/contributing/code/developer-guides/service-overviews/orca.md
similarity index 100%
rename from content/en/community/get-involved/contributing/code/developer-guides/service-overviews/orca.md
rename to content/en/docs/community/contributing/code/developer-guides/service-overviews/orca.md
diff --git a/content/en/community/get-involved/contributing/code/managing-deprecations.md b/content/en/docs/community/contributing/code/managing-deprecations.md
similarity index 100%
rename from content/en/community/get-involved/contributing/code/managing-deprecations.md
rename to content/en/docs/community/contributing/code/managing-deprecations.md
diff --git a/content/en/community/get-involved/contributing/code/nightly-builds/index.md b/content/en/docs/community/contributing/code/nightly-builds/index.md
similarity index 100%
rename from content/en/community/get-involved/contributing/code/nightly-builds/index.md
rename to content/en/docs/community/contributing/code/nightly-builds/index.md
diff --git a/content/en/community/get-involved/contributing/code/nightly-builds/troubleshooting - base - 10 - flow.png b/content/en/docs/community/contributing/code/nightly-builds/troubleshooting - base - 10 - flow.png
similarity index 100%
rename from content/en/community/get-involved/contributing/code/nightly-builds/troubleshooting - base - 10 - flow.png
rename to content/en/docs/community/contributing/code/nightly-builds/troubleshooting - base - 10 - flow.png
diff --git a/content/en/community/get-involved/contributing/code/nightly-builds/troubleshooting - base - 20 - mostRecent.png b/content/en/docs/community/contributing/code/nightly-builds/troubleshooting - base - 20 - mostRecent.png
similarity index 100%
rename from content/en/community/get-involved/contributing/code/nightly-builds/troubleshooting - base - 20 - mostRecent.png
rename to content/en/docs/community/contributing/code/nightly-builds/troubleshooting - base - 20 - mostRecent.png
diff --git a/content/en/community/get-involved/contributing/code/nightly-builds/troubleshooting - base - 30 - phase.png b/content/en/docs/community/contributing/code/nightly-builds/troubleshooting - base - 30 - phase.png
similarity index 100%
rename from content/en/community/get-involved/contributing/code/nightly-builds/troubleshooting - base - 30 - phase.png
rename to content/en/docs/community/contributing/code/nightly-builds/troubleshooting - base - 30 - phase.png
diff --git a/content/en/community/get-involved/contributing/code/nightly-builds/troubleshooting - build - 10 - consoleOutput.png b/content/en/docs/community/contributing/code/nightly-builds/troubleshooting - build - 10 - consoleOutput.png
similarity index 100%
rename from content/en/community/get-involved/contributing/code/nightly-builds/troubleshooting - build - 10 - consoleOutput.png
rename to content/en/docs/community/contributing/code/nightly-builds/troubleshooting - build - 10 - consoleOutput.png
diff --git a/content/en/community/get-involved/contributing/code/nightly-builds/troubleshooting - build - 20 - buildSteps.png b/content/en/docs/community/contributing/code/nightly-builds/troubleshooting - build - 20 - buildSteps.png
similarity index 100%
rename from content/en/community/get-involved/contributing/code/nightly-builds/troubleshooting - build - 20 - buildSteps.png
rename to content/en/docs/community/contributing/code/nightly-builds/troubleshooting - build - 20 - buildSteps.png
diff --git a/content/en/community/get-involved/contributing/code/nightly-builds/troubleshooting - build - 30 - failedOutput.png b/content/en/docs/community/contributing/code/nightly-builds/troubleshooting - build - 30 - failedOutput.png
similarity index 100%
rename from content/en/community/get-involved/contributing/code/nightly-builds/troubleshooting - build - 30 - failedOutput.png
rename to content/en/docs/community/contributing/code/nightly-builds/troubleshooting - build - 30 - failedOutput.png
diff --git a/content/en/community/get-involved/contributing/code/nightly-builds/troubleshooting - test - 10 - testResultsOverview.png b/content/en/docs/community/contributing/code/nightly-builds/troubleshooting - test - 10 - testResultsOverview.png
similarity index 100%
rename from content/en/community/get-involved/contributing/code/nightly-builds/troubleshooting - test - 10 - testResultsOverview.png
rename to content/en/docs/community/contributing/code/nightly-builds/troubleshooting - test - 10 - testResultsOverview.png
diff --git a/content/en/community/get-involved/contributing/code/nightly-builds/troubleshooting - test - 20 - failingTest.png b/content/en/docs/community/contributing/code/nightly-builds/troubleshooting - test - 20 - failingTest.png
similarity index 100%
rename from content/en/community/get-involved/contributing/code/nightly-builds/troubleshooting - test - 20 - failingTest.png
rename to content/en/docs/community/contributing/code/nightly-builds/troubleshooting - test - 20 - failingTest.png
diff --git a/content/en/community/get-involved/contributing/code/nightly-builds/troubleshooting - test - 30 - failingStep.png b/content/en/docs/community/contributing/code/nightly-builds/troubleshooting - test - 30 - failingStep.png
similarity index 100%
rename from content/en/community/get-involved/contributing/code/nightly-builds/troubleshooting - test - 30 - failingStep.png
rename to content/en/docs/community/contributing/code/nightly-builds/troubleshooting - test - 30 - failingStep.png
diff --git a/content/en/community/get-involved/contributing/code/nightly-builds/troubleshooting - test - 40 - failingDetails.png b/content/en/docs/community/contributing/code/nightly-builds/troubleshooting - test - 40 - failingDetails.png
similarity index 100%
rename from content/en/community/get-involved/contributing/code/nightly-builds/troubleshooting - test - 40 - failingDetails.png
rename to content/en/docs/community/contributing/code/nightly-builds/troubleshooting - test - 40 - failingDetails.png
diff --git a/content/en/community/get-involved/contributing/code/releasing/commit.png b/content/en/docs/community/contributing/code/releasing/commit.png
similarity index 100%
rename from content/en/community/get-involved/contributing/code/releasing/commit.png
rename to content/en/docs/community/contributing/code/releasing/commit.png
diff --git a/content/en/community/get-involved/contributing/code/releasing/index.md b/content/en/docs/community/contributing/code/releasing/index.md
similarity index 100%
rename from content/en/community/get-involved/contributing/code/releasing/index.md
rename to content/en/docs/community/contributing/code/releasing/index.md
diff --git a/content/en/community/get-involved/contributing/code/releasing/patch.png b/content/en/docs/community/contributing/code/releasing/patch.png
similarity index 100%
rename from content/en/community/get-involved/contributing/code/releasing/patch.png
rename to content/en/docs/community/contributing/code/releasing/patch.png
diff --git a/content/en/community/get-involved/contributing/docs/docs-style-guide.md b/content/en/docs/community/contributing/docs/docs-style-guide.md
similarity index 100%
rename from content/en/community/get-involved/contributing/docs/docs-style-guide.md
rename to content/en/docs/community/contributing/docs/docs-style-guide.md
diff --git a/content/en/community/get-involved/contributing/docs/github-changes.md b/content/en/docs/community/contributing/docs/github-changes.md
similarity index 100%
rename from content/en/community/get-involved/contributing/docs/github-changes.md
rename to content/en/docs/community/contributing/docs/github-changes.md
diff --git a/content/en/community/get-involved/contributing/docs/index.md b/content/en/docs/community/contributing/docs/index.md
similarity index 72%
rename from content/en/community/get-involved/contributing/docs/index.md
rename to content/en/docs/community/contributing/docs/index.md
index fce455f9..8a037c77 100644
--- a/content/en/community/get-involved/contributing/docs/index.md
+++ b/content/en/docs/community/contributing/docs/index.md
@@ -1,6 +1,6 @@
---
-title: "Docs"
-linkTitle: "Docs"
+title: 'Docs'
+linkTitle: 'Docs'
weight: 2
description:
---
@@ -15,14 +15,14 @@ Bugs affecting more than one service commonly surface only when the whole system
The **build cop** responsibilities include:
-* Triage integration test failures on `master` and the 3 most recent release branches
-* [Clean up](#cleaning-orphaned-resources) orphaned resources across target cloud providers
-* Route [new GitHub issues](https://github.com/spinnaker/spinnaker/issues) to the appropriate SIG
+- Triage integration test failures on `master` and the 3 most recent release branches
+- [Clean up](#cleaning-orphaned-resources) orphaned resources across target cloud providers
+- Route [new GitHub issues](https://github.com/spinnaker/spinnaker/issues) to the appropriate SIG
(applying GitHub labels as appropriate). You can find the full list of SIGs in the
[governance repo](https://github.com/spinnaker/governance/blob/master/sig-index.md)
-* Observe any systemic problems raised in the [#general](https://spinnakerteam.slack.com/messages/general/)
+- Observe any systemic problems raised in the [#general](https://spinnakerteam.slack.com/messages/general/)
and [#dev](https://spinnakerteam.slack.com/messages/dev/) Slack channels
-* Log observations and corrective actions taken in the [rotation log](https://docs.google.com/document/d/1T0kifZ0C7zSIKOy2McKfmDnwvmRuU5Z3t81Tly6kH1M/edit#)
+- Log observations and corrective actions taken in the [rotation log](https://docs.google.com/document/d/1T0kifZ0C7zSIKOy2McKfmDnwvmRuU5Z3t81Tly6kH1M/edit#)
## Process Structure
@@ -40,12 +40,16 @@ As its name implies, `Flow_BuildAndValidate` builds and tests the whole Spinnake
1. Constructs a BOM from the most recent commit on the target branch
1. Builds a Docker container and a Debian package of each Spinnaker microservice.
1. Builds additional supporting artifacts:
- * `halyard`
- * `spin-cli`
- * Changelog
+
+- `halyard`
+- `spin-cli`
+- Changelog
+
1. Publishes the BOM under the following names:
- * _With the floating tag:_ `-latest-unvalidated` (e.g. `master-latest-unvalidated`)
- * _With a fixed tag:_ `-` (e.g. `master-20191213154039`)
+
+- _With the floating tag:_ `-latest-unvalidated` (e.g. `master-latest-unvalidated`)
+- _With a fixed tag:_ `-` (e.g. `master-20191213154039`)
+
1. Publishes the [changelog](https://gist.github.com/spinnaker-release/4f8cd09490870ae9ebf78be3be1763ee)
### 2. [Validate_BomAndReportMultiPlatform](https://builds.spinnaker.io/job/Validate_BomAndReportMultiPlatform/)
@@ -61,24 +65,25 @@ Spinnaker works whether deployed as a single VM or in a Kubernetes cluster, for
1. Connects to this instance and executes a series of `hal config` steps, including account setup for the managed cloud provider(s).
1. Deploys the configuration with `hal deploy apply`.
1. Invokes [`citest`](https://github.com/google/citest) integration tests against the new Spinnaker instance.
- * `citest` invokes a command to Spinnaker, and then uses the underlying cloud provider's CLI to confirm the expected changes were made. For example, using `gcloud` to confirm a GCE server group was created or deleted.
+ - `citest` invokes a command to Spinnaker, and then uses the underlying cloud provider's CLI to confirm the expected changes were made. For example, using `gcloud` to confirm a GCE server group was created or deleted.
## Cleaning Orphaned Resources
Occasionally, integration tests fail in a way that is either undesirable or difficult to automatically clean up. Build cops should periodically ensure these orphaned resources are deleted from the following locations:
-* [`spinnaker-community` GCP project](https://console.cloud.google.com/home/dashboard?organizationId=912934373776&project=spinnaker-community)
- * [Instance Groups](https://console.cloud.google.com/compute/instanceGroups/list?organizationId=912934373776&project=spinnaker-community&instanceGroupsTablesize=50&instanceGroupsTablequery=%255B%257B_22k_22_3A_22name_22_2C_22t_22_3A10_2C_22v_22_3A_22_5C_22gcp*_5C_22_22%257D%255D) named `gcp-*`
- * [VMs](https://console.cloud.google.com/compute/instances?organizationId=912934373776&project=spinnaker-community&instancessize=50&instancesquery=%255B%257B_22k_22_3A_22name_22_2C_22t_22_3A10_2C_22v_22_3A_22_5C_22jenkins-validate-bom*_5C_22_22%257D%255D) named `jenkins-validate-bom-*`
- * [Load balancers](https://console.cloud.google.com/net-services/loadbalancing/loadBalancers/list?project=spinnaker-community&organizationId=912934373776&filter=%255B%257B_22k_22_3A_22Name_22_2C_22t_22_3A10_2C_22v_22_3A_22_5C_22gcp*_5C_22_22%257D%255D) named `gcp-*`
- * [Managed certificates](https://console.cloud.google.com/net-services/loadbalancing/advanced/sslCertificates/list?project=spinnaker-community&organizationId=912934373776&sslCertificateTablesize=50&sslCertificateTablequery=%255B%257B_22k_22_3A_22domain_22_2C_22t_22_3A10_2C_22v_22_3A_22_5C_22localhost_5C_22_22%257D%255D) that are _**not**_ `builds.spinnaker.io` (!)
+- [`spinnaker-community` GCP project](https://console.cloud.google.com/home/dashboard?organizationId=912934373776&project=spinnaker-community)
+ - [Instance Groups](https://console.cloud.google.com/compute/instanceGroups/list?organizationId=912934373776&project=spinnaker-community&instanceGroupsTablesize=50&instanceGroupsTablequery=%255B%257B_22k_22_3A_22name_22_2C_22t_22_3A10_2C_22v_22_3A_22_5C_22gcp*_5C_22_22%257D%255D) named `gcp-*`
+ - [VMs](https://console.cloud.google.com/compute/instances?organizationId=912934373776&project=spinnaker-community&instancessize=50&instancesquery=%255B%257B_22k_22_3A_22name_22_2C_22t_22_3A10_2C_22v_22_3A_22_5C_22jenkins-validate-bom*_5C_22_22%257D%255D) named `jenkins-validate-bom-*`
+ - [Load balancers](https://console.cloud.google.com/net-services/loadbalancing/loadBalancers/list?project=spinnaker-community&organizationId=912934373776&filter=%255B%257B_22k_22_3A_22Name_22_2C_22t_22_3A10_2C_22v_22_3A_22_5C_22gcp*_5C_22_22%257D%255D) named `gcp-*`
+ - [Managed certificates](https://console.cloud.google.com/net-services/loadbalancing/advanced/sslCertificates/list?project=spinnaker-community&organizationId=912934373776&sslCertificateTablesize=50&sslCertificateTablequery=%255B%257B_22k_22_3A_22domain_22_2C_22t_22_3A10_2C_22v_22_3A_22_5C_22localhost_5C_22_22%257D%255D) that are _**not**_ `builds.spinnaker.io` (!)
## Deleting Obsolete Artifacts
The following jobs assist in removing old artifacts created during the build process:
-* [Admin_DailyJanitor](https://builds.spinnaker.io/view/5%20Admin/job/Admin_DailyJanitor/)
-* [Admin_AuditBoms](https://builds.spinnaker.io/view/5%20Admin/job/Admin_AuditBoms/)
-* [Admin_DeleteObsoleteArtifacts](https://builds.spinnaker.io/view/5%20Admin/job/Admin_DeleteObsoleteArtifacts/)
+
+- [Admin_DailyJanitor](https://builds.spinnaker.io/view/5%20Admin/job/Admin_DailyJanitor/)
+- [Admin_AuditBoms](https://builds.spinnaker.io/view/5%20Admin/job/Admin_AuditBoms/)
+- [Admin_DeleteObsoleteArtifacts](https://builds.spinnaker.io/view/5%20Admin/job/Admin_DeleteObsoleteArtifacts/)
## Troubleshooting Playbook
@@ -86,29 +91,29 @@ Check whether the failure happened during the _build_ or the _test_ phase:
1. Click the failing Flow.
- ![](troubleshooting - base - 10 - flow.png)
+ ![](troubleshooting - base - 10 - flow.png)
1. Click for the most recent failing build.
- ![](troubleshooting - base - 20 - mostRecent.png)
+ ![](troubleshooting - base - 20 - mostRecent.png)
1. Click through to the failing phase.
- ![](troubleshooting - base - 30 - phase.png)
+ ![](troubleshooting - base - 30 - phase.png)
### Build Failures
-1. The build phase uses many subshells to perform its work in parallel. Use the `Console Output`
-to help narrow down which step of the build has failed, and use the collected logs to view more information
-on what specificially went wrong.
+1. The build phase uses many subshells to perform its work in parallel. Use the `Console Output`
+ to help narrow down which step of the build has failed, and use the collected logs to view more information
+ on what specificially went wrong.
- ![](troubleshooting - build - 10 - consoleOutput.png)
+ ![](troubleshooting - build - 10 - consoleOutput.png)
-1. The Console Output prints out after each completion how much work is still remaining.
+1. The Console Output prints out after each completion how much work is still remaining.
![](troubleshooting - build - 20 - buildSteps.png)
-1. Frequently, the build error will be printed out directly to the Console Output, but sometimes this output can be hard to read. View the raw file directly using the Build Artifacts link from Step 1.
+1. Frequently, the build error will be printed out directly to the Console Output, but sometimes this output can be hard to read. View the raw file directly using the Build Artifacts link from Step 1.
![](troubleshooting - build - 30 - failedOutput.png)
@@ -128,15 +133,15 @@ Follow these steps to delete the artifact and resolve the issue:
repository](https://bintray.com/beta/#/spinnaker-releases/jars?tab=packages)
1. Click on the Spinnaker repository that had the failure. (If you don't see
-it, click to the next page; there are only 10 items per page for some reason.)
+ it, click to the next page; there are only 10 items per page for some reason.)
1. Click on the specific version that had the issue.
-1. Click "Actions" in the upper right and select "Edit".
+1. Click "Actions" in the upper right and select "Edit".
1. On the next page, click the "Delete" link in the upper right. It
-will look like nothing happened, but after 10 seconds or so, the page will
-refresh and the version will be gone.
+ will look like nothing happened, but after 10 seconds or so, the page will
+ refresh and the version will be gone.
Now that the conflict has been removed, you can restart the build.
@@ -144,19 +149,19 @@ Now that the conflict has been removed, you can restart the build.
1. View the Test Results Overview.
- ![](troubleshooting - test - 10 - testResultsOverview.png)
+ ![](troubleshooting - test - 10 - testResultsOverview.png)
1. Identify the failing test.
- ![](troubleshooting - test - 20 - failingTest.png)
+ ![](troubleshooting - test - 20 - failingTest.png)
1. Identify which step in the test is failing.
- ![](troubleshooting - test - 30 - failingStep.png)
+ ![](troubleshooting - test - 30 - failingStep.png)
1. It can sometimes help to view the last call that was made prior to that stage failing.
- ![](troubleshooting - test - 40 - failingDetails.png)
+ ![](troubleshooting - test - 40 - failingDetails.png)
### Connecting to the Jenkins VM
diff --git a/content/en/community/get-involved/contributing/docs/reviewing-prs.md b/content/en/docs/community/contributing/docs/reviewing-prs.md
similarity index 100%
rename from content/en/community/get-involved/contributing/docs/reviewing-prs.md
rename to content/en/docs/community/contributing/docs/reviewing-prs.md
diff --git a/content/en/community/get-involved/contributing/local-clone.md b/content/en/docs/community/contributing/local-clone.md
similarity index 84%
rename from content/en/community/get-involved/contributing/local-clone.md
rename to content/en/docs/community/contributing/local-clone.md
index 60be9f30..97e4c71c 100644
--- a/content/en/community/get-involved/contributing/local-clone.md
+++ b/content/en/docs/community/contributing/local-clone.md
@@ -1,11 +1,9 @@
---
layout: single
title: Make a Change Using a Local Clone
-sidebar:
- nav: community
---
-To make significant changes to a Spinnaker service or other repository, you can fork the repository and work from a local clone. The workflow below walks through a change to the `spinnaker/spinnaker.io` repository as an example, but a fork-and-pull-request workflow should be used for all Spinnaker contributions. Make sure you have [git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git) installed on your computer and have configured your GitHub account. See the [GitHub Help](https://help.github.com) for details.
+To make significant changes to a Spinnaker service or other repository, you can fork the repository and work from a local clone. The workflow below walks through a change to the `spinnaker/spinnaker.io` repository as an example, but a fork-and-pull-request workflow should be used for all Spinnaker contributions. Make sure you have [git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git) installed on your computer and have configured your GitHub account. See the [GitHub Help](https://help.github.com) for details.
## Fork the repository
@@ -47,27 +45,27 @@ To make significant changes to a Spinnaker service or other repository, you can
Make sure your local repository is current before you start making changes. Fetch commits from your fork's `origin/master` and `spinnaker/spinnaker.io`'s `upstream/master`:
- ```bash
- git fetch origin
- git fetch upstream
- ```
+```bash
+git fetch origin
+git fetch upstream
+```
## Create a working branch
1. Make sure you are in your `master` branch before you create your working
-branch. You can use `git branch` to see which branch you are in.
+ branch. You can use `git branch` to see which branch you are in.
- ```bash
- git branch
- ```
+ ````bash
+ git branch
+ ```
- The output lists your local branches. There is an `*` next to the branch you are in.
+ The output lists your local branches. There is an `*` next to the branch you are in.
- ```bash
+ ```bash
working-branch-1
working-branch-2
* master
- ```
+ ````
If you are not in `master`, execute `git checkout master` to go to your `master` branch. See the [Understanding history: What is a branch?](https://git-scm.com/docs/user-manual#what-is-a-branch) section of the _Git User Manual_ for more information.
@@ -77,9 +75,9 @@ branch. You can use `git branch` to see which branch you are in.
git checkout -b upstream/master
```
- Since `git` tracks changes to `upstream\master`, you don't need to rebase your fork before you create a working branch.
+ Since `git` tracks changes to `upstream\master`, you don't need to rebase your fork before you create a working branch.
-1. Make your changes.
+1. Make your changes.
Use the `git status` command at any time to see what files you've changed.
@@ -173,9 +171,9 @@ hugo server
Congratulations! You can view your submitted pull request on the **Pull requests** [tab](https://github.com/spinnaker/spinnaker.io/pulls).
->Do not delete your working branch until your pull request has been merged! You may need to update your content based on reviewer feedback.
+> Do not delete your working branch until your pull request has been merged! You may need to update your content based on reviewer feedback.
-When you look at your PR, you may see a **This branch is out-of-date with the base branch** message. This means approvers merged PRs while you were working on your changes. If you see a **Merge conflict** message, you need to [rebase your PR](#merge-conflicts-and-rebasing).
+When you look at your PR, you may see a **This branch is out-of-date with the base branch** message. This means approvers merged PRs while you were working on your changes. If you see a **Merge conflict** message, you need to [rebase your PR](#merge-conflicts-and-rebasing).
## Addressing feedback locally
@@ -240,11 +238,11 @@ If another contributor commits changes to the same file in another PR, it can cr
git status
```
- This results in a number of files marked as conflicted.
+This results in a number of files marked as conflicted.
1. Open each conflicted file and look for the conflict markers: `>>>`, `<<<`, and `===`. Resolve the conflict and delete the conflict marker.
- >For more information, see [How conflicts are presented](https://git-scm.com/docs/git-merge#_how_conflicts_are_presented).
+ > For more information, see [How conflicts are presented](https://git-scm.com/docs/git-merge#_how_conflicts_are_presented).
1. Add the files to the changeset:
@@ -252,15 +250,15 @@ If another contributor commits changes to the same file in another PR, it can cr
git add
```
-1. Continue the rebase:
+1. Continue the rebase:
- ```bash
- git rebase --continue
- ```
+```bash
+git rebase --continue
+```
1. Repeat steps 2 to 5 as needed.
- After applying all commits, the `git status` command shows that the rebase is complete.
+After applying all commits, the `git status` command shows that the rebase is complete.
1. Force-push your working branch to your remote fork:
@@ -270,4 +268,4 @@ If another contributor commits changes to the same file in another PR, it can cr
The pull request no longer shows any conflicts.
->For more information, see [Git Branching - Basic Branching and Merging](https://git-scm.com/book/en/v2/Git-Branching-Basic-Branching-and-Merging#_basic_merge_conflicts), [Advanced Merging](https://git-scm.com/book/en/v2/Git-Tools-Advanced-Merging), or ask in the `#sig-documentation` Slack channel for help.
+> For more information, see [Git Branching - Basic Branching and Merging](https://git-scm.com/book/en/v2/Git-Branching-Basic-Branching-and-Merging#_basic_merge_conflicts), [Advanced Merging](https://git-scm.com/book/en/v2/Git-Tools-Advanced-Merging), or ask in the `#sig-documentation` Slack channel for help.
diff --git a/content/en/community/get-involved/contributing/submitting.md b/content/en/docs/community/contributing/submitting.md
similarity index 68%
rename from content/en/community/get-involved/contributing/submitting.md
rename to content/en/docs/community/contributing/submitting.md
index 741f08db..b9b2c4a2 100644
--- a/content/en/community/get-involved/contributing/submitting.md
+++ b/content/en/docs/community/contributing/submitting.md
@@ -1,8 +1,7 @@
---
layout: single
-title: "Pull Requests and Changes"
-sidebar:
- nav: community
+title: 'Pull Requests and Changes'
+
aliases:
- /docs/how-to-submit-a-pr
---
@@ -15,17 +14,17 @@ To work on bigger technical changes, follow the [feature proposal](#feature-prop
## Pull Request Tips
-* Check that your title describes your changes and adheres to our [message conventions](#commit-and-pr-message-conventions).
-* Add inline code comments to changes that might not be obvious.
-* Squash your commits into logically reviewable chunks when you first submit
+- Check that your title describes your changes and adheres to our [message conventions](#commit-and-pr-message-conventions).
+- Add inline code comments to changes that might not be obvious.
+- Squash your commits into logically reviewable chunks when you first submit
your PR. Address feedback in follow-up (unsquashed) commits. It's much easier
to review incremental changes to feedback when the commits are kept separate.
-* All pull requests should get reviewed by at least one other [member of the
+- All pull requests should get reviewed by at least one other [member of the
Spinnaker organization](https://github.com/orgs/spinnaker/people) before
merging. (While some members of the organization have access to merge without
- a review, this should *only* be done in an emergency or when merging a large
+ a review, this should _only_ be done in an emergency or when merging a large
series of dependency bumps across repositories.)
-* Squash your commits when merging to the branch.
+- Squash your commits when merging to the branch.
## Commit and PR message conventions
@@ -33,7 +32,6 @@ Please follow conventions below in your git commit messages. Since GitHub auto-f
Note: In order to track and summarize the changes happening in Spinnaker, we use a changelog automation tool called [clog](https://github.com/clog-tool/clog-cli) which scrapes information from commit messages, which follow the ['conventional'](https://github.com/conventional-changelog/conventional-changelog/blob/a5505865ff3dd710cf757f50530e73ef0ca641da/conventions/angular.md) format.
-
To summarize, messages should be formatted as follows:
```
@@ -46,17 +44,17 @@ To summarize, messages should be formatted as follows:
#### Type
-Type | Purpose
---------|------------
-feat | A new feature. Please also link to the issue (in the body) if applicable. Causes a minor version bump.
-fix | A bug fix. Please also link to the issue (in the body) if applicable.
-docs | A documentation change.
-style | A code change that does not affect the meaning of the code, (e.g. indentation).
-refactor | A code change that neither fixes a bug or add a feature.
-perf | A code change that improves performance.
-test | Adding missing tests.
-chore | Changes to build process or auxiliary tools or libraries such as documentation generation.
-config | Changes to configurations that have tangible effects on users, (e.g. renaming properties, changing defaults, etc).
+| Type | Purpose |
+| -------- | ------------------------------------------------------------------------------------------------------------------ |
+| feat | A new feature. Please also link to the issue (in the body) if applicable. Causes a minor version bump. |
+| fix | A bug fix. Please also link to the issue (in the body) if applicable. |
+| docs | A documentation change. |
+| style | A code change that does not affect the meaning of the code, (e.g. indentation). |
+| refactor | A code change that neither fixes a bug or add a feature. |
+| perf | A code change that improves performance. |
+| test | Adding missing tests. |
+| chore | Changes to build process or auxiliary tools or libraries such as documentation generation. |
+| config | Changes to configurations that have tangible effects on users, (e.g. renaming properties, changing defaults, etc). |
The type of keyword affects the next semantic version bump. The `feat` keyword causes a minor version bump, while the rest of the keywords cause a patch version bump. Major version bumps are triggered by the presence of the words `BREAKING CHANGE` in the _commit message body_. This is covered more in [Body](#body).
@@ -81,7 +79,8 @@ fix(authN): Fixed session authentication coherence.
The `scope` is purposefully left open-ended, but try to group similar changes using the same value. Changes that have the same `scope` will be grouped together during changelog generation:
**Features**
-* Some_scope
+
+- Some_scope
- First feature goes here.
- Second feature goes here.
@@ -105,25 +104,26 @@ BREAKING CHANGE: More detail here if necessary.
At minimum, 'BREAKING CHANGE' must be specified on the last line. The extra detail is not mandatory.
-
### Feature Proposals
The Spinnaker community has historically avoided accepting
pull requests that add features without prior discussion. If you would like to
propose a feature:
+
- [Open an
-issue](https://github.com/spinnaker/spinnaker/issues/new) describing the desired functionality.
+ issue](https://github.com/spinnaker/spinnaker/issues/new) describing the desired functionality.
- Share your issue link in the [#dev
-channel](https://spinnakerteam.slack.com/messages/C0DPVDMQE/) in Slack.
+ channel](https://spinnakerteam.slack.com/messages/C0DPVDMQE/) in Slack.
- Consider discussing your ideas with other contributors before implementing them, to avoid rework.
### Requests For Change
If your change is large or very impactful, we may encourage you to submit an RFC:
+
- Use the [RFC
-template](https://github.com/spinnaker/governance/blob/master/rfc/.template.md).
+ template](https://github.com/spinnaker/governance/blob/master/rfc/.template.md).
- Consult several [already-submitted RFCs](https://github.com/spinnaker/governance/tree/master/rfc) for
-reference.
+ reference.
- When your RFC is ready, add it to [the `spinnaker/governance/rfc`
-directory](https://github.com/spinnaker/governance/tree/master/rfc) with a
-pull request. Approvers will see and review it.
+ directory](https://github.com/spinnaker/governance/tree/master/rfc) with a
+ pull request. Approvers will see and review it.
diff --git a/content/en/docs/community/get-help/_index.md b/content/en/docs/community/get-help/_index.md
new file mode 100644
index 00000000..6b740ce3
--- /dev/null
+++ b/content/en/docs/community/get-help/_index.md
@@ -0,0 +1,8 @@
+---
+title: 'Get Help'
+linkTitle: 'Get Help'
+weight: 1
+
+description: >
+ FAQs and Governance Information
+---
diff --git a/content/en/community/get-help/faqs/_index.md b/content/en/docs/community/get-help/faqs/_index.md
similarity index 80%
rename from content/en/community/get-help/faqs/_index.md
rename to content/en/docs/community/get-help/faqs/_index.md
index 439f22f6..78ee0787 100644
--- a/content/en/community/get-help/faqs/_index.md
+++ b/content/en/docs/community/get-help/faqs/_index.md
@@ -1,6 +1,6 @@
---
-title: "Frequently Asked Questions"
-linkTitle: "FAQ"
+title: 'Frequently Asked Questions'
+linkTitle: 'FAQ'
weight: 2
description:
---
@@ -8,40 +8,45 @@ description:
## What are the integrations available to Spinnaker?
### Cloud providers
-* Amazon Web Services
-* Google Cloud Platform
-* Cloud Foundry
-* Kubernetes
-* Microsoft Azure
-* Netflix Titus ( coming soon )
+
+- Amazon Web Services
+- Google Cloud Platform
+- Cloud Foundry
+- Kubernetes
+- Microsoft Azure
+- Netflix Titus ( coming soon )
### CI platforms
-* Jenkins
-* Travis
+
+- Jenkins
+- Travis
### Source repositories
-* GitHub
-* BitBucket Server / Stash
+
+- GitHub
+- BitBucket Server / Stash
### Messaging support
-* Email
-* Slack
-* Twilio
+
+- Email
+- Slack
+- Twilio
### Docker Registries
- * Anything with support for the [v2 Docker Registry API](https://docs.docker.com/registry/spec/api/)
+
+- Anything with support for the [v2 Docker Registry API](https://docs.docker.com/registry/spec/api/)
If you would like to add your own integration, we're happy to help you out in the slack channel.
## I have an existing pre-1.0 Spinnaker installation - how do I migrate to Halyard?
-There is no one-size-fits-all migration strategy because of how varied
+There is no one-size-fits-all migration strategy because of how varied
Spinnaker installations & configurations can be. However, there are a few
things you can keep in mind:
1. As long as you use the same storage source (GCS/S3/AZS bucket) all of your existing
pipelines & applications will be migrated.
-2. If you create the same cloud provider accounts that you had in your old Spinnaker
+2. If you create the same cloud provider accounts that you had in your old Spinnaker
installation, all of the same infrastructure will be available to you.
## Why don't the versions used in each subcomponent in the new top-level versioned Spinnaker match those in the github releases?
@@ -62,21 +67,19 @@ that matches `version-` follows semantic versioning. You can see an
example of this below:
![](./clouddriver-releases.png)
-
+
## I want to build my own cloud provider, how do I start?
Adding a new cloud provider is not a simple task. You would want to extend the Clouddriver and Deck modules to support your new cloud provider. Look at the [Kubernetes commit stream](https://github.com/spinnaker/clouddriver/pulls?q=is%3Apr+author%3Alwander+is%3Aclosed) for an example.
-
## How do I store my Spinnaker application in version control?
There are two kinds of application metadata at play within Spinnaker.
1. Data unique to Spinnaker, e.g. pipelines and their execution state, active triggers, deployment strategies, etc. Currently, these are stored inside Redis or SQL (for certain services), but we are actively adding support for S3 and GCS buckets, as well as Git backed data stores to make exporting, transferring and versioning this state simpler.
2. Data and relationships between different Spinnaker resources. These come entirely from data available from the underlying platform (AWS, GCP, etc...), and are derived from either
- a. Platform state, e.g. instance health, load balancer and server group relationships, etc...
- b. Spinnaker's naming conventions. For example, if you create a server group with name `myapp-dev-v000`, Spinnaker picks up this name from the platform and derives that you have an application `myapp`, with a cluster named `myapp-dev`, which contains a single server group with version `v000`.
-
+ a. Platform state, e.g. instance health, load balancer and server group relationships, etc...
+ b. Spinnaker's naming conventions. For example, if you create a server group with name `myapp-dev-v000`, Spinnaker picks up this name from the platform and derives that you have an application `myapp`, with a cluster named `myapp-dev`, which contains a single server group with version `v000`.
## Where can I find the Spinnaker API?
diff --git a/content/en/community/get-help/faqs/clouddriver-releases.png b/content/en/docs/community/get-help/faqs/clouddriver-releases.png
similarity index 100%
rename from content/en/community/get-help/faqs/clouddriver-releases.png
rename to content/en/docs/community/get-help/faqs/clouddriver-releases.png
diff --git a/content/en/docs/community/get-help/governance/_index.md b/content/en/docs/community/get-help/governance/_index.md
new file mode 100644
index 00000000..357f0f46
--- /dev/null
+++ b/content/en/docs/community/get-help/governance/_index.md
@@ -0,0 +1,6 @@
+---
+title: 'Governance'
+linkTitle: 'Governance'
+
+description:
+---
diff --git a/content/en/community/get-help/governance/sigs/index.md b/content/en/docs/community/get-help/governance/sigs/index.md
similarity index 62%
rename from content/en/community/get-help/governance/sigs/index.md
rename to content/en/docs/community/get-help/governance/sigs/index.md
index 9d007f3d..31154601 100644
--- a/content/en/community/get-help/governance/sigs/index.md
+++ b/content/en/docs/community/get-help/governance/sigs/index.md
@@ -1,10 +1,8 @@
---
-title: "Spinnaker Special Interest Groups"
-linkTitle: "Spinnaker Special Interest Groups"
-weight: 2
+title: 'Spinnaker Special Interest Groups'
+
description:
---
-
Information about Spinnaker SIGs has been moved to [the governance
repository](https://github.com/spinnaker/governance/blob/master/sig-index.md)
diff --git a/content/en/docs/community/gsoc/_index.md b/content/en/docs/community/gsoc/_index.md
index d7faad27..01abda37 100644
--- a/content/en/docs/community/gsoc/_index.md
+++ b/content/en/docs/community/gsoc/_index.md
@@ -1,6 +1,7 @@
---
-title: "Google Summer of Code"
-description: >
+title: 'Google Summer of Code'
+linktitle: 'Google Summer of Code'
+description: >
Information about working on Spinnaker as part of Google Summer of Code.
---
@@ -8,10 +9,10 @@ description: >
This page is a list of accepted ideas prepared specifically for [Spinnaker](https://spinnaker.io/concepts/), an open-source multi-cloud continuous delivery platform. The following list is non-exclusive, therefore if you're passionate about a different project, we're happy to review it! It should meet the [GSoC project guidelines](https://google.github.io/gsocguides/student/writing-a-proposal) and would require at least 1 mentor that we can try to help pair.
-| Project | Related Skillsets |
-|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|
-| try.spinnaker.ioOne of the best ways to learn Spinnaker is to use Spinnaker. This project is focused on generating (and destroying) temporary sandbox environments for new users to play around with, hosted by spinnaker.io.**Available Mentor(s):** Fernando Freire, Dan Johnston | Java AWS Infrastructure |
-| Gamifying SpinnakerGamifying is more than just giving users a pat on the back. It can influence good behavior and set guidance towards learning new skills. Companies could also use this data to find experienced users within their organizations. While the sky is the limit, let’s find what mechanics inspire you and bring that to life in Spinnaker!**Available Mentor(s):** Dan Johnston, Fernando Freire | Javascript Java |
-| Build-a-PluginMake a plugin to integrate Spinnaker with your favorite service / tool! Learn about Spinnaker and its Plugin Framework by creating a plugin for Spinnaker. Once the plugin is built, we will work together to add the plugin into the OSS Spinnaker Plugin Repository.**Available Mentor(s):** Cameron Motevasselani, Dan Johnston | Java Javascript |
-| Release ImprovementPossible projects could include showing code coverage for projects, "X days since last deploy failure" signs and more!**Available Mentor(s):** Cameron Motevasselani, Fernando Freire | Java Github Actions Testing frameworks |
-| Mobile-first Spinnaker ExperienceBuild a mobile-first Spinnaker experience that gives users a quick and easy way to get at-a-glance intelligence about their cloud infrastructure, with easy hooks for taking the most common CD actions on the go.**Available Mentor(s):** Fernando Freire, Dan Johnston | *All Optional* Javascript/ReactNative Flutter Java/Kotlin ObjectiveC/Swift |
\ No newline at end of file
+| Project | Related Skillsets |
+| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- |
+| try.spinnaker.ioOne of the best ways to learn Spinnaker is to use Spinnaker. This project is focused on generating (and destroying) temporary sandbox environments for new users to play around with, hosted by spinnaker.io.**Available Mentor(s):** Fernando Freire, Dan Johnston | Java AWS Infrastructure |
+| Gamifying SpinnakerGamifying is more than just giving users a pat on the back. It can influence good behavior and set guidance towards learning new skills. Companies could also use this data to find experienced users within their organizations. While the sky is the limit, let’s find what mechanics inspire you and bring that to life in Spinnaker!**Available Mentor(s):** Dan Johnston, Fernando Freire | Javascript Java |
+| Build-a-PluginMake a plugin to integrate Spinnaker with your favorite service / tool! Learn about Spinnaker and its Plugin Framework by creating a plugin for Spinnaker. Once the plugin is built, we will work together to add the plugin into the OSS Spinnaker Plugin Repository.**Available Mentor(s):** Cameron Motevasselani, Dan Johnston | Java Javascript |
+| Release ImprovementPossible projects could include showing code coverage for projects, "X days since last deploy failure" signs and more!**Available Mentor(s):** Cameron Motevasselani, Fernando Freire | Java Github Actions Testing frameworks |
+| Mobile-first Spinnaker ExperienceBuild a mobile-first Spinnaker experience that gives users a quick and easy way to get at-a-glance intelligence about their cloud infrastructure, with easy hooks for taking the most common CD actions on the go.**Available Mentor(s):** Fernando Freire, Dan Johnston | _All Optional_ Javascript/ReactNative Flutter Java/Kotlin ObjectiveC/Swift |
diff --git a/content/en/docs/community/security/_index.md b/content/en/docs/community/security/_index.md
index c0e16a1f..1960164b 100644
--- a/content/en/docs/community/security/_index.md
+++ b/content/en/docs/community/security/_index.md
@@ -1,50 +1,50 @@
---
-title: "Security"
-linkTitle: "Security"
-weight: 2
+title: 'Security'
+linkTitle: 'Security'
+weight: 5
description:
---
## Responsible Disclosure Policy
-We know that security is very important to the Spinnaker community. We welcome _(and encourage)_ any reviews and testing of Spinnaker's open source code to ensure the quality and security of Spinnaker for users around the world.
+We know that security is very important to the Spinnaker community. We welcome _(and encourage)_ any reviews and testing of Spinnaker's open source code to ensure the quality and security of Spinnaker for users around the world.
### Where should I report security issues?
-If you would like to report a vulnerability in the Spinnaker open source code, please email us at [security@spinnaker.io](mailto:security@spinnaker.io) right away, and a member of the [Security Special Interest Group (SIG)](https://github.com/spinnaker/governance/tree/master/sig-security) will get back to you as soon as we are able. We deeply appreciate your support in discovering and disclosing security issues in a responsible way.
+If you would like to report a vulnerability in the Spinnaker open source code, please email us at [security@spinnaker.io](mailto:security@spinnaker.io) right away, and a member of the [Security Special Interest Group (SIG)](https://github.com/spinnaker/governance/tree/master/sig-security) will get back to you as soon as we are able. We deeply appreciate your support in discovering and disclosing security issues in a responsible way.
### What should I include in a security report?
Please share any information we need to understand and reproduce the security issue you've discovered, including:
-* A complete description of the security issue
-* Steps to detect or reproduce the security bug
-* Versions and configurations affected by the issue
-* Whether you would like credit for finding the bug
+- A complete description of the security issue
+- Steps to detect or reproduce the security bug
+- Versions and configurations affected by the issue
+- Whether you would like credit for finding the bug
-*Note:* As an independent open source community, we do not provide bug bounties for security reports at this time.
+_Note:_ As an independent open source community, we do not provide bug bounties for security reports at this time.
### What kind of bugs should I report?
-To help us prioritize bugs affecting the Spinnaker community, please only report security issues affecting the Spinnaker open source code or common configurations for deployed Spinnaker services. Please keep in mind that security issues with higher severity will receive priority over less impactful bugs.
+To help us prioritize bugs affecting the Spinnaker community, please only report security issues affecting the Spinnaker open source code or common configurations for deployed Spinnaker services. Please keep in mind that security issues with higher severity will receive priority over less impactful bugs.
-*Note:* Do not conduct testing or security research against systems or data that you do not own.
+_Note:_ Do not conduct testing or security research against systems or data that you do not own.
### Can I include code for fixing a security issue?
-Absolutely! We love code contributions too, especially for security improvements. Please follow the [contributing guidelines](https://spinnaker.io/community/contributing/submitting/) for any changes you would like to share. If you have any questions, feel free to contact the Security SIG by saying _hello_ in the [Spinnaker Slack](http://join.spinnaker.io) [#security-sig](https://spinnakerteam.slack.com/archives/CFN8F5UR2) channel.
+Absolutely! We love code contributions too, especially for security improvements. Please follow the [contributing guidelines](https://spinnaker.io/community/contributing/submitting/) for any changes you would like to share. If you have any questions, feel free to contact the Security SIG by saying _hello_ in the [Spinnaker Slack](http://join.spinnaker.io) [#security-sig](https://spinnakerteam.slack.com/archives/CFN8F5UR2) channel.
### How are security bugs handled?
-We've created a 4-step process to review and mitigate any reported security issues in Spinnaker open source code. These steps are further described in the [Vulnerability Handling Process](https://docs.google.com/document/d/1dCJ17v2K-lEVBTEGsgS4xnuOZo30Ufd3gSoYrG6XZfA) document.
+We've created a 4-step process to review and mitigate any reported security issues in Spinnaker open source code. These steps are further described in the [Vulnerability Handling Process](https://docs.google.com/document/d/1dCJ17v2K-lEVBTEGsgS4xnuOZo30Ufd3gSoYrG6XZfA) document.
#### Step 1: A Front Door
-As part of the Spinnaker community, members of the Security SIG have volunteered to review and triage security vulnerabilities detected in Spinnaker open source code. All security issues that have been responsibly disclosed to [security@spinnaker.io](mailto:security@spinnaker.io) will be acknowledged and reviewed within one week of receiving the report.
+As part of the Spinnaker community, members of the Security SIG have volunteered to review and triage security vulnerabilities detected in Spinnaker open source code. All security issues that have been responsibly disclosed to [security@spinnaker.io](mailto:security@spinnaker.io) will be acknowledged and reviewed within one week of receiving the report.
#### Step 2: Evaluating New Reports
-New security vulnerabilities will be assessed against our predefined security taxonomy, which is explained in detail in our [Vulnerability Handling Process](https://docs.google.com/document/d/1dCJ17v2K-lEVBTEGsgS4xnuOZo30Ufd3gSoYrG6XZfA). We will work with you _(the security researcher)_ to determine the scope and impact of the security issue, assign a severity rating, and reserve a [CVE ID](https://cve.mitre.org/cve/identifiers/) for newly discovered bugs.
+New security vulnerabilities will be assessed against our predefined security taxonomy, which is explained in detail in our [Vulnerability Handling Process](https://docs.google.com/document/d/1dCJ17v2K-lEVBTEGsgS4xnuOZo30Ufd3gSoYrG6XZfA). We will work with you _(the security researcher)_ to determine the scope and impact of the security issue, assign a severity rating, and reserve a [CVE ID](https://cve.mitre.org/cve/identifiers/) for newly discovered bugs.
#### Step 3: Tracking Vulnerabilities
@@ -52,12 +52,12 @@ We track and monitor security vulnerabilities in Spinnaker open source code thro
#### Step 4: Mitigating Vulnerabilities
-Once a security issue has been confirmed and evaluated, the Security SIG will work with other members of the Spinnaker community to identify individuals to develop a patch or fix for each bug. Code changes for security issues will be developed publicly unless otherwise accepted by majority vote of the Security SIG. We will then track released security patches in the changelog for each release and update the CVE record.
+Once a security issue has been confirmed and evaluated, the Security SIG will work with other members of the Spinnaker community to identify individuals to develop a patch or fix for each bug. Code changes for security issues will be developed publicly unless otherwise accepted by majority vote of the Security SIG. We will then track released security patches in the changelog for each release and update the CVE record.
-## I have another question not answered here. Who should I talk to?
+## I have another question not answered here. Who should I talk to?
-For general questions about Spinnaker security, feel free to join us in the [Spinnaker Slack](http://join.spinnaker.io) [#security-sig](https://spinnakerteam.slack.com/archives/CFN8F5UR2) channel. Questions or feedback regarding a security issue or vulnerability should be sent directly to [security@spinnaker.io](mailto:security@spinnaker.io).
+For general questions about Spinnaker security, feel free to join us in the [Spinnaker Slack](http://join.spinnaker.io) [#security-sig](https://spinnakerteam.slack.com/archives/CFN8F5UR2) channel. Questions or feedback regarding a security issue or vulnerability should be sent directly to [security@spinnaker.io](mailto:security@spinnaker.io).
-## I'd like to participate in the [Security SIG](https://github.com/spinnaker/governance/tree/master/sig-security). How do I join?
+## I'd like to participate in the [Security SIG](https://github.com/spinnaker/governance/tree/master/sig-security). How do I join?
-We're thrilled that you're interested in supporting Spinnaker security! The Security SIG meets bi-weekly to address security issues and provide input on security capabilities within the Spinnaker project. You can get startetd by [requesting an invite](http://join.spinnaker.io) to the Spinnaker Slack team and joining the [#security-sig](https://spinnakerteam.slack.com/archives/CFN8F5UR2) channel.
\ No newline at end of file
+We're thrilled that you're interested in supporting Spinnaker security! The Security SIG meets bi-weekly to address security issues and provide input on security capabilities within the Spinnaker project. You can get startetd by [requesting an invite](http://join.spinnaker.io) to the Spinnaker Slack team and joining the [#security-sig](https://spinnakerteam.slack.com/archives/CFN8F5UR2) channel.
diff --git a/content/en/docs/community/stay-informed/_index.md b/content/en/docs/community/stay-informed/_index.md
new file mode 100644
index 00000000..dbc383f0
--- /dev/null
+++ b/content/en/docs/community/stay-informed/_index.md
@@ -0,0 +1,5 @@
+---
+title: Stay Informed
+linktitle: Stay Informed
+weight: 3
+---
diff --git a/content/en/community/stay-informed/captains-log/PR_authors_annual.png b/content/en/docs/community/stay-informed/captains-log/PR_authors_annual.png
similarity index 100%
rename from content/en/community/stay-informed/captains-log/PR_authors_annual.png
rename to content/en/docs/community/stay-informed/captains-log/PR_authors_annual.png
diff --git a/content/en/community/stay-informed/captains-log/activity_by_repo.png b/content/en/docs/community/stay-informed/captains-log/activity_by_repo.png
similarity index 100%
rename from content/en/community/stay-informed/captains-log/activity_by_repo.png
rename to content/en/docs/community/stay-informed/captains-log/activity_by_repo.png
diff --git a/content/en/community/stay-informed/captains-log/company_contributions.png b/content/en/docs/community/stay-informed/captains-log/company_contributions.png
similarity index 100%
rename from content/en/community/stay-informed/captains-log/company_contributions.png
rename to content/en/docs/community/stay-informed/captains-log/company_contributions.png
diff --git a/content/en/community/stay-informed/captains-log/company_dev_count.png b/content/en/docs/community/stay-informed/captains-log/company_dev_count.png
similarity index 100%
rename from content/en/community/stay-informed/captains-log/company_dev_count.png
rename to content/en/docs/community/stay-informed/captains-log/company_dev_count.png
diff --git a/content/en/community/stay-informed/captains-log/github_events.png b/content/en/docs/community/stay-informed/captains-log/github_events.png
similarity index 100%
rename from content/en/community/stay-informed/captains-log/github_events.png
rename to content/en/docs/community/stay-informed/captains-log/github_events.png
diff --git a/content/en/community/stay-informed/captains-log/index.md b/content/en/docs/community/stay-informed/captains-log/index.md
similarity index 65%
rename from content/en/community/stay-informed/captains-log/index.md
rename to content/en/docs/community/stay-informed/captains-log/index.md
index b8ef039b..ef783210 100644
--- a/content/en/community/stay-informed/captains-log/index.md
+++ b/content/en/docs/community/stay-informed/captains-log/index.md
@@ -1,54 +1,54 @@
---
-layout: single
-title: "Captain's Log: The State of Spinnaker"
+title: "Captain's Log: The State of Spinnaker"
+name: 'captains-log'
sidebar:
nav: community
---
-_Welcome to the Captain's Log! This report on the state of Spinnaker contains regularly updated project contribution and code repository metrics, to visualize the story of the Spinnaker's growth across its ecosystem._
+
+Welcome to the Captain's Log! This report on the state of Spinnaker contains regularly updated project contribution and code repository metrics, to visualize the story of the Spinnaker's growth across its ecosystem.
[Success stories](/success-stories/) from around the web tell of enterprises moving from brittle deployments to continuous delivery with Spinnaker:
-* [Airbnb uses Spinnaker](https://techbeacon.com/app-dev-testing/how-airbnb-scaled-its-migration-continuous-delivery-spinnaker) to migrate from monolith to service-oriented architecture.
-* [SAP leverages Spinnaker](https://blog.spinnaker.io/pipeline-redemption-how-spinnaker-is-shaping-delivery-excellence-at-sap-3b3c931b4f63?) on its mission to run the world better.
-* [Pinterest boosts productivity with Spinnaker](https://devops.com/devops-chat-ci-cd-velocity-for-large-monolithic-services-with-pinterest/) as it pioneers visual discovery.
-* [Mercari champions Spinnaker](https://speakerdeck.com/tcnksm/continuous-delivery-for-microservices-with-spinnaker-at-mercari) as a safeguard against deployment fear while releasing new services.
-* [Salesforce adopted Spinnaker](https://engineering.salesforce.com/salesforce-speakers-at-spinnaker-summit-and-kubecon-2019-d968292fd681) to bake images for both Kubernetes and VMs, to support its complex delivery requirements.
+
+- [Airbnb uses Spinnaker](https://techbeacon.com/app-dev-testing/how-airbnb-scaled-its-migration-continuous-delivery-spinnaker) to migrate from monolith to service-oriented architecture.
+- [SAP leverages Spinnaker](https://blog.spinnaker.io/pipeline-redemption-how-spinnaker-is-shaping-delivery-excellence-at-sap-3b3c931b4f63?) on its mission to run the world better.
+- [Pinterest boosts productivity with Spinnaker](https://devops.com/devops-chat-ci-cd-velocity-for-large-monolithic-services-with-pinterest/) as it pioneers visual discovery.
+- [Mercari champions Spinnaker](https://speakerdeck.com/tcnksm/continuous-delivery-for-microservices-with-spinnaker-at-mercari) as a safeguard against deployment fear while releasing new services.
+- [Salesforce adopted Spinnaker](https://engineering.salesforce.com/salesforce-speakers-at-spinnaker-summit-and-kubecon-2019-d968292fd681) to bake images for both Kubernetes and VMs, to support its complex delivery requirements.
## Spinnaker's trajectory
Our community began as a partnership between Netflix & Google, eager to share the benefits of Continuous Delivery. Now it's a vibrant OSS project, attracting hundreds of companies to participate as it evolves, integrating unique use cases and tools. Behold!
-{{< figure src="./stats-2020-02-05-with-logo.png" >}}
-
-
+{{< figure src="./stats-2020-02-05-with-logo.png" class="captains-log" >}}
### GitHub events in Spinnaker repositories
After steadily building momentum since its first OSS release in 2015, Spinnaker activity takes off. In December 2019, significant events within a week achieved a recent high of more than 4 times the weekly average so far:
-{{< figure src="./github_events.png" >}}
+{{< figure src="./github_events.png" class="captains-log">}}
### Contributions per company
Building from a committed base of key organizations, 2019 saw a rise in contributions from end-user companies and new stakeholders like Armory, OpsMx, and Amazon. The average number of contributions from companies besides Netflix and Google in H2 2019 was more than 2.5 times the average from December 2015 to today:
-{{< figure src="./company_contributions.png" >}}
+{{< figure src="./company_contributions.png" class="captains-log">}}
### Activity by repository
The Spinnaker ecosystem currently includes 44 repositories, including the microservices that deliver its core functionality and interface with deployment targets such as AWS, GCP, and Kubernetes. Added as the project has diversified: cleanup and monitoring tools, documentation, governance, community resources, and much more:
-{{< figure src="./activity_by_repo.png" >}}
+{{< figure src="./activity_by_repo.png" class="captains-log">}}
### Companies and developers contributing each week
Spinnaker has seen steadily increasing engagement from companies, and spikes of developer activity around community initiatives. The average weekly number of contributing developers was double the prior average in 2019, with up to 21 companies and 124 developers contributing each week:
-{{< figure src="./company_dev_count.png" >}}
+{{< figure src="./company_dev_count.png" class="captains-log">}}
### Myriad pull request contributors
Authors contribute pull requests to Spinnaker repositories each week, building the project collaboratively over time. In 2019, 314 unique developers submitted PRs, compared to 282 in 2018, and 194 in 2017:
-{{< figure src="./PR_authors_annual.png" >}}
+{{< figure src="./PR_authors_annual.png" class="captains-log">}}
### Visit Spinnaker DevStats for more!
-The data presented here comes from [Spinnaker's DevStats Dashboard](https://spinnaker.devstats.cd.foundation/), an awesome project growth [visualization and monitoring tool](https://devstats.cncf.io/) built by CNCF engineers in collaboration with Kubernetes and other CNCF project communities. DevStats defines a “contribution” as a review, comment, commit, PR, or issue. Big thanks to Lukasz Gryglicki and the CNCF!
+The data presented here comes from Spinnaker's DevStats Dashboard, an awesome project growth [visualization and monitoring tool](https://devstats.cncf.io/) built by CNCF engineers in collaboration with Kubernetes and other CNCF project communities. DevStats defines a “contribution” as a review, comment, commit, PR, or issue. Big thanks to Lukasz Gryglicki and the CNCF!
_Last updated February 2020_
diff --git a/content/en/community/stay-informed/captains-log/pr_authors.png b/content/en/docs/community/stay-informed/captains-log/pr_authors.png
similarity index 100%
rename from content/en/community/stay-informed/captains-log/pr_authors.png
rename to content/en/docs/community/stay-informed/captains-log/pr_authors.png
diff --git a/content/en/community/stay-informed/captains-log/stats-2020-02-05-with-logo.png b/content/en/docs/community/stay-informed/captains-log/stats-2020-02-05-with-logo.png
similarity index 100%
rename from content/en/community/stay-informed/captains-log/stats-2020-02-05-with-logo.png
rename to content/en/docs/community/stay-informed/captains-log/stats-2020-02-05-with-logo.png
diff --git a/content/en/community/stay-informed/captains-log/updated.png b/content/en/docs/community/stay-informed/captains-log/updated.png
similarity index 100%
rename from content/en/community/stay-informed/captains-log/updated.png
rename to content/en/docs/community/stay-informed/captains-log/updated.png
diff --git a/content/en/community/stay-informed/news/_index.md b/content/en/docs/community/stay-informed/news/_index.md
similarity index 56%
rename from content/en/community/stay-informed/news/_index.md
rename to content/en/docs/community/stay-informed/news/_index.md
index 14698681..280b8c08 100644
--- a/content/en/community/stay-informed/news/_index.md
+++ b/content/en/docs/community/stay-informed/news/_index.md
@@ -1,7 +1,4 @@
---
title: News
linkTitle: News
-menu:
- main:
- weight: 4
---
diff --git a/content/en/community/stay-informed/news/newsletter/_index.md b/content/en/docs/community/stay-informed/news/newsletter/_index.md
similarity index 100%
rename from content/en/community/stay-informed/news/newsletter/_index.md
rename to content/en/docs/community/stay-informed/news/newsletter/_index.md
diff --git a/content/en/community/stay-informed/news/newsletter/edition1.md b/content/en/docs/community/stay-informed/news/newsletter/edition1.md
similarity index 100%
rename from content/en/community/stay-informed/news/newsletter/edition1.md
rename to content/en/docs/community/stay-informed/news/newsletter/edition1.md
diff --git a/content/en/community/stay-informed/news/newsletter/edition2.md b/content/en/docs/community/stay-informed/news/newsletter/edition2.md
similarity index 100%
rename from content/en/community/stay-informed/news/newsletter/edition2.md
rename to content/en/docs/community/stay-informed/news/newsletter/edition2.md
diff --git a/content/en/community/stay-informed/news/newsletter/edition3.md b/content/en/docs/community/stay-informed/news/newsletter/edition3.md
similarity index 100%
rename from content/en/community/stay-informed/news/newsletter/edition3.md
rename to content/en/docs/community/stay-informed/news/newsletter/edition3.md
diff --git a/content/en/community/stay-informed/news/videos/_index.md b/content/en/docs/community/stay-informed/news/videos/_index.md
similarity index 100%
rename from content/en/community/stay-informed/news/videos/_index.md
rename to content/en/docs/community/stay-informed/news/videos/_index.md
diff --git a/content/en/community/stay-informed/security/_index.md b/content/en/docs/community/stay-informed/security/_index.md
similarity index 100%
rename from content/en/community/stay-informed/security/_index.md
rename to content/en/docs/community/stay-informed/security/_index.md
diff --git a/content/en/community/stay-informed/stats/_index.md b/content/en/docs/community/stay-informed/stats/_index.md
similarity index 100%
rename from content/en/community/stay-informed/stats/_index.md
rename to content/en/docs/community/stay-informed/stats/_index.md
diff --git a/content/en/docs/guides/developer/plugin-creator/project-config.md b/content/en/docs/guides/developer/plugin-creator/project-config.md
index 10870032..8c2bbb89 100644
--- a/content/en/docs/guides/developer/plugin-creator/project-config.md
+++ b/content/en/docs/guides/developer/plugin-creator/project-config.md
@@ -1,16 +1,13 @@
---
layout: single
-title: "Plugin Project Configuration"
+title: 'Plugin Project Configuration'
sidebar:
nav: guides
redirect-from:
- /guides/developer/plugin-creators/project-config/
---
-
-{% include toc %}
-
-Plugins are an evolving feature. The easiest way to set up a new plugin
+Plugins are an evolving feature. The easiest way to set up a new plugin
project is to copy one of the
[spinnaker-plugin-examples](https://github.com/spinnaker-plugin-examples)
projects that most closely resembles what you want to do.
@@ -84,6 +81,7 @@ String normalizedVersion() {
```
**Notes:**
+
1. The `plugins` block imports the node plugin but does not apply it. This
plugin is needed by the ui-extension to build assets. It also imports
the spinnaker-extensions gradle tooling.
@@ -146,6 +144,7 @@ spinnakerPlugin {
```
**Notes:**
+
1. The `io.spinnaker.plugin.service-extension` and `maven-publish` are used for plugin bundling
and metadata generation.
2. Spinnaker services require JDK 1.8 compatible bytecode.
@@ -199,9 +198,10 @@ When you build your plugin project with gradle, it will produce a `.plugin-ref`
Once you have that file generated, navigate to the `plugins` directory for the host service, wherever you are running it. You can then create a symlink to the `.plugin-ref` file, and this will cause the host service to see your plugin and load the classes from your development workspace when the host service starts up.
For the example project:
+
```
$ cd /path/to/orca/plugins
$ ln -sf /path/to/dev/workspaces/spinnaker-plugin-helloworld/helloworld-orca/build/orca.plugin-ref
```
-Now, when you attach your debugger to the host services, any breakpoints in your plugin code will be hit and you can step through them in your IDE, evaluate expressions, etc.
\ No newline at end of file
+Now, when you attach your debugger to the host services, any breakpoints in your plugin code will be hit and you can step through them in your IDE, evaluate expressions, etc.
diff --git a/content/en/docs/reference/halyard/commands.md b/content/en/docs/reference/halyard/commands.md
index 2c6db297..e09a1a50 100644
--- a/content/en/docs/reference/halyard/commands.md
+++ b/content/en/docs/reference/halyard/commands.md
@@ -1,9525 +1,10904 @@
---
-title: "Commands"
+title: 'Commands'
description: Halyard command reference
---
-
Published: 2020-04-30 21:10:29
-
## Table of Contents
+- [hal](#hal)
+- [hal admin](#hal-admin)
+- [hal admin deprecate](#hal-admin-deprecate)
+- [hal admin deprecate version](#hal-admin-deprecate-version)
+- [hal admin publish](#hal-admin-publish)
+- [hal admin publish bom](#hal-admin-publish-bom)
+- [hal admin publish latest](#hal-admin-publish-latest)
+- [hal admin publish latest-halyard](#hal-admin-publish-latest-halyard)
+- [hal admin publish latest-spinnaker](#hal-admin-publish-latest-spinnaker)
+- [hal admin publish profile](#hal-admin-publish-profile)
+- [hal admin publish version](#hal-admin-publish-version)
+- [hal backup](#hal-backup)
+- [hal backup create](#hal-backup-create)
+- [hal backup restore](#hal-backup-restore)
+- [hal config](#hal-config)
+- [hal config artifact](#hal-config-artifact)
+- [hal config artifact bitbucket](#hal-config-artifact-bitbucket)
+- [hal config artifact bitbucket account](#hal-config-artifact-bitbucket-account)
+- [hal config artifact bitbucket account add](#hal-config-artifact-bitbucket-account-add)
+- [hal config artifact bitbucket account delete](#hal-config-artifact-bitbucket-account-delete)
+- [hal config artifact bitbucket account edit](#hal-config-artifact-bitbucket-account-edit)
+- [hal config artifact bitbucket account get](#hal-config-artifact-bitbucket-account-get)
+- [hal config artifact bitbucket account list](#hal-config-artifact-bitbucket-account-list)
+- [hal config artifact bitbucket disable](#hal-config-artifact-bitbucket-disable)
+- [hal config artifact bitbucket enable](#hal-config-artifact-bitbucket-enable)
+- [hal config artifact gcs](#hal-config-artifact-gcs)
+- [hal config artifact gcs account](#hal-config-artifact-gcs-account)
+- [hal config artifact gcs account add](#hal-config-artifact-gcs-account-add)
+- [hal config artifact gcs account delete](#hal-config-artifact-gcs-account-delete)
+- [hal config artifact gcs account edit](#hal-config-artifact-gcs-account-edit)
+- [hal config artifact gcs account get](#hal-config-artifact-gcs-account-get)
+- [hal config artifact gcs account list](#hal-config-artifact-gcs-account-list)
+- [hal config artifact gcs disable](#hal-config-artifact-gcs-disable)
+- [hal config artifact gcs enable](#hal-config-artifact-gcs-enable)
+- [hal config artifact github](#hal-config-artifact-github)
+- [hal config artifact github account](#hal-config-artifact-github-account)
+- [hal config artifact github account add](#hal-config-artifact-github-account-add)
+- [hal config artifact github account delete](#hal-config-artifact-github-account-delete)
+- [hal config artifact github account edit](#hal-config-artifact-github-account-edit)
+- [hal config artifact github account get](#hal-config-artifact-github-account-get)
+- [hal config artifact github account list](#hal-config-artifact-github-account-list)
+- [hal config artifact github disable](#hal-config-artifact-github-disable)
+- [hal config artifact github enable](#hal-config-artifact-github-enable)
+- [hal config artifact gitlab](#hal-config-artifact-gitlab)
+- [hal config artifact gitlab account](#hal-config-artifact-gitlab-account)
+- [hal config artifact gitlab account add](#hal-config-artifact-gitlab-account-add)
+- [hal config artifact gitlab account delete](#hal-config-artifact-gitlab-account-delete)
+- [hal config artifact gitlab account edit](#hal-config-artifact-gitlab-account-edit)
+- [hal config artifact gitlab account get](#hal-config-artifact-gitlab-account-get)
+- [hal config artifact gitlab account list](#hal-config-artifact-gitlab-account-list)
+- [hal config artifact gitlab disable](#hal-config-artifact-gitlab-disable)
+- [hal config artifact gitlab enable](#hal-config-artifact-gitlab-enable)
+- [hal config artifact gitrepo](#hal-config-artifact-gitrepo)
+- [hal config artifact gitrepo account](#hal-config-artifact-gitrepo-account)
+- [hal config artifact gitrepo account add](#hal-config-artifact-gitrepo-account-add)
+- [hal config artifact gitrepo account delete](#hal-config-artifact-gitrepo-account-delete)
+- [hal config artifact gitrepo account edit](#hal-config-artifact-gitrepo-account-edit)
+- [hal config artifact gitrepo account get](#hal-config-artifact-gitrepo-account-get)
+- [hal config artifact gitrepo account list](#hal-config-artifact-gitrepo-account-list)
+- [hal config artifact gitrepo disable](#hal-config-artifact-gitrepo-disable)
+- [hal config artifact gitrepo enable](#hal-config-artifact-gitrepo-enable)
+- [hal config artifact helm](#hal-config-artifact-helm)
+- [hal config artifact helm account](#hal-config-artifact-helm-account)
+- [hal config artifact helm account add](#hal-config-artifact-helm-account-add)
+- [hal config artifact helm account delete](#hal-config-artifact-helm-account-delete)
+- [hal config artifact helm account edit](#hal-config-artifact-helm-account-edit)
+- [hal config artifact helm account get](#hal-config-artifact-helm-account-get)
+- [hal config artifact helm account list](#hal-config-artifact-helm-account-list)
+- [hal config artifact helm disable](#hal-config-artifact-helm-disable)
+- [hal config artifact helm enable](#hal-config-artifact-helm-enable)
+- [hal config artifact http](#hal-config-artifact-http)
+- [hal config artifact http account](#hal-config-artifact-http-account)
+- [hal config artifact http account add](#hal-config-artifact-http-account-add)
+- [hal config artifact http account delete](#hal-config-artifact-http-account-delete)
+- [hal config artifact http account edit](#hal-config-artifact-http-account-edit)
+- [hal config artifact http account get](#hal-config-artifact-http-account-get)
+- [hal config artifact http account list](#hal-config-artifact-http-account-list)
+- [hal config artifact http disable](#hal-config-artifact-http-disable)
+- [hal config artifact http enable](#hal-config-artifact-http-enable)
+- [hal config artifact maven](#hal-config-artifact-maven)
+- [hal config artifact maven account](#hal-config-artifact-maven-account)
+- [hal config artifact maven account add](#hal-config-artifact-maven-account-add)
+- [hal config artifact maven account delete](#hal-config-artifact-maven-account-delete)
+- [hal config artifact maven account edit](#hal-config-artifact-maven-account-edit)
+- [hal config artifact maven account get](#hal-config-artifact-maven-account-get)
+- [hal config artifact maven account list](#hal-config-artifact-maven-account-list)
+- [hal config artifact maven disable](#hal-config-artifact-maven-disable)
+- [hal config artifact maven enable](#hal-config-artifact-maven-enable)
+- [hal config artifact oracle](#hal-config-artifact-oracle)
+- [hal config artifact oracle account](#hal-config-artifact-oracle-account)
+- [hal config artifact oracle account add](#hal-config-artifact-oracle-account-add)
+- [hal config artifact oracle account delete](#hal-config-artifact-oracle-account-delete)
+- [hal config artifact oracle account edit](#hal-config-artifact-oracle-account-edit)
+- [hal config artifact oracle account get](#hal-config-artifact-oracle-account-get)
+- [hal config artifact oracle account list](#hal-config-artifact-oracle-account-list)
+- [hal config artifact oracle disable](#hal-config-artifact-oracle-disable)
+- [hal config artifact oracle enable](#hal-config-artifact-oracle-enable)
+- [hal config artifact s3](#hal-config-artifact-s3)
+- [hal config artifact s3 account](#hal-config-artifact-s3-account)
+- [hal config artifact s3 account add](#hal-config-artifact-s3-account-add)
+- [hal config artifact s3 account delete](#hal-config-artifact-s3-account-delete)
+- [hal config artifact s3 account edit](#hal-config-artifact-s3-account-edit)
+- [hal config artifact s3 account get](#hal-config-artifact-s3-account-get)
+- [hal config artifact s3 account list](#hal-config-artifact-s3-account-list)
+- [hal config artifact s3 disable](#hal-config-artifact-s3-disable)
+- [hal config artifact s3 enable](#hal-config-artifact-s3-enable)
+- [hal config artifact templates](#hal-config-artifact-templates)
+- [hal config artifact templates add](#hal-config-artifact-templates-add)
+- [hal config artifact templates delete](#hal-config-artifact-templates-delete)
+- [hal config artifact templates edit](#hal-config-artifact-templates-edit)
+- [hal config artifact templates list](#hal-config-artifact-templates-list)
+- [hal config canary](#hal-config-canary)
+- [hal config canary aws](#hal-config-canary-aws)
+- [hal config canary aws account](#hal-config-canary-aws-account)
+- [hal config canary aws account add](#hal-config-canary-aws-account-add)
+- [hal config canary aws account delete](#hal-config-canary-aws-account-delete)
+- [hal config canary aws account edit](#hal-config-canary-aws-account-edit)
+- [hal config canary aws account get](#hal-config-canary-aws-account-get)
+- [hal config canary aws account list](#hal-config-canary-aws-account-list)
+- [hal config canary aws disable](#hal-config-canary-aws-disable)
+- [hal config canary aws edit](#hal-config-canary-aws-edit)
+- [hal config canary aws enable](#hal-config-canary-aws-enable)
+- [hal config canary datadog](#hal-config-canary-datadog)
+- [hal config canary datadog account](#hal-config-canary-datadog-account)
+- [hal config canary datadog account add](#hal-config-canary-datadog-account-add)
+- [hal config canary datadog account delete](#hal-config-canary-datadog-account-delete)
+- [hal config canary datadog account edit](#hal-config-canary-datadog-account-edit)
+- [hal config canary datadog account get](#hal-config-canary-datadog-account-get)
+- [hal config canary datadog account list](#hal-config-canary-datadog-account-list)
+- [hal config canary datadog disable](#hal-config-canary-datadog-disable)
+- [hal config canary datadog enable](#hal-config-canary-datadog-enable)
+- [hal config canary disable](#hal-config-canary-disable)
+- [hal config canary edit](#hal-config-canary-edit)
+- [hal config canary enable](#hal-config-canary-enable)
+- [hal config canary google](#hal-config-canary-google)
+- [hal config canary google account](#hal-config-canary-google-account)
+- [hal config canary google account add](#hal-config-canary-google-account-add)
+- [hal config canary google account delete](#hal-config-canary-google-account-delete)
+- [hal config canary google account edit](#hal-config-canary-google-account-edit)
+- [hal config canary google account get](#hal-config-canary-google-account-get)
+- [hal config canary google account list](#hal-config-canary-google-account-list)
+- [hal config canary google disable](#hal-config-canary-google-disable)
+- [hal config canary google edit](#hal-config-canary-google-edit)
+- [hal config canary google enable](#hal-config-canary-google-enable)
+- [hal config canary newrelic](#hal-config-canary-newrelic)
+- [hal config canary newrelic account](#hal-config-canary-newrelic-account)
+- [hal config canary newrelic account add](#hal-config-canary-newrelic-account-add)
+- [hal config canary newrelic account delete](#hal-config-canary-newrelic-account-delete)
+- [hal config canary newrelic account edit](#hal-config-canary-newrelic-account-edit)
+- [hal config canary newrelic account get](#hal-config-canary-newrelic-account-get)
+- [hal config canary newrelic account list](#hal-config-canary-newrelic-account-list)
+- [hal config canary newrelic disable](#hal-config-canary-newrelic-disable)
+- [hal config canary newrelic enable](#hal-config-canary-newrelic-enable)
+- [hal config canary prometheus](#hal-config-canary-prometheus)
+- [hal config canary prometheus account](#hal-config-canary-prometheus-account)
+- [hal config canary prometheus account add](#hal-config-canary-prometheus-account-add)
+- [hal config canary prometheus account delete](#hal-config-canary-prometheus-account-delete)
+- [hal config canary prometheus account edit](#hal-config-canary-prometheus-account-edit)
+- [hal config canary prometheus account get](#hal-config-canary-prometheus-account-get)
+- [hal config canary prometheus account list](#hal-config-canary-prometheus-account-list)
+- [hal config canary prometheus disable](#hal-config-canary-prometheus-disable)
+- [hal config canary prometheus edit](#hal-config-canary-prometheus-edit)
+- [hal config canary prometheus enable](#hal-config-canary-prometheus-enable)
+- [hal config canary signalfx](#hal-config-canary-signalfx)
+- [hal config canary signalfx account](#hal-config-canary-signalfx-account)
+- [hal config canary signalfx account add](#hal-config-canary-signalfx-account-add)
+- [hal config canary signalfx account delete](#hal-config-canary-signalfx-account-delete)
+- [hal config canary signalfx account edit](#hal-config-canary-signalfx-account-edit)
+- [hal config canary signalfx account get](#hal-config-canary-signalfx-account-get)
+- [hal config canary signalfx account list](#hal-config-canary-signalfx-account-list)
+- [hal config canary signalfx disable](#hal-config-canary-signalfx-disable)
+- [hal config canary signalfx enable](#hal-config-canary-signalfx-enable)
+- [hal config ci](#hal-config-ci)
+- [hal config ci codebuild](#hal-config-ci-codebuild)
+- [hal config ci codebuild account](#hal-config-ci-codebuild-account)
+- [hal config ci codebuild account add](#hal-config-ci-codebuild-account-add)
+- [hal config ci codebuild account delete](#hal-config-ci-codebuild-account-delete)
+- [hal config ci codebuild account edit](#hal-config-ci-codebuild-account-edit)
+- [hal config ci codebuild account get](#hal-config-ci-codebuild-account-get)
+- [hal config ci codebuild account list](#hal-config-ci-codebuild-account-list)
+- [hal config ci codebuild disable](#hal-config-ci-codebuild-disable)
+- [hal config ci codebuild edit](#hal-config-ci-codebuild-edit)
+- [hal config ci codebuild enable](#hal-config-ci-codebuild-enable)
+- [hal config ci concourse](#hal-config-ci-concourse)
+- [hal config ci concourse disable](#hal-config-ci-concourse-disable)
+- [hal config ci concourse enable](#hal-config-ci-concourse-enable)
+- [hal config ci concourse master](#hal-config-ci-concourse-master)
+- [hal config ci concourse master add](#hal-config-ci-concourse-master-add)
+- [hal config ci concourse master delete](#hal-config-ci-concourse-master-delete)
+- [hal config ci concourse master edit](#hal-config-ci-concourse-master-edit)
+- [hal config ci concourse master get](#hal-config-ci-concourse-master-get)
+- [hal config ci concourse master list](#hal-config-ci-concourse-master-list)
+- [hal config ci gcb](#hal-config-ci-gcb)
+- [hal config ci gcb account](#hal-config-ci-gcb-account)
+- [hal config ci gcb account add](#hal-config-ci-gcb-account-add)
+- [hal config ci gcb account delete](#hal-config-ci-gcb-account-delete)
+- [hal config ci gcb account edit](#hal-config-ci-gcb-account-edit)
+- [hal config ci gcb account list](#hal-config-ci-gcb-account-list)
+- [hal config ci gcb disable](#hal-config-ci-gcb-disable)
+- [hal config ci gcb enable](#hal-config-ci-gcb-enable)
+- [hal config ci jenkins](#hal-config-ci-jenkins)
+- [hal config ci jenkins disable](#hal-config-ci-jenkins-disable)
+- [hal config ci jenkins enable](#hal-config-ci-jenkins-enable)
+- [hal config ci jenkins master](#hal-config-ci-jenkins-master)
+- [hal config ci jenkins master add](#hal-config-ci-jenkins-master-add)
+- [hal config ci jenkins master delete](#hal-config-ci-jenkins-master-delete)
+- [hal config ci jenkins master edit](#hal-config-ci-jenkins-master-edit)
+- [hal config ci jenkins master get](#hal-config-ci-jenkins-master-get)
+- [hal config ci jenkins master list](#hal-config-ci-jenkins-master-list)
+- [hal config ci travis](#hal-config-ci-travis)
+- [hal config ci travis disable](#hal-config-ci-travis-disable)
+- [hal config ci travis enable](#hal-config-ci-travis-enable)
+- [hal config ci travis master](#hal-config-ci-travis-master)
+- [hal config ci travis master add](#hal-config-ci-travis-master-add)
+- [hal config ci travis master delete](#hal-config-ci-travis-master-delete)
+- [hal config ci travis master edit](#hal-config-ci-travis-master-edit)
+- [hal config ci travis master get](#hal-config-ci-travis-master-get)
+- [hal config ci travis master list](#hal-config-ci-travis-master-list)
+- [hal config ci wercker](#hal-config-ci-wercker)
+- [hal config ci wercker disable](#hal-config-ci-wercker-disable)
+- [hal config ci wercker enable](#hal-config-ci-wercker-enable)
+- [hal config ci wercker master](#hal-config-ci-wercker-master)
+- [hal config ci wercker master add](#hal-config-ci-wercker-master-add)
+- [hal config ci wercker master delete](#hal-config-ci-wercker-master-delete)
+- [hal config ci wercker master edit](#hal-config-ci-wercker-master-edit)
+- [hal config ci wercker master get](#hal-config-ci-wercker-master-get)
+- [hal config ci wercker master list](#hal-config-ci-wercker-master-list)
+- [hal config deploy](#hal-config-deploy)
+- [hal config deploy component-sizing](#hal-config-deploy-component-sizing)
+- [hal config deploy component-sizing clouddriver](#hal-config-deploy-component-sizing-clouddriver)
+- [hal config deploy component-sizing clouddriver delete](#hal-config-deploy-component-sizing-clouddriver-delete)
+- [hal config deploy component-sizing clouddriver edit](#hal-config-deploy-component-sizing-clouddriver-edit)
+- [hal config deploy component-sizing clouddriver-bootstrap](#hal-config-deploy-component-sizing-clouddriver-bootstrap)
+- [hal config deploy component-sizing clouddriver-bootstrap delete](#hal-config-deploy-component-sizing-clouddriver-bootstrap-delete)
+- [hal config deploy component-sizing clouddriver-bootstrap edit](#hal-config-deploy-component-sizing-clouddriver-bootstrap-edit)
+- [hal config deploy component-sizing clouddriver-caching](#hal-config-deploy-component-sizing-clouddriver-caching)
+- [hal config deploy component-sizing clouddriver-caching delete](#hal-config-deploy-component-sizing-clouddriver-caching-delete)
+- [hal config deploy component-sizing clouddriver-caching edit](#hal-config-deploy-component-sizing-clouddriver-caching-edit)
+- [hal config deploy component-sizing clouddriver-ro](#hal-config-deploy-component-sizing-clouddriver-ro)
+- [hal config deploy component-sizing clouddriver-ro delete](#hal-config-deploy-component-sizing-clouddriver-ro-delete)
+- [hal config deploy component-sizing clouddriver-ro edit](#hal-config-deploy-component-sizing-clouddriver-ro-edit)
+- [hal config deploy component-sizing clouddriver-ro-deck](#hal-config-deploy-component-sizing-clouddriver-ro-deck)
+- [hal config deploy component-sizing clouddriver-ro-deck delete](#hal-config-deploy-component-sizing-clouddriver-ro-deck-delete)
+- [hal config deploy component-sizing clouddriver-ro-deck edit](#hal-config-deploy-component-sizing-clouddriver-ro-deck-edit)
+- [hal config deploy component-sizing clouddriver-rw](#hal-config-deploy-component-sizing-clouddriver-rw)
+- [hal config deploy component-sizing clouddriver-rw delete](#hal-config-deploy-component-sizing-clouddriver-rw-delete)
+- [hal config deploy component-sizing clouddriver-rw edit](#hal-config-deploy-component-sizing-clouddriver-rw-edit)
+- [hal config deploy component-sizing consul-client](#hal-config-deploy-component-sizing-consul-client)
+- [hal config deploy component-sizing consul-client delete](#hal-config-deploy-component-sizing-consul-client-delete)
+- [hal config deploy component-sizing consul-client edit](#hal-config-deploy-component-sizing-consul-client-edit)
+- [hal config deploy component-sizing consul-server](#hal-config-deploy-component-sizing-consul-server)
+- [hal config deploy component-sizing consul-server delete](#hal-config-deploy-component-sizing-consul-server-delete)
+- [hal config deploy component-sizing consul-server edit](#hal-config-deploy-component-sizing-consul-server-edit)
+- [hal config deploy component-sizing deck](#hal-config-deploy-component-sizing-deck)
+- [hal config deploy component-sizing deck delete](#hal-config-deploy-component-sizing-deck-delete)
+- [hal config deploy component-sizing deck edit](#hal-config-deploy-component-sizing-deck-edit)
+- [hal config deploy component-sizing echo](#hal-config-deploy-component-sizing-echo)
+- [hal config deploy component-sizing echo delete](#hal-config-deploy-component-sizing-echo-delete)
+- [hal config deploy component-sizing echo edit](#hal-config-deploy-component-sizing-echo-edit)
+- [hal config deploy component-sizing echo-scheduler](#hal-config-deploy-component-sizing-echo-scheduler)
+- [hal config deploy component-sizing echo-scheduler delete](#hal-config-deploy-component-sizing-echo-scheduler-delete)
+- [hal config deploy component-sizing echo-scheduler edit](#hal-config-deploy-component-sizing-echo-scheduler-edit)
+- [hal config deploy component-sizing echo-worker](#hal-config-deploy-component-sizing-echo-worker)
+- [hal config deploy component-sizing echo-worker delete](#hal-config-deploy-component-sizing-echo-worker-delete)
+- [hal config deploy component-sizing echo-worker edit](#hal-config-deploy-component-sizing-echo-worker-edit)
+- [hal config deploy component-sizing fiat](#hal-config-deploy-component-sizing-fiat)
+- [hal config deploy component-sizing fiat delete](#hal-config-deploy-component-sizing-fiat-delete)
+- [hal config deploy component-sizing fiat edit](#hal-config-deploy-component-sizing-fiat-edit)
+- [hal config deploy component-sizing front50](#hal-config-deploy-component-sizing-front50)
+- [hal config deploy component-sizing front50 delete](#hal-config-deploy-component-sizing-front50-delete)
+- [hal config deploy component-sizing front50 edit](#hal-config-deploy-component-sizing-front50-edit)
+- [hal config deploy component-sizing gate](#hal-config-deploy-component-sizing-gate)
+- [hal config deploy component-sizing gate delete](#hal-config-deploy-component-sizing-gate-delete)
+- [hal config deploy component-sizing gate edit](#hal-config-deploy-component-sizing-gate-edit)
+- [hal config deploy component-sizing igor](#hal-config-deploy-component-sizing-igor)
+- [hal config deploy component-sizing igor delete](#hal-config-deploy-component-sizing-igor-delete)
+- [hal config deploy component-sizing igor edit](#hal-config-deploy-component-sizing-igor-edit)
+- [hal config deploy component-sizing kayenta](#hal-config-deploy-component-sizing-kayenta)
+- [hal config deploy component-sizing kayenta delete](#hal-config-deploy-component-sizing-kayenta-delete)
+- [hal config deploy component-sizing kayenta edit](#hal-config-deploy-component-sizing-kayenta-edit)
+- [hal config deploy component-sizing monitoring-daemon](#hal-config-deploy-component-sizing-monitoring-daemon)
+- [hal config deploy component-sizing monitoring-daemon delete](#hal-config-deploy-component-sizing-monitoring-daemon-delete)
+- [hal config deploy component-sizing monitoring-daemon edit](#hal-config-deploy-component-sizing-monitoring-daemon-edit)
+- [hal config deploy component-sizing orca](#hal-config-deploy-component-sizing-orca)
+- [hal config deploy component-sizing orca delete](#hal-config-deploy-component-sizing-orca-delete)
+- [hal config deploy component-sizing orca edit](#hal-config-deploy-component-sizing-orca-edit)
+- [hal config deploy component-sizing orca-bootstrap](#hal-config-deploy-component-sizing-orca-bootstrap)
+- [hal config deploy component-sizing orca-bootstrap delete](#hal-config-deploy-component-sizing-orca-bootstrap-delete)
+- [hal config deploy component-sizing orca-bootstrap edit](#hal-config-deploy-component-sizing-orca-bootstrap-edit)
+- [hal config deploy component-sizing redis](#hal-config-deploy-component-sizing-redis)
+- [hal config deploy component-sizing redis delete](#hal-config-deploy-component-sizing-redis-delete)
+- [hal config deploy component-sizing redis edit](#hal-config-deploy-component-sizing-redis-edit)
+- [hal config deploy component-sizing redis-bootstrap](#hal-config-deploy-component-sizing-redis-bootstrap)
+- [hal config deploy component-sizing redis-bootstrap delete](#hal-config-deploy-component-sizing-redis-bootstrap-delete)
+- [hal config deploy component-sizing redis-bootstrap edit](#hal-config-deploy-component-sizing-redis-bootstrap-edit)
+- [hal config deploy component-sizing rosco](#hal-config-deploy-component-sizing-rosco)
+- [hal config deploy component-sizing rosco delete](#hal-config-deploy-component-sizing-rosco-delete)
+- [hal config deploy component-sizing rosco edit](#hal-config-deploy-component-sizing-rosco-edit)
+- [hal config deploy component-sizing vault-client](#hal-config-deploy-component-sizing-vault-client)
+- [hal config deploy component-sizing vault-client delete](#hal-config-deploy-component-sizing-vault-client-delete)
+- [hal config deploy component-sizing vault-client edit](#hal-config-deploy-component-sizing-vault-client-edit)
+- [hal config deploy component-sizing vault-server](#hal-config-deploy-component-sizing-vault-server)
+- [hal config deploy component-sizing vault-server delete](#hal-config-deploy-component-sizing-vault-server-delete)
+- [hal config deploy component-sizing vault-server edit](#hal-config-deploy-component-sizing-vault-server-edit)
+- [hal config deploy edit](#hal-config-deploy-edit)
+- [hal config deploy ha](#hal-config-deploy-ha)
+- [hal config deploy ha clouddriver](#hal-config-deploy-ha-clouddriver)
+- [hal config deploy ha clouddriver disable](#hal-config-deploy-ha-clouddriver-disable)
+- [hal config deploy ha clouddriver edit](#hal-config-deploy-ha-clouddriver-edit)
+- [hal config deploy ha clouddriver enable](#hal-config-deploy-ha-clouddriver-enable)
+- [hal config deploy ha echo](#hal-config-deploy-ha-echo)
+- [hal config deploy ha echo disable](#hal-config-deploy-ha-echo-disable)
+- [hal config deploy ha echo enable](#hal-config-deploy-ha-echo-enable)
+- [hal config edit](#hal-config-edit)
+- [hal config features](#hal-config-features)
+- [hal config features edit](#hal-config-features-edit)
+- [hal config generate](#hal-config-generate)
+- [hal config list](#hal-config-list)
+- [hal config metric-stores](#hal-config-metric-stores)
+- [hal config metric-stores datadog](#hal-config-metric-stores-datadog)
+- [hal config metric-stores datadog disable](#hal-config-metric-stores-datadog-disable)
+- [hal config metric-stores datadog edit](#hal-config-metric-stores-datadog-edit)
+- [hal config metric-stores datadog enable](#hal-config-metric-stores-datadog-enable)
+- [hal config metric-stores edit](#hal-config-metric-stores-edit)
+- [hal config metric-stores newrelic](#hal-config-metric-stores-newrelic)
+- [hal config metric-stores newrelic disable](#hal-config-metric-stores-newrelic-disable)
+- [hal config metric-stores newrelic edit](#hal-config-metric-stores-newrelic-edit)
+- [hal config metric-stores newrelic enable](#hal-config-metric-stores-newrelic-enable)
+- [hal config metric-stores prometheus](#hal-config-metric-stores-prometheus)
+- [hal config metric-stores prometheus disable](#hal-config-metric-stores-prometheus-disable)
+- [hal config metric-stores prometheus edit](#hal-config-metric-stores-prometheus-edit)
+- [hal config metric-stores prometheus enable](#hal-config-metric-stores-prometheus-enable)
+- [hal config metric-stores stackdriver](#hal-config-metric-stores-stackdriver)
+- [hal config metric-stores stackdriver disable](#hal-config-metric-stores-stackdriver-disable)
+- [hal config metric-stores stackdriver edit](#hal-config-metric-stores-stackdriver-edit)
+- [hal config metric-stores stackdriver enable](#hal-config-metric-stores-stackdriver-enable)
+- [hal config notification](#hal-config-notification)
+- [hal config notification github-status](#hal-config-notification-github-status)
+- [hal config notification github-status disable](#hal-config-notification-github-status-disable)
+- [hal config notification github-status edit](#hal-config-notification-github-status-edit)
+- [hal config notification github-status enable](#hal-config-notification-github-status-enable)
+- [hal config notification pubsub](#hal-config-notification-pubsub)
+- [hal config notification pubsub google](#hal-config-notification-pubsub-google)
+- [hal config notification pubsub google add](#hal-config-notification-pubsub-google-add)
+- [hal config notification pubsub google delete](#hal-config-notification-pubsub-google-delete)
+- [hal config notification pubsub google disable](#hal-config-notification-pubsub-google-disable)
+- [hal config notification pubsub google edit](#hal-config-notification-pubsub-google-edit)
+- [hal config notification pubsub google enable](#hal-config-notification-pubsub-google-enable)
+- [hal config notification pubsub google get](#hal-config-notification-pubsub-google-get)
+- [hal config notification pubsub google list](#hal-config-notification-pubsub-google-list)
+- [hal config notification slack](#hal-config-notification-slack)
+- [hal config notification slack disable](#hal-config-notification-slack-disable)
+- [hal config notification slack edit](#hal-config-notification-slack-edit)
+- [hal config notification slack enable](#hal-config-notification-slack-enable)
+- [hal config notification twilio](#hal-config-notification-twilio)
+- [hal config notification twilio disable](#hal-config-notification-twilio-disable)
+- [hal config notification twilio edit](#hal-config-notification-twilio-edit)
+- [hal config notification twilio enable](#hal-config-notification-twilio-enable)
+- [hal config provider](#hal-config-provider)
+- [hal config provider appengine](#hal-config-provider-appengine)
+- [hal config provider appengine account](#hal-config-provider-appengine-account)
+- [hal config provider appengine account add](#hal-config-provider-appengine-account-add)
+- [hal config provider appengine account delete](#hal-config-provider-appengine-account-delete)
+- [hal config provider appengine account edit](#hal-config-provider-appengine-account-edit)
+- [hal config provider appengine account get](#hal-config-provider-appengine-account-get)
+- [hal config provider appengine account list](#hal-config-provider-appengine-account-list)
+- [hal config provider appengine disable](#hal-config-provider-appengine-disable)
+- [hal config provider appengine edit](#hal-config-provider-appengine-edit)
+- [hal config provider appengine enable](#hal-config-provider-appengine-enable)
+- [hal config provider aws](#hal-config-provider-aws)
+- [hal config provider aws account](#hal-config-provider-aws-account)
+- [hal config provider aws account add](#hal-config-provider-aws-account-add)
+- [hal config provider aws account delete](#hal-config-provider-aws-account-delete)
+- [hal config provider aws account edit](#hal-config-provider-aws-account-edit)
+- [hal config provider aws account get](#hal-config-provider-aws-account-get)
+- [hal config provider aws account list](#hal-config-provider-aws-account-list)
+- [hal config provider aws bakery](#hal-config-provider-aws-bakery)
+- [hal config provider aws bakery edit](#hal-config-provider-aws-bakery-edit)
+- [hal config provider aws disable](#hal-config-provider-aws-disable)
+- [hal config provider aws edit](#hal-config-provider-aws-edit)
+- [hal config provider aws enable](#hal-config-provider-aws-enable)
+- [hal config provider aws features](#hal-config-provider-aws-features)
+- [hal config provider aws features edit](#hal-config-provider-aws-features-edit)
+- [hal config provider azure](#hal-config-provider-azure)
+- [hal config provider azure account](#hal-config-provider-azure-account)
+- [hal config provider azure account add](#hal-config-provider-azure-account-add)
+- [hal config provider azure account delete](#hal-config-provider-azure-account-delete)
+- [hal config provider azure account edit](#hal-config-provider-azure-account-edit)
+- [hal config provider azure account get](#hal-config-provider-azure-account-get)
+- [hal config provider azure account list](#hal-config-provider-azure-account-list)
+- [hal config provider azure bakery](#hal-config-provider-azure-bakery)
+- [hal config provider azure bakery base-image](#hal-config-provider-azure-bakery-base-image)
+- [hal config provider azure bakery base-image add](#hal-config-provider-azure-bakery-base-image-add)
+- [hal config provider azure bakery base-image delete](#hal-config-provider-azure-bakery-base-image-delete)
+- [hal config provider azure bakery base-image edit](#hal-config-provider-azure-bakery-base-image-edit)
+- [hal config provider azure bakery base-image get](#hal-config-provider-azure-bakery-base-image-get)
+- [hal config provider azure bakery base-image list](#hal-config-provider-azure-bakery-base-image-list)
+- [hal config provider azure bakery edit](#hal-config-provider-azure-bakery-edit)
+- [hal config provider azure disable](#hal-config-provider-azure-disable)
+- [hal config provider azure enable](#hal-config-provider-azure-enable)
+- [hal config provider cloudfoundry](#hal-config-provider-cloudfoundry)
+- [hal config provider cloudfoundry account](#hal-config-provider-cloudfoundry-account)
+- [hal config provider cloudfoundry account add](#hal-config-provider-cloudfoundry-account-add)
+- [hal config provider cloudfoundry account delete](#hal-config-provider-cloudfoundry-account-delete)
+- [hal config provider cloudfoundry account edit](#hal-config-provider-cloudfoundry-account-edit)
+- [hal config provider cloudfoundry account get](#hal-config-provider-cloudfoundry-account-get)
+- [hal config provider cloudfoundry account list](#hal-config-provider-cloudfoundry-account-list)
+- [hal config provider cloudfoundry disable](#hal-config-provider-cloudfoundry-disable)
+- [hal config provider cloudfoundry enable](#hal-config-provider-cloudfoundry-enable)
+- [hal config provider dcos](#hal-config-provider-dcos)
+- [hal config provider dcos account](#hal-config-provider-dcos-account)
+- [hal config provider dcos account add](#hal-config-provider-dcos-account-add)
+- [hal config provider dcos account delete](#hal-config-provider-dcos-account-delete)
+- [hal config provider dcos account edit](#hal-config-provider-dcos-account-edit)
+- [hal config provider dcos account get](#hal-config-provider-dcos-account-get)
+- [hal config provider dcos account list](#hal-config-provider-dcos-account-list)
+- [hal config provider dcos cluster](#hal-config-provider-dcos-cluster)
+- [hal config provider dcos cluster add](#hal-config-provider-dcos-cluster-add)
+- [hal config provider dcos cluster delete](#hal-config-provider-dcos-cluster-delete)
+- [hal config provider dcos cluster edit](#hal-config-provider-dcos-cluster-edit)
+- [hal config provider dcos cluster get](#hal-config-provider-dcos-cluster-get)
+- [hal config provider dcos cluster list](#hal-config-provider-dcos-cluster-list)
+- [hal config provider dcos disable](#hal-config-provider-dcos-disable)
+- [hal config provider dcos enable](#hal-config-provider-dcos-enable)
+- [hal config provider docker-registry](#hal-config-provider-docker-registry)
+- [hal config provider docker-registry account](#hal-config-provider-docker-registry-account)
+- [hal config provider docker-registry account add](#hal-config-provider-docker-registry-account-add)
+- [hal config provider docker-registry account delete](#hal-config-provider-docker-registry-account-delete)
+- [hal config provider docker-registry account edit](#hal-config-provider-docker-registry-account-edit)
+- [hal config provider docker-registry account get](#hal-config-provider-docker-registry-account-get)
+- [hal config provider docker-registry account list](#hal-config-provider-docker-registry-account-list)
+- [hal config provider docker-registry disable](#hal-config-provider-docker-registry-disable)
+- [hal config provider docker-registry enable](#hal-config-provider-docker-registry-enable)
+- [hal config provider ecs](#hal-config-provider-ecs)
+- [hal config provider ecs account](#hal-config-provider-ecs-account)
+- [hal config provider ecs account add](#hal-config-provider-ecs-account-add)
+- [hal config provider ecs account delete](#hal-config-provider-ecs-account-delete)
+- [hal config provider ecs account edit](#hal-config-provider-ecs-account-edit)
+- [hal config provider ecs account get](#hal-config-provider-ecs-account-get)
+- [hal config provider ecs account list](#hal-config-provider-ecs-account-list)
+- [hal config provider ecs disable](#hal-config-provider-ecs-disable)
+- [hal config provider ecs enable](#hal-config-provider-ecs-enable)
+- [hal config provider google](#hal-config-provider-google)
+- [hal config provider google account](#hal-config-provider-google-account)
+- [hal config provider google account add](#hal-config-provider-google-account-add)
+- [hal config provider google account delete](#hal-config-provider-google-account-delete)
+- [hal config provider google account edit](#hal-config-provider-google-account-edit)
+- [hal config provider google account get](#hal-config-provider-google-account-get)
+- [hal config provider google account list](#hal-config-provider-google-account-list)
+- [hal config provider google bakery](#hal-config-provider-google-bakery)
+- [hal config provider google bakery base-image](#hal-config-provider-google-bakery-base-image)
+- [hal config provider google bakery base-image add](#hal-config-provider-google-bakery-base-image-add)
+- [hal config provider google bakery base-image delete](#hal-config-provider-google-bakery-base-image-delete)
+- [hal config provider google bakery base-image edit](#hal-config-provider-google-bakery-base-image-edit)
+- [hal config provider google bakery base-image get](#hal-config-provider-google-bakery-base-image-get)
+- [hal config provider google bakery base-image list](#hal-config-provider-google-bakery-base-image-list)
+- [hal config provider google bakery edit](#hal-config-provider-google-bakery-edit)
+- [hal config provider google disable](#hal-config-provider-google-disable)
+- [hal config provider google edit](#hal-config-provider-google-edit)
+- [hal config provider google enable](#hal-config-provider-google-enable)
+- [hal config provider huaweicloud](#hal-config-provider-huaweicloud)
+- [hal config provider huaweicloud account](#hal-config-provider-huaweicloud-account)
+- [hal config provider huaweicloud account add](#hal-config-provider-huaweicloud-account-add)
+- [hal config provider huaweicloud account delete](#hal-config-provider-huaweicloud-account-delete)
+- [hal config provider huaweicloud account edit](#hal-config-provider-huaweicloud-account-edit)
+- [hal config provider huaweicloud account get](#hal-config-provider-huaweicloud-account-get)
+- [hal config provider huaweicloud account list](#hal-config-provider-huaweicloud-account-list)
+- [hal config provider huaweicloud bakery](#hal-config-provider-huaweicloud-bakery)
+- [hal config provider huaweicloud bakery base-image](#hal-config-provider-huaweicloud-bakery-base-image)
+- [hal config provider huaweicloud bakery base-image add](#hal-config-provider-huaweicloud-bakery-base-image-add)
+- [hal config provider huaweicloud bakery base-image delete](#hal-config-provider-huaweicloud-bakery-base-image-delete)
+- [hal config provider huaweicloud bakery base-image edit](#hal-config-provider-huaweicloud-bakery-base-image-edit)
+- [hal config provider huaweicloud bakery base-image get](#hal-config-provider-huaweicloud-bakery-base-image-get)
+- [hal config provider huaweicloud bakery base-image list](#hal-config-provider-huaweicloud-bakery-base-image-list)
+- [hal config provider huaweicloud bakery edit](#hal-config-provider-huaweicloud-bakery-edit)
+- [hal config provider huaweicloud disable](#hal-config-provider-huaweicloud-disable)
+- [hal config provider huaweicloud enable](#hal-config-provider-huaweicloud-enable)
+- [hal config provider kubernetes](#hal-config-provider-kubernetes)
+- [hal config provider kubernetes account](#hal-config-provider-kubernetes-account)
+- [hal config provider kubernetes account add](#hal-config-provider-kubernetes-account-add)
+- [hal config provider kubernetes account delete](#hal-config-provider-kubernetes-account-delete)
+- [hal config provider kubernetes account edit](#hal-config-provider-kubernetes-account-edit)
+- [hal config provider kubernetes account get](#hal-config-provider-kubernetes-account-get)
+- [hal config provider kubernetes account list](#hal-config-provider-kubernetes-account-list)
+- [hal config provider kubernetes disable](#hal-config-provider-kubernetes-disable)
+- [hal config provider kubernetes edit](#hal-config-provider-kubernetes-edit)
+- [hal config provider kubernetes enable](#hal-config-provider-kubernetes-enable)
+- [hal config provider oracle](#hal-config-provider-oracle)
+- [hal config provider oracle account](#hal-config-provider-oracle-account)
+- [hal config provider oracle account add](#hal-config-provider-oracle-account-add)
+- [hal config provider oracle account delete](#hal-config-provider-oracle-account-delete)
+- [hal config provider oracle account edit](#hal-config-provider-oracle-account-edit)
+- [hal config provider oracle account get](#hal-config-provider-oracle-account-get)
+- [hal config provider oracle account list](#hal-config-provider-oracle-account-list)
+- [hal config provider oracle bakery](#hal-config-provider-oracle-bakery)
+- [hal config provider oracle bakery base-image](#hal-config-provider-oracle-bakery-base-image)
+- [hal config provider oracle bakery base-image add](#hal-config-provider-oracle-bakery-base-image-add)
+- [hal config provider oracle bakery base-image delete](#hal-config-provider-oracle-bakery-base-image-delete)
+- [hal config provider oracle bakery base-image edit](#hal-config-provider-oracle-bakery-base-image-edit)
+- [hal config provider oracle bakery base-image get](#hal-config-provider-oracle-bakery-base-image-get)
+- [hal config provider oracle bakery base-image list](#hal-config-provider-oracle-bakery-base-image-list)
+- [hal config provider oracle bakery edit](#hal-config-provider-oracle-bakery-edit)
+- [hal config provider oracle disable](#hal-config-provider-oracle-disable)
+- [hal config provider oracle enable](#hal-config-provider-oracle-enable)
+- [hal config provider tencentcloud](#hal-config-provider-tencentcloud)
+- [hal config provider tencentcloud account](#hal-config-provider-tencentcloud-account)
+- [hal config provider tencentcloud account add](#hal-config-provider-tencentcloud-account-add)
+- [hal config provider tencentcloud account delete](#hal-config-provider-tencentcloud-account-delete)
+- [hal config provider tencentcloud account edit](#hal-config-provider-tencentcloud-account-edit)
+- [hal config provider tencentcloud account get](#hal-config-provider-tencentcloud-account-get)
+- [hal config provider tencentcloud account list](#hal-config-provider-tencentcloud-account-list)
+- [hal config provider tencentcloud bakery](#hal-config-provider-tencentcloud-bakery)
+- [hal config provider tencentcloud bakery base-image](#hal-config-provider-tencentcloud-bakery-base-image)
+- [hal config provider tencentcloud bakery base-image add](#hal-config-provider-tencentcloud-bakery-base-image-add)
+- [hal config provider tencentcloud bakery base-image delete](#hal-config-provider-tencentcloud-bakery-base-image-delete)
+- [hal config provider tencentcloud bakery base-image edit](#hal-config-provider-tencentcloud-bakery-base-image-edit)
+- [hal config provider tencentcloud bakery base-image get](#hal-config-provider-tencentcloud-bakery-base-image-get)
+- [hal config provider tencentcloud bakery base-image list](#hal-config-provider-tencentcloud-bakery-base-image-list)
+- [hal config provider tencentcloud bakery edit](#hal-config-provider-tencentcloud-bakery-edit)
+- [hal config provider tencentcloud disable](#hal-config-provider-tencentcloud-disable)
+- [hal config provider tencentcloud enable](#hal-config-provider-tencentcloud-enable)
+- [hal config pubsub](#hal-config-pubsub)
+- [hal config pubsub google](#hal-config-pubsub-google)
+- [hal config pubsub google disable](#hal-config-pubsub-google-disable)
+- [hal config pubsub google enable](#hal-config-pubsub-google-enable)
+- [hal config pubsub google subscription](#hal-config-pubsub-google-subscription)
+- [hal config pubsub google subscription add](#hal-config-pubsub-google-subscription-add)
+- [hal config pubsub google subscription delete](#hal-config-pubsub-google-subscription-delete)
+- [hal config pubsub google subscription edit](#hal-config-pubsub-google-subscription-edit)
+- [hal config pubsub google subscription get](#hal-config-pubsub-google-subscription-get)
+- [hal config pubsub google subscription list](#hal-config-pubsub-google-subscription-list)
+- [hal config repository](#hal-config-repository)
+- [hal config repository artifactory](#hal-config-repository-artifactory)
+- [hal config repository artifactory disable](#hal-config-repository-artifactory-disable)
+- [hal config repository artifactory enable](#hal-config-repository-artifactory-enable)
+- [hal config repository artifactory search](#hal-config-repository-artifactory-search)
+- [hal config repository artifactory search add](#hal-config-repository-artifactory-search-add)
+- [hal config repository artifactory search delete](#hal-config-repository-artifactory-search-delete)
+- [hal config repository artifactory search edit](#hal-config-repository-artifactory-search-edit)
+- [hal config repository artifactory search get](#hal-config-repository-artifactory-search-get)
+- [hal config repository artifactory search list](#hal-config-repository-artifactory-search-list)
+- [hal config security](#hal-config-security)
+- [hal config security api](#hal-config-security-api)
+- [hal config security api edit](#hal-config-security-api-edit)
+- [hal config security api ssl](#hal-config-security-api-ssl)
+- [hal config security api ssl disable](#hal-config-security-api-ssl-disable)
+- [hal config security api ssl edit](#hal-config-security-api-ssl-edit)
+- [hal config security api ssl enable](#hal-config-security-api-ssl-enable)
+- [hal config security authn](#hal-config-security-authn)
+- [hal config security authn iap](#hal-config-security-authn-iap)
+- [hal config security authn iap disable](#hal-config-security-authn-iap-disable)
+- [hal config security authn iap edit](#hal-config-security-authn-iap-edit)
+- [hal config security authn iap enable](#hal-config-security-authn-iap-enable)
+- [hal config security authn ldap](#hal-config-security-authn-ldap)
+- [hal config security authn ldap disable](#hal-config-security-authn-ldap-disable)
+- [hal config security authn ldap edit](#hal-config-security-authn-ldap-edit)
+- [hal config security authn ldap enable](#hal-config-security-authn-ldap-enable)
+- [hal config security authn oauth2](#hal-config-security-authn-oauth2)
+- [hal config security authn oauth2 disable](#hal-config-security-authn-oauth2-disable)
+- [hal config security authn oauth2 edit](#hal-config-security-authn-oauth2-edit)
+- [hal config security authn oauth2 enable](#hal-config-security-authn-oauth2-enable)
+- [hal config security authn saml](#hal-config-security-authn-saml)
+- [hal config security authn saml disable](#hal-config-security-authn-saml-disable)
+- [hal config security authn saml edit](#hal-config-security-authn-saml-edit)
+- [hal config security authn saml enable](#hal-config-security-authn-saml-enable)
+- [hal config security authn x509](#hal-config-security-authn-x509)
+- [hal config security authn x509 disable](#hal-config-security-authn-x509-disable)
+- [hal config security authn x509 edit](#hal-config-security-authn-x509-edit)
+- [hal config security authn x509 enable](#hal-config-security-authn-x509-enable)
+- [hal config security authz](#hal-config-security-authz)
+- [hal config security authz disable](#hal-config-security-authz-disable)
+- [hal config security authz edit](#hal-config-security-authz-edit)
+- [hal config security authz enable](#hal-config-security-authz-enable)
+- [hal config security authz file](#hal-config-security-authz-file)
+- [hal config security authz file edit](#hal-config-security-authz-file-edit)
+- [hal config security authz github](#hal-config-security-authz-github)
+- [hal config security authz github edit](#hal-config-security-authz-github-edit)
+- [hal config security authz google](#hal-config-security-authz-google)
+- [hal config security authz google edit](#hal-config-security-authz-google-edit)
+- [hal config security authz ldap](#hal-config-security-authz-ldap)
+- [hal config security authz ldap edit](#hal-config-security-authz-ldap-edit)
+- [hal config security ui](#hal-config-security-ui)
+- [hal config security ui edit](#hal-config-security-ui-edit)
+- [hal config security ui ssl](#hal-config-security-ui-ssl)
+- [hal config security ui ssl disable](#hal-config-security-ui-ssl-disable)
+- [hal config security ui ssl edit](#hal-config-security-ui-ssl-edit)
+- [hal config security ui ssl enable](#hal-config-security-ui-ssl-enable)
+- [hal config stats](#hal-config-stats)
+- [hal config stats disable](#hal-config-stats-disable)
+- [hal config stats edit](#hal-config-stats-edit)
+- [hal config stats enable](#hal-config-stats-enable)
+- [hal config storage](#hal-config-storage)
+- [hal config storage azs](#hal-config-storage-azs)
+- [hal config storage azs edit](#hal-config-storage-azs-edit)
+- [hal config storage edit](#hal-config-storage-edit)
+- [hal config storage gcs](#hal-config-storage-gcs)
+- [hal config storage gcs edit](#hal-config-storage-gcs-edit)
+- [hal config storage oracle](#hal-config-storage-oracle)
+- [hal config storage oracle edit](#hal-config-storage-oracle-edit)
+- [hal config storage s3](#hal-config-storage-s3)
+- [hal config storage s3 edit](#hal-config-storage-s3-edit)
+- [hal config version](#hal-config-version)
+- [hal config version edit](#hal-config-version-edit)
+- [hal config webhook](#hal-config-webhook)
+- [hal config webhook trust](#hal-config-webhook-trust)
+- [hal config webhook trust disable](#hal-config-webhook-trust-disable)
+- [hal config webhook trust edit](#hal-config-webhook-trust-edit)
+- [hal config webhook trust enable](#hal-config-webhook-trust-enable)
+- [hal deploy](#hal-deploy)
+- [hal deploy apply](#hal-deploy-apply)
+- [hal deploy clean](#hal-deploy-clean)
+- [hal deploy collect-logs](#hal-deploy-collect-logs)
+- [hal deploy connect](#hal-deploy-connect)
+- [hal deploy details](#hal-deploy-details)
+- [hal deploy diff](#hal-deploy-diff)
+- [hal deploy rollback](#hal-deploy-rollback)
+- [hal plugins](#hal-plugins)
+- [hal plugins add](#hal-plugins-add)
+- [hal plugins delete](#hal-plugins-delete)
+- [hal plugins disable](#hal-plugins-disable)
+- [hal plugins disable-downloading](#hal-plugins-disable-downloading)
+- [hal plugins edit](#hal-plugins-edit)
+- [hal plugins enable](#hal-plugins-enable)
+- [hal plugins enable-downloading](#hal-plugins-enable-downloading)
+- [hal plugins list](#hal-plugins-list)
+- [hal plugins repository](#hal-plugins-repository)
+- [hal plugins repository add](#hal-plugins-repository-add)
+- [hal plugins repository delete](#hal-plugins-repository-delete)
+- [hal plugins repository edit](#hal-plugins-repository-edit)
+- [hal plugins repository list](#hal-plugins-repository-list)
+- [hal shutdown](#hal-shutdown)
+- [hal spin](#hal-spin)
+- [hal spin install](#hal-spin-install)
+- [hal task](#hal-task)
+- [hal task interrupt](#hal-task-interrupt)
+- [hal task list](#hal-task-list)
+- [hal version](#hal-version)
+- [hal version bom](#hal-version-bom)
+- [hal version latest](#hal-version-latest)
+- [hal version list](#hal-version-list)
- * [**hal**](#hal)
- * [**hal admin**](#hal-admin)
- * [**hal admin deprecate**](#hal-admin-deprecate)
- * [**hal admin deprecate version**](#hal-admin-deprecate-version)
- * [**hal admin publish**](#hal-admin-publish)
- * [**hal admin publish bom**](#hal-admin-publish-bom)
- * [**hal admin publish latest**](#hal-admin-publish-latest)
- * [**hal admin publish latest-halyard**](#hal-admin-publish-latest-halyard)
- * [**hal admin publish latest-spinnaker**](#hal-admin-publish-latest-spinnaker)
- * [**hal admin publish profile**](#hal-admin-publish-profile)
- * [**hal admin publish version**](#hal-admin-publish-version)
- * [**hal backup**](#hal-backup)
- * [**hal backup create**](#hal-backup-create)
- * [**hal backup restore**](#hal-backup-restore)
- * [**hal config**](#hal-config)
- * [**hal config artifact**](#hal-config-artifact)
- * [**hal config artifact bitbucket**](#hal-config-artifact-bitbucket)
- * [**hal config artifact bitbucket account**](#hal-config-artifact-bitbucket-account)
- * [**hal config artifact bitbucket account add**](#hal-config-artifact-bitbucket-account-add)
- * [**hal config artifact bitbucket account delete**](#hal-config-artifact-bitbucket-account-delete)
- * [**hal config artifact bitbucket account edit**](#hal-config-artifact-bitbucket-account-edit)
- * [**hal config artifact bitbucket account get**](#hal-config-artifact-bitbucket-account-get)
- * [**hal config artifact bitbucket account list**](#hal-config-artifact-bitbucket-account-list)
- * [**hal config artifact bitbucket disable**](#hal-config-artifact-bitbucket-disable)
- * [**hal config artifact bitbucket enable**](#hal-config-artifact-bitbucket-enable)
- * [**hal config artifact gcs**](#hal-config-artifact-gcs)
- * [**hal config artifact gcs account**](#hal-config-artifact-gcs-account)
- * [**hal config artifact gcs account add**](#hal-config-artifact-gcs-account-add)
- * [**hal config artifact gcs account delete**](#hal-config-artifact-gcs-account-delete)
- * [**hal config artifact gcs account edit**](#hal-config-artifact-gcs-account-edit)
- * [**hal config artifact gcs account get**](#hal-config-artifact-gcs-account-get)
- * [**hal config artifact gcs account list**](#hal-config-artifact-gcs-account-list)
- * [**hal config artifact gcs disable**](#hal-config-artifact-gcs-disable)
- * [**hal config artifact gcs enable**](#hal-config-artifact-gcs-enable)
- * [**hal config artifact github**](#hal-config-artifact-github)
- * [**hal config artifact github account**](#hal-config-artifact-github-account)
- * [**hal config artifact github account add**](#hal-config-artifact-github-account-add)
- * [**hal config artifact github account delete**](#hal-config-artifact-github-account-delete)
- * [**hal config artifact github account edit**](#hal-config-artifact-github-account-edit)
- * [**hal config artifact github account get**](#hal-config-artifact-github-account-get)
- * [**hal config artifact github account list**](#hal-config-artifact-github-account-list)
- * [**hal config artifact github disable**](#hal-config-artifact-github-disable)
- * [**hal config artifact github enable**](#hal-config-artifact-github-enable)
- * [**hal config artifact gitlab**](#hal-config-artifact-gitlab)
- * [**hal config artifact gitlab account**](#hal-config-artifact-gitlab-account)
- * [**hal config artifact gitlab account add**](#hal-config-artifact-gitlab-account-add)
- * [**hal config artifact gitlab account delete**](#hal-config-artifact-gitlab-account-delete)
- * [**hal config artifact gitlab account edit**](#hal-config-artifact-gitlab-account-edit)
- * [**hal config artifact gitlab account get**](#hal-config-artifact-gitlab-account-get)
- * [**hal config artifact gitlab account list**](#hal-config-artifact-gitlab-account-list)
- * [**hal config artifact gitlab disable**](#hal-config-artifact-gitlab-disable)
- * [**hal config artifact gitlab enable**](#hal-config-artifact-gitlab-enable)
- * [**hal config artifact gitrepo**](#hal-config-artifact-gitrepo)
- * [**hal config artifact gitrepo account**](#hal-config-artifact-gitrepo-account)
- * [**hal config artifact gitrepo account add**](#hal-config-artifact-gitrepo-account-add)
- * [**hal config artifact gitrepo account delete**](#hal-config-artifact-gitrepo-account-delete)
- * [**hal config artifact gitrepo account edit**](#hal-config-artifact-gitrepo-account-edit)
- * [**hal config artifact gitrepo account get**](#hal-config-artifact-gitrepo-account-get)
- * [**hal config artifact gitrepo account list**](#hal-config-artifact-gitrepo-account-list)
- * [**hal config artifact gitrepo disable**](#hal-config-artifact-gitrepo-disable)
- * [**hal config artifact gitrepo enable**](#hal-config-artifact-gitrepo-enable)
- * [**hal config artifact helm**](#hal-config-artifact-helm)
- * [**hal config artifact helm account**](#hal-config-artifact-helm-account)
- * [**hal config artifact helm account add**](#hal-config-artifact-helm-account-add)
- * [**hal config artifact helm account delete**](#hal-config-artifact-helm-account-delete)
- * [**hal config artifact helm account edit**](#hal-config-artifact-helm-account-edit)
- * [**hal config artifact helm account get**](#hal-config-artifact-helm-account-get)
- * [**hal config artifact helm account list**](#hal-config-artifact-helm-account-list)
- * [**hal config artifact helm disable**](#hal-config-artifact-helm-disable)
- * [**hal config artifact helm enable**](#hal-config-artifact-helm-enable)
- * [**hal config artifact http**](#hal-config-artifact-http)
- * [**hal config artifact http account**](#hal-config-artifact-http-account)
- * [**hal config artifact http account add**](#hal-config-artifact-http-account-add)
- * [**hal config artifact http account delete**](#hal-config-artifact-http-account-delete)
- * [**hal config artifact http account edit**](#hal-config-artifact-http-account-edit)
- * [**hal config artifact http account get**](#hal-config-artifact-http-account-get)
- * [**hal config artifact http account list**](#hal-config-artifact-http-account-list)
- * [**hal config artifact http disable**](#hal-config-artifact-http-disable)
- * [**hal config artifact http enable**](#hal-config-artifact-http-enable)
- * [**hal config artifact maven**](#hal-config-artifact-maven)
- * [**hal config artifact maven account**](#hal-config-artifact-maven-account)
- * [**hal config artifact maven account add**](#hal-config-artifact-maven-account-add)
- * [**hal config artifact maven account delete**](#hal-config-artifact-maven-account-delete)
- * [**hal config artifact maven account edit**](#hal-config-artifact-maven-account-edit)
- * [**hal config artifact maven account get**](#hal-config-artifact-maven-account-get)
- * [**hal config artifact maven account list**](#hal-config-artifact-maven-account-list)
- * [**hal config artifact maven disable**](#hal-config-artifact-maven-disable)
- * [**hal config artifact maven enable**](#hal-config-artifact-maven-enable)
- * [**hal config artifact oracle**](#hal-config-artifact-oracle)
- * [**hal config artifact oracle account**](#hal-config-artifact-oracle-account)
- * [**hal config artifact oracle account add**](#hal-config-artifact-oracle-account-add)
- * [**hal config artifact oracle account delete**](#hal-config-artifact-oracle-account-delete)
- * [**hal config artifact oracle account edit**](#hal-config-artifact-oracle-account-edit)
- * [**hal config artifact oracle account get**](#hal-config-artifact-oracle-account-get)
- * [**hal config artifact oracle account list**](#hal-config-artifact-oracle-account-list)
- * [**hal config artifact oracle disable**](#hal-config-artifact-oracle-disable)
- * [**hal config artifact oracle enable**](#hal-config-artifact-oracle-enable)
- * [**hal config artifact s3**](#hal-config-artifact-s3)
- * [**hal config artifact s3 account**](#hal-config-artifact-s3-account)
- * [**hal config artifact s3 account add**](#hal-config-artifact-s3-account-add)
- * [**hal config artifact s3 account delete**](#hal-config-artifact-s3-account-delete)
- * [**hal config artifact s3 account edit**](#hal-config-artifact-s3-account-edit)
- * [**hal config artifact s3 account get**](#hal-config-artifact-s3-account-get)
- * [**hal config artifact s3 account list**](#hal-config-artifact-s3-account-list)
- * [**hal config artifact s3 disable**](#hal-config-artifact-s3-disable)
- * [**hal config artifact s3 enable**](#hal-config-artifact-s3-enable)
- * [**hal config artifact templates**](#hal-config-artifact-templates)
- * [**hal config artifact templates add**](#hal-config-artifact-templates-add)
- * [**hal config artifact templates delete**](#hal-config-artifact-templates-delete)
- * [**hal config artifact templates edit**](#hal-config-artifact-templates-edit)
- * [**hal config artifact templates list**](#hal-config-artifact-templates-list)
- * [**hal config canary**](#hal-config-canary)
- * [**hal config canary aws**](#hal-config-canary-aws)
- * [**hal config canary aws account**](#hal-config-canary-aws-account)
- * [**hal config canary aws account add**](#hal-config-canary-aws-account-add)
- * [**hal config canary aws account delete**](#hal-config-canary-aws-account-delete)
- * [**hal config canary aws account edit**](#hal-config-canary-aws-account-edit)
- * [**hal config canary aws account get**](#hal-config-canary-aws-account-get)
- * [**hal config canary aws account list**](#hal-config-canary-aws-account-list)
- * [**hal config canary aws disable**](#hal-config-canary-aws-disable)
- * [**hal config canary aws edit**](#hal-config-canary-aws-edit)
- * [**hal config canary aws enable**](#hal-config-canary-aws-enable)
- * [**hal config canary datadog**](#hal-config-canary-datadog)
- * [**hal config canary datadog account**](#hal-config-canary-datadog-account)
- * [**hal config canary datadog account add**](#hal-config-canary-datadog-account-add)
- * [**hal config canary datadog account delete**](#hal-config-canary-datadog-account-delete)
- * [**hal config canary datadog account edit**](#hal-config-canary-datadog-account-edit)
- * [**hal config canary datadog account get**](#hal-config-canary-datadog-account-get)
- * [**hal config canary datadog account list**](#hal-config-canary-datadog-account-list)
- * [**hal config canary datadog disable**](#hal-config-canary-datadog-disable)
- * [**hal config canary datadog enable**](#hal-config-canary-datadog-enable)
- * [**hal config canary disable**](#hal-config-canary-disable)
- * [**hal config canary edit**](#hal-config-canary-edit)
- * [**hal config canary enable**](#hal-config-canary-enable)
- * [**hal config canary google**](#hal-config-canary-google)
- * [**hal config canary google account**](#hal-config-canary-google-account)
- * [**hal config canary google account add**](#hal-config-canary-google-account-add)
- * [**hal config canary google account delete**](#hal-config-canary-google-account-delete)
- * [**hal config canary google account edit**](#hal-config-canary-google-account-edit)
- * [**hal config canary google account get**](#hal-config-canary-google-account-get)
- * [**hal config canary google account list**](#hal-config-canary-google-account-list)
- * [**hal config canary google disable**](#hal-config-canary-google-disable)
- * [**hal config canary google edit**](#hal-config-canary-google-edit)
- * [**hal config canary google enable**](#hal-config-canary-google-enable)
- * [**hal config canary newrelic**](#hal-config-canary-newrelic)
- * [**hal config canary newrelic account**](#hal-config-canary-newrelic-account)
- * [**hal config canary newrelic account add**](#hal-config-canary-newrelic-account-add)
- * [**hal config canary newrelic account delete**](#hal-config-canary-newrelic-account-delete)
- * [**hal config canary newrelic account edit**](#hal-config-canary-newrelic-account-edit)
- * [**hal config canary newrelic account get**](#hal-config-canary-newrelic-account-get)
- * [**hal config canary newrelic account list**](#hal-config-canary-newrelic-account-list)
- * [**hal config canary newrelic disable**](#hal-config-canary-newrelic-disable)
- * [**hal config canary newrelic enable**](#hal-config-canary-newrelic-enable)
- * [**hal config canary prometheus**](#hal-config-canary-prometheus)
- * [**hal config canary prometheus account**](#hal-config-canary-prometheus-account)
- * [**hal config canary prometheus account add**](#hal-config-canary-prometheus-account-add)
- * [**hal config canary prometheus account delete**](#hal-config-canary-prometheus-account-delete)
- * [**hal config canary prometheus account edit**](#hal-config-canary-prometheus-account-edit)
- * [**hal config canary prometheus account get**](#hal-config-canary-prometheus-account-get)
- * [**hal config canary prometheus account list**](#hal-config-canary-prometheus-account-list)
- * [**hal config canary prometheus disable**](#hal-config-canary-prometheus-disable)
- * [**hal config canary prometheus edit**](#hal-config-canary-prometheus-edit)
- * [**hal config canary prometheus enable**](#hal-config-canary-prometheus-enable)
- * [**hal config canary signalfx**](#hal-config-canary-signalfx)
- * [**hal config canary signalfx account**](#hal-config-canary-signalfx-account)
- * [**hal config canary signalfx account add**](#hal-config-canary-signalfx-account-add)
- * [**hal config canary signalfx account delete**](#hal-config-canary-signalfx-account-delete)
- * [**hal config canary signalfx account edit**](#hal-config-canary-signalfx-account-edit)
- * [**hal config canary signalfx account get**](#hal-config-canary-signalfx-account-get)
- * [**hal config canary signalfx account list**](#hal-config-canary-signalfx-account-list)
- * [**hal config canary signalfx disable**](#hal-config-canary-signalfx-disable)
- * [**hal config canary signalfx enable**](#hal-config-canary-signalfx-enable)
- * [**hal config ci**](#hal-config-ci)
- * [**hal config ci codebuild**](#hal-config-ci-codebuild)
- * [**hal config ci codebuild account**](#hal-config-ci-codebuild-account)
- * [**hal config ci codebuild account add**](#hal-config-ci-codebuild-account-add)
- * [**hal config ci codebuild account delete**](#hal-config-ci-codebuild-account-delete)
- * [**hal config ci codebuild account edit**](#hal-config-ci-codebuild-account-edit)
- * [**hal config ci codebuild account get**](#hal-config-ci-codebuild-account-get)
- * [**hal config ci codebuild account list**](#hal-config-ci-codebuild-account-list)
- * [**hal config ci codebuild disable**](#hal-config-ci-codebuild-disable)
- * [**hal config ci codebuild edit**](#hal-config-ci-codebuild-edit)
- * [**hal config ci codebuild enable**](#hal-config-ci-codebuild-enable)
- * [**hal config ci concourse**](#hal-config-ci-concourse)
- * [**hal config ci concourse disable**](#hal-config-ci-concourse-disable)
- * [**hal config ci concourse enable**](#hal-config-ci-concourse-enable)
- * [**hal config ci concourse master**](#hal-config-ci-concourse-master)
- * [**hal config ci concourse master add**](#hal-config-ci-concourse-master-add)
- * [**hal config ci concourse master delete**](#hal-config-ci-concourse-master-delete)
- * [**hal config ci concourse master edit**](#hal-config-ci-concourse-master-edit)
- * [**hal config ci concourse master get**](#hal-config-ci-concourse-master-get)
- * [**hal config ci concourse master list**](#hal-config-ci-concourse-master-list)
- * [**hal config ci gcb**](#hal-config-ci-gcb)
- * [**hal config ci gcb account**](#hal-config-ci-gcb-account)
- * [**hal config ci gcb account add**](#hal-config-ci-gcb-account-add)
- * [**hal config ci gcb account delete**](#hal-config-ci-gcb-account-delete)
- * [**hal config ci gcb account edit**](#hal-config-ci-gcb-account-edit)
- * [**hal config ci gcb account list**](#hal-config-ci-gcb-account-list)
- * [**hal config ci gcb disable**](#hal-config-ci-gcb-disable)
- * [**hal config ci gcb enable**](#hal-config-ci-gcb-enable)
- * [**hal config ci jenkins**](#hal-config-ci-jenkins)
- * [**hal config ci jenkins disable**](#hal-config-ci-jenkins-disable)
- * [**hal config ci jenkins enable**](#hal-config-ci-jenkins-enable)
- * [**hal config ci jenkins master**](#hal-config-ci-jenkins-master)
- * [**hal config ci jenkins master add**](#hal-config-ci-jenkins-master-add)
- * [**hal config ci jenkins master delete**](#hal-config-ci-jenkins-master-delete)
- * [**hal config ci jenkins master edit**](#hal-config-ci-jenkins-master-edit)
- * [**hal config ci jenkins master get**](#hal-config-ci-jenkins-master-get)
- * [**hal config ci jenkins master list**](#hal-config-ci-jenkins-master-list)
- * [**hal config ci travis**](#hal-config-ci-travis)
- * [**hal config ci travis disable**](#hal-config-ci-travis-disable)
- * [**hal config ci travis enable**](#hal-config-ci-travis-enable)
- * [**hal config ci travis master**](#hal-config-ci-travis-master)
- * [**hal config ci travis master add**](#hal-config-ci-travis-master-add)
- * [**hal config ci travis master delete**](#hal-config-ci-travis-master-delete)
- * [**hal config ci travis master edit**](#hal-config-ci-travis-master-edit)
- * [**hal config ci travis master get**](#hal-config-ci-travis-master-get)
- * [**hal config ci travis master list**](#hal-config-ci-travis-master-list)
- * [**hal config ci wercker**](#hal-config-ci-wercker)
- * [**hal config ci wercker disable**](#hal-config-ci-wercker-disable)
- * [**hal config ci wercker enable**](#hal-config-ci-wercker-enable)
- * [**hal config ci wercker master**](#hal-config-ci-wercker-master)
- * [**hal config ci wercker master add**](#hal-config-ci-wercker-master-add)
- * [**hal config ci wercker master delete**](#hal-config-ci-wercker-master-delete)
- * [**hal config ci wercker master edit**](#hal-config-ci-wercker-master-edit)
- * [**hal config ci wercker master get**](#hal-config-ci-wercker-master-get)
- * [**hal config ci wercker master list**](#hal-config-ci-wercker-master-list)
- * [**hal config deploy**](#hal-config-deploy)
- * [**hal config deploy component-sizing**](#hal-config-deploy-component-sizing)
- * [**hal config deploy component-sizing clouddriver**](#hal-config-deploy-component-sizing-clouddriver)
- * [**hal config deploy component-sizing clouddriver delete**](#hal-config-deploy-component-sizing-clouddriver-delete)
- * [**hal config deploy component-sizing clouddriver edit**](#hal-config-deploy-component-sizing-clouddriver-edit)
- * [**hal config deploy component-sizing clouddriver-bootstrap**](#hal-config-deploy-component-sizing-clouddriver-bootstrap)
- * [**hal config deploy component-sizing clouddriver-bootstrap delete**](#hal-config-deploy-component-sizing-clouddriver-bootstrap-delete)
- * [**hal config deploy component-sizing clouddriver-bootstrap edit**](#hal-config-deploy-component-sizing-clouddriver-bootstrap-edit)
- * [**hal config deploy component-sizing clouddriver-caching**](#hal-config-deploy-component-sizing-clouddriver-caching)
- * [**hal config deploy component-sizing clouddriver-caching delete**](#hal-config-deploy-component-sizing-clouddriver-caching-delete)
- * [**hal config deploy component-sizing clouddriver-caching edit**](#hal-config-deploy-component-sizing-clouddriver-caching-edit)
- * [**hal config deploy component-sizing clouddriver-ro**](#hal-config-deploy-component-sizing-clouddriver-ro)
- * [**hal config deploy component-sizing clouddriver-ro delete**](#hal-config-deploy-component-sizing-clouddriver-ro-delete)
- * [**hal config deploy component-sizing clouddriver-ro edit**](#hal-config-deploy-component-sizing-clouddriver-ro-edit)
- * [**hal config deploy component-sizing clouddriver-ro-deck**](#hal-config-deploy-component-sizing-clouddriver-ro-deck)
- * [**hal config deploy component-sizing clouddriver-ro-deck delete**](#hal-config-deploy-component-sizing-clouddriver-ro-deck-delete)
- * [**hal config deploy component-sizing clouddriver-ro-deck edit**](#hal-config-deploy-component-sizing-clouddriver-ro-deck-edit)
- * [**hal config deploy component-sizing clouddriver-rw**](#hal-config-deploy-component-sizing-clouddriver-rw)
- * [**hal config deploy component-sizing clouddriver-rw delete**](#hal-config-deploy-component-sizing-clouddriver-rw-delete)
- * [**hal config deploy component-sizing clouddriver-rw edit**](#hal-config-deploy-component-sizing-clouddriver-rw-edit)
- * [**hal config deploy component-sizing consul-client**](#hal-config-deploy-component-sizing-consul-client)
- * [**hal config deploy component-sizing consul-client delete**](#hal-config-deploy-component-sizing-consul-client-delete)
- * [**hal config deploy component-sizing consul-client edit**](#hal-config-deploy-component-sizing-consul-client-edit)
- * [**hal config deploy component-sizing consul-server**](#hal-config-deploy-component-sizing-consul-server)
- * [**hal config deploy component-sizing consul-server delete**](#hal-config-deploy-component-sizing-consul-server-delete)
- * [**hal config deploy component-sizing consul-server edit**](#hal-config-deploy-component-sizing-consul-server-edit)
- * [**hal config deploy component-sizing deck**](#hal-config-deploy-component-sizing-deck)
- * [**hal config deploy component-sizing deck delete**](#hal-config-deploy-component-sizing-deck-delete)
- * [**hal config deploy component-sizing deck edit**](#hal-config-deploy-component-sizing-deck-edit)
- * [**hal config deploy component-sizing echo**](#hal-config-deploy-component-sizing-echo)
- * [**hal config deploy component-sizing echo delete**](#hal-config-deploy-component-sizing-echo-delete)
- * [**hal config deploy component-sizing echo edit**](#hal-config-deploy-component-sizing-echo-edit)
- * [**hal config deploy component-sizing echo-scheduler**](#hal-config-deploy-component-sizing-echo-scheduler)
- * [**hal config deploy component-sizing echo-scheduler delete**](#hal-config-deploy-component-sizing-echo-scheduler-delete)
- * [**hal config deploy component-sizing echo-scheduler edit**](#hal-config-deploy-component-sizing-echo-scheduler-edit)
- * [**hal config deploy component-sizing echo-worker**](#hal-config-deploy-component-sizing-echo-worker)
- * [**hal config deploy component-sizing echo-worker delete**](#hal-config-deploy-component-sizing-echo-worker-delete)
- * [**hal config deploy component-sizing echo-worker edit**](#hal-config-deploy-component-sizing-echo-worker-edit)
- * [**hal config deploy component-sizing fiat**](#hal-config-deploy-component-sizing-fiat)
- * [**hal config deploy component-sizing fiat delete**](#hal-config-deploy-component-sizing-fiat-delete)
- * [**hal config deploy component-sizing fiat edit**](#hal-config-deploy-component-sizing-fiat-edit)
- * [**hal config deploy component-sizing front50**](#hal-config-deploy-component-sizing-front50)
- * [**hal config deploy component-sizing front50 delete**](#hal-config-deploy-component-sizing-front50-delete)
- * [**hal config deploy component-sizing front50 edit**](#hal-config-deploy-component-sizing-front50-edit)
- * [**hal config deploy component-sizing gate**](#hal-config-deploy-component-sizing-gate)
- * [**hal config deploy component-sizing gate delete**](#hal-config-deploy-component-sizing-gate-delete)
- * [**hal config deploy component-sizing gate edit**](#hal-config-deploy-component-sizing-gate-edit)
- * [**hal config deploy component-sizing igor**](#hal-config-deploy-component-sizing-igor)
- * [**hal config deploy component-sizing igor delete**](#hal-config-deploy-component-sizing-igor-delete)
- * [**hal config deploy component-sizing igor edit**](#hal-config-deploy-component-sizing-igor-edit)
- * [**hal config deploy component-sizing kayenta**](#hal-config-deploy-component-sizing-kayenta)
- * [**hal config deploy component-sizing kayenta delete**](#hal-config-deploy-component-sizing-kayenta-delete)
- * [**hal config deploy component-sizing kayenta edit**](#hal-config-deploy-component-sizing-kayenta-edit)
- * [**hal config deploy component-sizing monitoring-daemon**](#hal-config-deploy-component-sizing-monitoring-daemon)
- * [**hal config deploy component-sizing monitoring-daemon delete**](#hal-config-deploy-component-sizing-monitoring-daemon-delete)
- * [**hal config deploy component-sizing monitoring-daemon edit**](#hal-config-deploy-component-sizing-monitoring-daemon-edit)
- * [**hal config deploy component-sizing orca**](#hal-config-deploy-component-sizing-orca)
- * [**hal config deploy component-sizing orca delete**](#hal-config-deploy-component-sizing-orca-delete)
- * [**hal config deploy component-sizing orca edit**](#hal-config-deploy-component-sizing-orca-edit)
- * [**hal config deploy component-sizing orca-bootstrap**](#hal-config-deploy-component-sizing-orca-bootstrap)
- * [**hal config deploy component-sizing orca-bootstrap delete**](#hal-config-deploy-component-sizing-orca-bootstrap-delete)
- * [**hal config deploy component-sizing orca-bootstrap edit**](#hal-config-deploy-component-sizing-orca-bootstrap-edit)
- * [**hal config deploy component-sizing redis**](#hal-config-deploy-component-sizing-redis)
- * [**hal config deploy component-sizing redis delete**](#hal-config-deploy-component-sizing-redis-delete)
- * [**hal config deploy component-sizing redis edit**](#hal-config-deploy-component-sizing-redis-edit)
- * [**hal config deploy component-sizing redis-bootstrap**](#hal-config-deploy-component-sizing-redis-bootstrap)
- * [**hal config deploy component-sizing redis-bootstrap delete**](#hal-config-deploy-component-sizing-redis-bootstrap-delete)
- * [**hal config deploy component-sizing redis-bootstrap edit**](#hal-config-deploy-component-sizing-redis-bootstrap-edit)
- * [**hal config deploy component-sizing rosco**](#hal-config-deploy-component-sizing-rosco)
- * [**hal config deploy component-sizing rosco delete**](#hal-config-deploy-component-sizing-rosco-delete)
- * [**hal config deploy component-sizing rosco edit**](#hal-config-deploy-component-sizing-rosco-edit)
- * [**hal config deploy component-sizing vault-client**](#hal-config-deploy-component-sizing-vault-client)
- * [**hal config deploy component-sizing vault-client delete**](#hal-config-deploy-component-sizing-vault-client-delete)
- * [**hal config deploy component-sizing vault-client edit**](#hal-config-deploy-component-sizing-vault-client-edit)
- * [**hal config deploy component-sizing vault-server**](#hal-config-deploy-component-sizing-vault-server)
- * [**hal config deploy component-sizing vault-server delete**](#hal-config-deploy-component-sizing-vault-server-delete)
- * [**hal config deploy component-sizing vault-server edit**](#hal-config-deploy-component-sizing-vault-server-edit)
- * [**hal config deploy edit**](#hal-config-deploy-edit)
- * [**hal config deploy ha**](#hal-config-deploy-ha)
- * [**hal config deploy ha clouddriver**](#hal-config-deploy-ha-clouddriver)
- * [**hal config deploy ha clouddriver disable**](#hal-config-deploy-ha-clouddriver-disable)
- * [**hal config deploy ha clouddriver edit**](#hal-config-deploy-ha-clouddriver-edit)
- * [**hal config deploy ha clouddriver enable**](#hal-config-deploy-ha-clouddriver-enable)
- * [**hal config deploy ha echo**](#hal-config-deploy-ha-echo)
- * [**hal config deploy ha echo disable**](#hal-config-deploy-ha-echo-disable)
- * [**hal config deploy ha echo enable**](#hal-config-deploy-ha-echo-enable)
- * [**hal config edit**](#hal-config-edit)
- * [**hal config features**](#hal-config-features)
- * [**hal config features edit**](#hal-config-features-edit)
- * [**hal config generate**](#hal-config-generate)
- * [**hal config list**](#hal-config-list)
- * [**hal config metric-stores**](#hal-config-metric-stores)
- * [**hal config metric-stores datadog**](#hal-config-metric-stores-datadog)
- * [**hal config metric-stores datadog disable**](#hal-config-metric-stores-datadog-disable)
- * [**hal config metric-stores datadog edit**](#hal-config-metric-stores-datadog-edit)
- * [**hal config metric-stores datadog enable**](#hal-config-metric-stores-datadog-enable)
- * [**hal config metric-stores edit**](#hal-config-metric-stores-edit)
- * [**hal config metric-stores newrelic**](#hal-config-metric-stores-newrelic)
- * [**hal config metric-stores newrelic disable**](#hal-config-metric-stores-newrelic-disable)
- * [**hal config metric-stores newrelic edit**](#hal-config-metric-stores-newrelic-edit)
- * [**hal config metric-stores newrelic enable**](#hal-config-metric-stores-newrelic-enable)
- * [**hal config metric-stores prometheus**](#hal-config-metric-stores-prometheus)
- * [**hal config metric-stores prometheus disable**](#hal-config-metric-stores-prometheus-disable)
- * [**hal config metric-stores prometheus edit**](#hal-config-metric-stores-prometheus-edit)
- * [**hal config metric-stores prometheus enable**](#hal-config-metric-stores-prometheus-enable)
- * [**hal config metric-stores stackdriver**](#hal-config-metric-stores-stackdriver)
- * [**hal config metric-stores stackdriver disable**](#hal-config-metric-stores-stackdriver-disable)
- * [**hal config metric-stores stackdriver edit**](#hal-config-metric-stores-stackdriver-edit)
- * [**hal config metric-stores stackdriver enable**](#hal-config-metric-stores-stackdriver-enable)
- * [**hal config notification**](#hal-config-notification)
- * [**hal config notification github-status**](#hal-config-notification-github-status)
- * [**hal config notification github-status disable**](#hal-config-notification-github-status-disable)
- * [**hal config notification github-status edit**](#hal-config-notification-github-status-edit)
- * [**hal config notification github-status enable**](#hal-config-notification-github-status-enable)
- * [**hal config notification pubsub**](#hal-config-notification-pubsub)
- * [**hal config notification pubsub google**](#hal-config-notification-pubsub-google)
- * [**hal config notification pubsub google add**](#hal-config-notification-pubsub-google-add)
- * [**hal config notification pubsub google delete**](#hal-config-notification-pubsub-google-delete)
- * [**hal config notification pubsub google disable**](#hal-config-notification-pubsub-google-disable)
- * [**hal config notification pubsub google edit**](#hal-config-notification-pubsub-google-edit)
- * [**hal config notification pubsub google enable**](#hal-config-notification-pubsub-google-enable)
- * [**hal config notification pubsub google get**](#hal-config-notification-pubsub-google-get)
- * [**hal config notification pubsub google list**](#hal-config-notification-pubsub-google-list)
- * [**hal config notification slack**](#hal-config-notification-slack)
- * [**hal config notification slack disable**](#hal-config-notification-slack-disable)
- * [**hal config notification slack edit**](#hal-config-notification-slack-edit)
- * [**hal config notification slack enable**](#hal-config-notification-slack-enable)
- * [**hal config notification twilio**](#hal-config-notification-twilio)
- * [**hal config notification twilio disable**](#hal-config-notification-twilio-disable)
- * [**hal config notification twilio edit**](#hal-config-notification-twilio-edit)
- * [**hal config notification twilio enable**](#hal-config-notification-twilio-enable)
- * [**hal config provider**](#hal-config-provider)
- * [**hal config provider appengine**](#hal-config-provider-appengine)
- * [**hal config provider appengine account**](#hal-config-provider-appengine-account)
- * [**hal config provider appengine account add**](#hal-config-provider-appengine-account-add)
- * [**hal config provider appengine account delete**](#hal-config-provider-appengine-account-delete)
- * [**hal config provider appengine account edit**](#hal-config-provider-appengine-account-edit)
- * [**hal config provider appengine account get**](#hal-config-provider-appengine-account-get)
- * [**hal config provider appengine account list**](#hal-config-provider-appengine-account-list)
- * [**hal config provider appengine disable**](#hal-config-provider-appengine-disable)
- * [**hal config provider appengine edit**](#hal-config-provider-appengine-edit)
- * [**hal config provider appengine enable**](#hal-config-provider-appengine-enable)
- * [**hal config provider aws**](#hal-config-provider-aws)
- * [**hal config provider aws account**](#hal-config-provider-aws-account)
- * [**hal config provider aws account add**](#hal-config-provider-aws-account-add)
- * [**hal config provider aws account delete**](#hal-config-provider-aws-account-delete)
- * [**hal config provider aws account edit**](#hal-config-provider-aws-account-edit)
- * [**hal config provider aws account get**](#hal-config-provider-aws-account-get)
- * [**hal config provider aws account list**](#hal-config-provider-aws-account-list)
- * [**hal config provider aws bakery**](#hal-config-provider-aws-bakery)
- * [**hal config provider aws bakery edit**](#hal-config-provider-aws-bakery-edit)
- * [**hal config provider aws disable**](#hal-config-provider-aws-disable)
- * [**hal config provider aws edit**](#hal-config-provider-aws-edit)
- * [**hal config provider aws enable**](#hal-config-provider-aws-enable)
- * [**hal config provider aws features**](#hal-config-provider-aws-features)
- * [**hal config provider aws features edit**](#hal-config-provider-aws-features-edit)
- * [**hal config provider azure**](#hal-config-provider-azure)
- * [**hal config provider azure account**](#hal-config-provider-azure-account)
- * [**hal config provider azure account add**](#hal-config-provider-azure-account-add)
- * [**hal config provider azure account delete**](#hal-config-provider-azure-account-delete)
- * [**hal config provider azure account edit**](#hal-config-provider-azure-account-edit)
- * [**hal config provider azure account get**](#hal-config-provider-azure-account-get)
- * [**hal config provider azure account list**](#hal-config-provider-azure-account-list)
- * [**hal config provider azure bakery**](#hal-config-provider-azure-bakery)
- * [**hal config provider azure bakery base-image**](#hal-config-provider-azure-bakery-base-image)
- * [**hal config provider azure bakery base-image add**](#hal-config-provider-azure-bakery-base-image-add)
- * [**hal config provider azure bakery base-image delete**](#hal-config-provider-azure-bakery-base-image-delete)
- * [**hal config provider azure bakery base-image edit**](#hal-config-provider-azure-bakery-base-image-edit)
- * [**hal config provider azure bakery base-image get**](#hal-config-provider-azure-bakery-base-image-get)
- * [**hal config provider azure bakery base-image list**](#hal-config-provider-azure-bakery-base-image-list)
- * [**hal config provider azure bakery edit**](#hal-config-provider-azure-bakery-edit)
- * [**hal config provider azure disable**](#hal-config-provider-azure-disable)
- * [**hal config provider azure enable**](#hal-config-provider-azure-enable)
- * [**hal config provider cloudfoundry**](#hal-config-provider-cloudfoundry)
- * [**hal config provider cloudfoundry account**](#hal-config-provider-cloudfoundry-account)
- * [**hal config provider cloudfoundry account add**](#hal-config-provider-cloudfoundry-account-add)
- * [**hal config provider cloudfoundry account delete**](#hal-config-provider-cloudfoundry-account-delete)
- * [**hal config provider cloudfoundry account edit**](#hal-config-provider-cloudfoundry-account-edit)
- * [**hal config provider cloudfoundry account get**](#hal-config-provider-cloudfoundry-account-get)
- * [**hal config provider cloudfoundry account list**](#hal-config-provider-cloudfoundry-account-list)
- * [**hal config provider cloudfoundry disable**](#hal-config-provider-cloudfoundry-disable)
- * [**hal config provider cloudfoundry enable**](#hal-config-provider-cloudfoundry-enable)
- * [**hal config provider dcos**](#hal-config-provider-dcos)
- * [**hal config provider dcos account**](#hal-config-provider-dcos-account)
- * [**hal config provider dcos account add**](#hal-config-provider-dcos-account-add)
- * [**hal config provider dcos account delete**](#hal-config-provider-dcos-account-delete)
- * [**hal config provider dcos account edit**](#hal-config-provider-dcos-account-edit)
- * [**hal config provider dcos account get**](#hal-config-provider-dcos-account-get)
- * [**hal config provider dcos account list**](#hal-config-provider-dcos-account-list)
- * [**hal config provider dcos cluster**](#hal-config-provider-dcos-cluster)
- * [**hal config provider dcos cluster add**](#hal-config-provider-dcos-cluster-add)
- * [**hal config provider dcos cluster delete**](#hal-config-provider-dcos-cluster-delete)
- * [**hal config provider dcos cluster edit**](#hal-config-provider-dcos-cluster-edit)
- * [**hal config provider dcos cluster get**](#hal-config-provider-dcos-cluster-get)
- * [**hal config provider dcos cluster list**](#hal-config-provider-dcos-cluster-list)
- * [**hal config provider dcos disable**](#hal-config-provider-dcos-disable)
- * [**hal config provider dcos enable**](#hal-config-provider-dcos-enable)
- * [**hal config provider docker-registry**](#hal-config-provider-docker-registry)
- * [**hal config provider docker-registry account**](#hal-config-provider-docker-registry-account)
- * [**hal config provider docker-registry account add**](#hal-config-provider-docker-registry-account-add)
- * [**hal config provider docker-registry account delete**](#hal-config-provider-docker-registry-account-delete)
- * [**hal config provider docker-registry account edit**](#hal-config-provider-docker-registry-account-edit)
- * [**hal config provider docker-registry account get**](#hal-config-provider-docker-registry-account-get)
- * [**hal config provider docker-registry account list**](#hal-config-provider-docker-registry-account-list)
- * [**hal config provider docker-registry disable**](#hal-config-provider-docker-registry-disable)
- * [**hal config provider docker-registry enable**](#hal-config-provider-docker-registry-enable)
- * [**hal config provider ecs**](#hal-config-provider-ecs)
- * [**hal config provider ecs account**](#hal-config-provider-ecs-account)
- * [**hal config provider ecs account add**](#hal-config-provider-ecs-account-add)
- * [**hal config provider ecs account delete**](#hal-config-provider-ecs-account-delete)
- * [**hal config provider ecs account edit**](#hal-config-provider-ecs-account-edit)
- * [**hal config provider ecs account get**](#hal-config-provider-ecs-account-get)
- * [**hal config provider ecs account list**](#hal-config-provider-ecs-account-list)
- * [**hal config provider ecs disable**](#hal-config-provider-ecs-disable)
- * [**hal config provider ecs enable**](#hal-config-provider-ecs-enable)
- * [**hal config provider google**](#hal-config-provider-google)
- * [**hal config provider google account**](#hal-config-provider-google-account)
- * [**hal config provider google account add**](#hal-config-provider-google-account-add)
- * [**hal config provider google account delete**](#hal-config-provider-google-account-delete)
- * [**hal config provider google account edit**](#hal-config-provider-google-account-edit)
- * [**hal config provider google account get**](#hal-config-provider-google-account-get)
- * [**hal config provider google account list**](#hal-config-provider-google-account-list)
- * [**hal config provider google bakery**](#hal-config-provider-google-bakery)
- * [**hal config provider google bakery base-image**](#hal-config-provider-google-bakery-base-image)
- * [**hal config provider google bakery base-image add**](#hal-config-provider-google-bakery-base-image-add)
- * [**hal config provider google bakery base-image delete**](#hal-config-provider-google-bakery-base-image-delete)
- * [**hal config provider google bakery base-image edit**](#hal-config-provider-google-bakery-base-image-edit)
- * [**hal config provider google bakery base-image get**](#hal-config-provider-google-bakery-base-image-get)
- * [**hal config provider google bakery base-image list**](#hal-config-provider-google-bakery-base-image-list)
- * [**hal config provider google bakery edit**](#hal-config-provider-google-bakery-edit)
- * [**hal config provider google disable**](#hal-config-provider-google-disable)
- * [**hal config provider google edit**](#hal-config-provider-google-edit)
- * [**hal config provider google enable**](#hal-config-provider-google-enable)
- * [**hal config provider huaweicloud**](#hal-config-provider-huaweicloud)
- * [**hal config provider huaweicloud account**](#hal-config-provider-huaweicloud-account)
- * [**hal config provider huaweicloud account add**](#hal-config-provider-huaweicloud-account-add)
- * [**hal config provider huaweicloud account delete**](#hal-config-provider-huaweicloud-account-delete)
- * [**hal config provider huaweicloud account edit**](#hal-config-provider-huaweicloud-account-edit)
- * [**hal config provider huaweicloud account get**](#hal-config-provider-huaweicloud-account-get)
- * [**hal config provider huaweicloud account list**](#hal-config-provider-huaweicloud-account-list)
- * [**hal config provider huaweicloud bakery**](#hal-config-provider-huaweicloud-bakery)
- * [**hal config provider huaweicloud bakery base-image**](#hal-config-provider-huaweicloud-bakery-base-image)
- * [**hal config provider huaweicloud bakery base-image add**](#hal-config-provider-huaweicloud-bakery-base-image-add)
- * [**hal config provider huaweicloud bakery base-image delete**](#hal-config-provider-huaweicloud-bakery-base-image-delete)
- * [**hal config provider huaweicloud bakery base-image edit**](#hal-config-provider-huaweicloud-bakery-base-image-edit)
- * [**hal config provider huaweicloud bakery base-image get**](#hal-config-provider-huaweicloud-bakery-base-image-get)
- * [**hal config provider huaweicloud bakery base-image list**](#hal-config-provider-huaweicloud-bakery-base-image-list)
- * [**hal config provider huaweicloud bakery edit**](#hal-config-provider-huaweicloud-bakery-edit)
- * [**hal config provider huaweicloud disable**](#hal-config-provider-huaweicloud-disable)
- * [**hal config provider huaweicloud enable**](#hal-config-provider-huaweicloud-enable)
- * [**hal config provider kubernetes**](#hal-config-provider-kubernetes)
- * [**hal config provider kubernetes account**](#hal-config-provider-kubernetes-account)
- * [**hal config provider kubernetes account add**](#hal-config-provider-kubernetes-account-add)
- * [**hal config provider kubernetes account delete**](#hal-config-provider-kubernetes-account-delete)
- * [**hal config provider kubernetes account edit**](#hal-config-provider-kubernetes-account-edit)
- * [**hal config provider kubernetes account get**](#hal-config-provider-kubernetes-account-get)
- * [**hal config provider kubernetes account list**](#hal-config-provider-kubernetes-account-list)
- * [**hal config provider kubernetes disable**](#hal-config-provider-kubernetes-disable)
- * [**hal config provider kubernetes edit**](#hal-config-provider-kubernetes-edit)
- * [**hal config provider kubernetes enable**](#hal-config-provider-kubernetes-enable)
- * [**hal config provider oracle**](#hal-config-provider-oracle)
- * [**hal config provider oracle account**](#hal-config-provider-oracle-account)
- * [**hal config provider oracle account add**](#hal-config-provider-oracle-account-add)
- * [**hal config provider oracle account delete**](#hal-config-provider-oracle-account-delete)
- * [**hal config provider oracle account edit**](#hal-config-provider-oracle-account-edit)
- * [**hal config provider oracle account get**](#hal-config-provider-oracle-account-get)
- * [**hal config provider oracle account list**](#hal-config-provider-oracle-account-list)
- * [**hal config provider oracle bakery**](#hal-config-provider-oracle-bakery)
- * [**hal config provider oracle bakery base-image**](#hal-config-provider-oracle-bakery-base-image)
- * [**hal config provider oracle bakery base-image add**](#hal-config-provider-oracle-bakery-base-image-add)
- * [**hal config provider oracle bakery base-image delete**](#hal-config-provider-oracle-bakery-base-image-delete)
- * [**hal config provider oracle bakery base-image edit**](#hal-config-provider-oracle-bakery-base-image-edit)
- * [**hal config provider oracle bakery base-image get**](#hal-config-provider-oracle-bakery-base-image-get)
- * [**hal config provider oracle bakery base-image list**](#hal-config-provider-oracle-bakery-base-image-list)
- * [**hal config provider oracle bakery edit**](#hal-config-provider-oracle-bakery-edit)
- * [**hal config provider oracle disable**](#hal-config-provider-oracle-disable)
- * [**hal config provider oracle enable**](#hal-config-provider-oracle-enable)
- * [**hal config provider tencentcloud**](#hal-config-provider-tencentcloud)
- * [**hal config provider tencentcloud account**](#hal-config-provider-tencentcloud-account)
- * [**hal config provider tencentcloud account add**](#hal-config-provider-tencentcloud-account-add)
- * [**hal config provider tencentcloud account delete**](#hal-config-provider-tencentcloud-account-delete)
- * [**hal config provider tencentcloud account edit**](#hal-config-provider-tencentcloud-account-edit)
- * [**hal config provider tencentcloud account get**](#hal-config-provider-tencentcloud-account-get)
- * [**hal config provider tencentcloud account list**](#hal-config-provider-tencentcloud-account-list)
- * [**hal config provider tencentcloud bakery**](#hal-config-provider-tencentcloud-bakery)
- * [**hal config provider tencentcloud bakery base-image**](#hal-config-provider-tencentcloud-bakery-base-image)
- * [**hal config provider tencentcloud bakery base-image add**](#hal-config-provider-tencentcloud-bakery-base-image-add)
- * [**hal config provider tencentcloud bakery base-image delete**](#hal-config-provider-tencentcloud-bakery-base-image-delete)
- * [**hal config provider tencentcloud bakery base-image edit**](#hal-config-provider-tencentcloud-bakery-base-image-edit)
- * [**hal config provider tencentcloud bakery base-image get**](#hal-config-provider-tencentcloud-bakery-base-image-get)
- * [**hal config provider tencentcloud bakery base-image list**](#hal-config-provider-tencentcloud-bakery-base-image-list)
- * [**hal config provider tencentcloud bakery edit**](#hal-config-provider-tencentcloud-bakery-edit)
- * [**hal config provider tencentcloud disable**](#hal-config-provider-tencentcloud-disable)
- * [**hal config provider tencentcloud enable**](#hal-config-provider-tencentcloud-enable)
- * [**hal config pubsub**](#hal-config-pubsub)
- * [**hal config pubsub google**](#hal-config-pubsub-google)
- * [**hal config pubsub google disable**](#hal-config-pubsub-google-disable)
- * [**hal config pubsub google enable**](#hal-config-pubsub-google-enable)
- * [**hal config pubsub google subscription**](#hal-config-pubsub-google-subscription)
- * [**hal config pubsub google subscription add**](#hal-config-pubsub-google-subscription-add)
- * [**hal config pubsub google subscription delete**](#hal-config-pubsub-google-subscription-delete)
- * [**hal config pubsub google subscription edit**](#hal-config-pubsub-google-subscription-edit)
- * [**hal config pubsub google subscription get**](#hal-config-pubsub-google-subscription-get)
- * [**hal config pubsub google subscription list**](#hal-config-pubsub-google-subscription-list)
- * [**hal config repository**](#hal-config-repository)
- * [**hal config repository artifactory**](#hal-config-repository-artifactory)
- * [**hal config repository artifactory disable**](#hal-config-repository-artifactory-disable)
- * [**hal config repository artifactory enable**](#hal-config-repository-artifactory-enable)
- * [**hal config repository artifactory search**](#hal-config-repository-artifactory-search)
- * [**hal config repository artifactory search add**](#hal-config-repository-artifactory-search-add)
- * [**hal config repository artifactory search delete**](#hal-config-repository-artifactory-search-delete)
- * [**hal config repository artifactory search edit**](#hal-config-repository-artifactory-search-edit)
- * [**hal config repository artifactory search get**](#hal-config-repository-artifactory-search-get)
- * [**hal config repository artifactory search list**](#hal-config-repository-artifactory-search-list)
- * [**hal config security**](#hal-config-security)
- * [**hal config security api**](#hal-config-security-api)
- * [**hal config security api edit**](#hal-config-security-api-edit)
- * [**hal config security api ssl**](#hal-config-security-api-ssl)
- * [**hal config security api ssl disable**](#hal-config-security-api-ssl-disable)
- * [**hal config security api ssl edit**](#hal-config-security-api-ssl-edit)
- * [**hal config security api ssl enable**](#hal-config-security-api-ssl-enable)
- * [**hal config security authn**](#hal-config-security-authn)
- * [**hal config security authn iap**](#hal-config-security-authn-iap)
- * [**hal config security authn iap disable**](#hal-config-security-authn-iap-disable)
- * [**hal config security authn iap edit**](#hal-config-security-authn-iap-edit)
- * [**hal config security authn iap enable**](#hal-config-security-authn-iap-enable)
- * [**hal config security authn ldap**](#hal-config-security-authn-ldap)
- * [**hal config security authn ldap disable**](#hal-config-security-authn-ldap-disable)
- * [**hal config security authn ldap edit**](#hal-config-security-authn-ldap-edit)
- * [**hal config security authn ldap enable**](#hal-config-security-authn-ldap-enable)
- * [**hal config security authn oauth2**](#hal-config-security-authn-oauth2)
- * [**hal config security authn oauth2 disable**](#hal-config-security-authn-oauth2-disable)
- * [**hal config security authn oauth2 edit**](#hal-config-security-authn-oauth2-edit)
- * [**hal config security authn oauth2 enable**](#hal-config-security-authn-oauth2-enable)
- * [**hal config security authn saml**](#hal-config-security-authn-saml)
- * [**hal config security authn saml disable**](#hal-config-security-authn-saml-disable)
- * [**hal config security authn saml edit**](#hal-config-security-authn-saml-edit)
- * [**hal config security authn saml enable**](#hal-config-security-authn-saml-enable)
- * [**hal config security authn x509**](#hal-config-security-authn-x509)
- * [**hal config security authn x509 disable**](#hal-config-security-authn-x509-disable)
- * [**hal config security authn x509 edit**](#hal-config-security-authn-x509-edit)
- * [**hal config security authn x509 enable**](#hal-config-security-authn-x509-enable)
- * [**hal config security authz**](#hal-config-security-authz)
- * [**hal config security authz disable**](#hal-config-security-authz-disable)
- * [**hal config security authz edit**](#hal-config-security-authz-edit)
- * [**hal config security authz enable**](#hal-config-security-authz-enable)
- * [**hal config security authz file**](#hal-config-security-authz-file)
- * [**hal config security authz file edit**](#hal-config-security-authz-file-edit)
- * [**hal config security authz github**](#hal-config-security-authz-github)
- * [**hal config security authz github edit**](#hal-config-security-authz-github-edit)
- * [**hal config security authz google**](#hal-config-security-authz-google)
- * [**hal config security authz google edit**](#hal-config-security-authz-google-edit)
- * [**hal config security authz ldap**](#hal-config-security-authz-ldap)
- * [**hal config security authz ldap edit**](#hal-config-security-authz-ldap-edit)
- * [**hal config security ui**](#hal-config-security-ui)
- * [**hal config security ui edit**](#hal-config-security-ui-edit)
- * [**hal config security ui ssl**](#hal-config-security-ui-ssl)
- * [**hal config security ui ssl disable**](#hal-config-security-ui-ssl-disable)
- * [**hal config security ui ssl edit**](#hal-config-security-ui-ssl-edit)
- * [**hal config security ui ssl enable**](#hal-config-security-ui-ssl-enable)
- * [**hal config stats**](#hal-config-stats)
- * [**hal config stats disable**](#hal-config-stats-disable)
- * [**hal config stats edit**](#hal-config-stats-edit)
- * [**hal config stats enable**](#hal-config-stats-enable)
- * [**hal config storage**](#hal-config-storage)
- * [**hal config storage azs**](#hal-config-storage-azs)
- * [**hal config storage azs edit**](#hal-config-storage-azs-edit)
- * [**hal config storage edit**](#hal-config-storage-edit)
- * [**hal config storage gcs**](#hal-config-storage-gcs)
- * [**hal config storage gcs edit**](#hal-config-storage-gcs-edit)
- * [**hal config storage oracle**](#hal-config-storage-oracle)
- * [**hal config storage oracle edit**](#hal-config-storage-oracle-edit)
- * [**hal config storage s3**](#hal-config-storage-s3)
- * [**hal config storage s3 edit**](#hal-config-storage-s3-edit)
- * [**hal config version**](#hal-config-version)
- * [**hal config version edit**](#hal-config-version-edit)
- * [**hal config webhook**](#hal-config-webhook)
- * [**hal config webhook trust**](#hal-config-webhook-trust)
- * [**hal config webhook trust disable**](#hal-config-webhook-trust-disable)
- * [**hal config webhook trust edit**](#hal-config-webhook-trust-edit)
- * [**hal config webhook trust enable**](#hal-config-webhook-trust-enable)
- * [**hal deploy**](#hal-deploy)
- * [**hal deploy apply**](#hal-deploy-apply)
- * [**hal deploy clean**](#hal-deploy-clean)
- * [**hal deploy collect-logs**](#hal-deploy-collect-logs)
- * [**hal deploy connect**](#hal-deploy-connect)
- * [**hal deploy details**](#hal-deploy-details)
- * [**hal deploy diff**](#hal-deploy-diff)
- * [**hal deploy rollback**](#hal-deploy-rollback)
- * [**hal plugins**](#hal-plugins)
- * [**hal plugins add**](#hal-plugins-add)
- * [**hal plugins delete**](#hal-plugins-delete)
- * [**hal plugins disable**](#hal-plugins-disable)
- * [**hal plugins disable-downloading**](#hal-plugins-disable-downloading)
- * [**hal plugins edit**](#hal-plugins-edit)
- * [**hal plugins enable**](#hal-plugins-enable)
- * [**hal plugins enable-downloading**](#hal-plugins-enable-downloading)
- * [**hal plugins list**](#hal-plugins-list)
- * [**hal plugins repository**](#hal-plugins-repository)
- * [**hal plugins repository add**](#hal-plugins-repository-add)
- * [**hal plugins repository delete**](#hal-plugins-repository-delete)
- * [**hal plugins repository edit**](#hal-plugins-repository-edit)
- * [**hal plugins repository list**](#hal-plugins-repository-list)
- * [**hal shutdown**](#hal-shutdown)
- * [**hal spin**](#hal-spin)
- * [**hal spin install**](#hal-spin-install)
- * [**hal task**](#hal-task)
- * [**hal task interrupt**](#hal-task-interrupt)
- * [**hal task list**](#hal-task-list)
- * [**hal version**](#hal-version)
- * [**hal version bom**](#hal-version-bom)
- * [**hal version latest**](#hal-version-latest)
- * [**hal version list**](#hal-version-list)
## hal
A tool for configuring, installing, and updating Spinnaker.
If this is your first time using Halyard to install Spinnaker we recommend that you skim the documentation on [https://spinnaker.io/reference/halyard/](https://spinnaker.io/reference/halyard/) for some familiarity with the product. If at any point you get stuck using 'hal', every command can be suffixed with '--help' for usage information.
-
#### Usage
+
```
hal [parameters] [subcommands]
```
+
#### Global Parameters
- * `--daemon-endpoint`: If supplied, connect to the daemon at this address.
- * `--options`: Get options for the specified field name.
- * `-a, --alpha`: Enable alpha halyard features.
- * `-c, --color`: Enable terminal color output.
- * `-d, --debug`: Show detailed network traffic with halyard daemon.
- * `-h, --help`: (*Default*: `false`) Display help text about this command.
- * `-l, --log`: Set the log level of the CLI.
- * `-o, --output`: Format the CLIs output.
- * `-q, --quiet`: Show no task information or messages. When set, ANSI formatting will be disabled, and all prompts will be accepted.
-
-#### Parameters
- * `--docs`: (*Default*: `false`) Print markdown docs for the hal CLI.
- * `--print-bash-completion`: (*Default*: `false`) Print bash command completion. This is used during the installation of Halyard.
- * `--ready`: (*Default*: `false`) Check if Halyard is up and running. Will exit with non-zero return code when it isn't.
- * `--version, -v`: (*Default*: `false`) Version of Halyard.
-
-#### Subcommands
- * `admin`: This is meant for users building and publishing their own Spinnaker images and config.
- * `backup`: Backup and restore (remote or local) copies of your halconfig and all required files.
- * `config`: Configure, validate, and view your halconfig.
- * `deploy`: Manage the deployment of Spinnaker. This includes where it's deployed, what the infrastructure footprint looks like, what the currently running deployment looks like, etc...
- * `plugins`: Show Spinnaker's configured plugins.
- * `shutdown`: Shutdown the halyard daemon.
- * `spin`: Manage the lifecycle of spin CLI.
- * `task`: This set of commands exposes utilities of dealing with Halyard's task engine.
- * `version`: Get information about the available Spinnaker versions.
+
+- `--daemon-endpoint`: If supplied, connect to the daemon at this address.
+- `--options`: Get options for the specified field name.
+- `-a, --alpha`: Enable alpha halyard features.
+- `-c, --color`: Enable terminal color output.
+- `-d, --debug`: Show detailed network traffic with halyard daemon.
+- `-h, --help`: (_Default_: `false`) Display help text about this command.
+- `-l, --log`: Set the log level of the CLI.
+- `-o, --output`: Format the CLIs output.
+- `-q, --quiet`: Show no task information or messages. When set, ANSI formatting will be disabled, and all prompts will be accepted.
+
+#### Parameters
+
+- `--docs`: (_Default_: `false`) Print markdown docs for the hal CLI.
+- `--print-bash-completion`: (_Default_: `false`) Print bash command completion. This is used during the installation of Halyard.
+- `--ready`: (_Default_: `false`) Check if Halyard is up and running. Will exit with non-zero return code when it isn't.
+- `--version, -v`: (_Default_: `false`) Version of Halyard.
+
+#### Subcommands
+
+- `admin`: This is meant for users building and publishing their own Spinnaker images and config.
+- `backup`: Backup and restore (remote or local) copies of your halconfig and all required files.
+- `config`: Configure, validate, and view your halconfig.
+- `deploy`: Manage the deployment of Spinnaker. This includes where it's deployed, what the infrastructure footprint looks like, what the currently running deployment looks like, etc...
+- `plugins`: Show Spinnaker's configured plugins.
+- `shutdown`: Shutdown the halyard daemon.
+- `spin`: Manage the lifecycle of spin CLI.
+- `task`: This set of commands exposes utilities of dealing with Halyard's task engine.
+- `version`: Get information about the available Spinnaker versions.
---
+
## hal admin
This is meant for users building and publishing their own Spinnaker images and config.
#### Usage
+
```
hal admin [subcommands]
```
#### Subcommands
- * `deprecate`: Deprecate config artifacts in your configured halconfig bucket.
- * `publish`: Publish config artifacts to your configured halconfig bucket.
+
+- `deprecate`: Deprecate config artifacts in your configured halconfig bucket.
+- `publish`: Publish config artifacts to your configured halconfig bucket.
---
+
## hal admin deprecate
Deprecate config artifacts in your configured halconfig bucket.
#### Usage
+
```
hal admin deprecate [subcommands]
```
#### Subcommands
- * `version`: Deprecate a version of Spinnaker, removing it from the global versions.yml tracking file.
+
+- `version`: Deprecate a version of Spinnaker, removing it from the global versions.yml tracking file.
---
+
## hal admin deprecate version
Deprecate a version of Spinnaker, removing it from the global versions.yml tracking file.
#### Usage
+
```
hal admin deprecate version [parameters]
```
#### Parameters
- * `--illegal-reason`: If supplied, the version will not only be deprecated, but will no longer be installable by Halyard for the supplied reason
- * `--version`: (*Required*) The version (x.y.z) of Spinnaker to be deprecated.
+- `--illegal-reason`: If supplied, the version will not only be deprecated, but will no longer be installable by Halyard for the supplied reason
+- `--version`: (_Required_) The version (x.y.z) of Spinnaker to be deprecated.
---
+
## hal admin publish
Publish config artifacts to your configured halconfig bucket.
#### Usage
+
```
hal admin publish [subcommands]
```
#### Subcommands
- * `bom`: Publish a Bill of Materials (BOM).
- * `latest` _(Deprecated)_ : Publish the latest version of Spinnaker to the global versions.yml tracking file.
- * `latest-halyard`: Publish the latest version of Halyard to the global versions.yml tracking file.
- * `latest-spinnaker`: Publish the latest version of Spinnaker to the global versions.yml tracking file.
- * `profile`: Publish a base halconfig profile for a specific Spinnaker artifact.
- * `version`: Publish a version of Spinnaker to the global versions.yml tracking file.
+
+- `bom`: Publish a Bill of Materials (BOM).
+- `latest` _(Deprecated)_ : Publish the latest version of Spinnaker to the global versions.yml tracking file.
+- `latest-halyard`: Publish the latest version of Halyard to the global versions.yml tracking file.
+- `latest-spinnaker`: Publish the latest version of Spinnaker to the global versions.yml tracking file.
+- `profile`: Publish a base halconfig profile for a specific Spinnaker artifact.
+- `version`: Publish a version of Spinnaker to the global versions.yml tracking file.
---
+
## hal admin publish bom
Publish a Bill of Materials (BOM).
#### Usage
+
```
hal admin publish bom [parameters]
```
#### Parameters
- * `--bom-path`: (*Required*) The path to the BOM owning the artifact to publish.
+- `--bom-path`: (_Required_) The path to the BOM owning the artifact to publish.
---
+
## hal admin publish latest
Publish the latest version of Spinnaker to the global versions.yml tracking file.
#### Usage
+
```
hal admin publish latest VERSION
```
-
---
+
## hal admin publish latest-halyard
Publish the latest version of Halyard to the global versions.yml tracking file.
#### Usage
+
```
hal admin publish latest-halyard VERSION
```
-
---
+
## hal admin publish latest-spinnaker
Publish the latest version of Spinnaker to the global versions.yml tracking file.
#### Usage
+
```
hal admin publish latest-spinnaker VERSION
```
-
---
+
## hal admin publish profile
Publish a base halconfig profile for a specific Spinnaker artifact.
#### Usage
+
```
hal admin publish profile ARTIFACT-NAME [parameters]
```
#### Parameters
+
`ARTIFACT-NAME`: The name of the artifact whose profile is being published (e.g. clouddriver).
- * `--bom-path`: (*Required*) The path to the BOM owning the artifact to publish.
- * `--profile-path`: (*Required*) The path to the artifact profile to publish.
+- `--bom-path`: (_Required_) The path to the BOM owning the artifact to publish.
+- `--profile-path`: (_Required_) The path to the artifact profile to publish.
---
+
## hal admin publish version
Publish a version of Spinnaker to the global versions.yml tracking file.
#### Usage
+
```
hal admin publish version [parameters]
```
#### Parameters
- * `--alias`: (*Required*) The alias this version of Spinnaker goes by.
- * `--changelog`: (*Required*) A link to this Spinnaker release's changelog.
- * `--minimum-halyard-version`: (*Required*) Minimum version of halyard required to install this release
- * `--version`: (*Required*) The version (x.y.z) of Spinnaker to be recorded. This must exist as a BOM.
+- `--alias`: (_Required_) The alias this version of Spinnaker goes by.
+- `--changelog`: (_Required_) A link to this Spinnaker release's changelog.
+- `--minimum-halyard-version`: (_Required_) Minimum version of halyard required to install this release
+- `--version`: (_Required_) The version (x.y.z) of Spinnaker to be recorded. This must exist as a BOM.
---
+
## hal backup
This is used to periodically checkpoint your configured Spinnaker installation as well as allow you to store all aspects of your configured Spinnaker installation, to be picked up by an installation of Halyard on another machine.
#### Usage
+
```
hal backup [subcommands]
```
#### Subcommands
- * `create`: Create a backup of Halyard's state.
- * `restore`: Restore an existing backup.
+
+- `create`: Create a backup of Halyard's state.
+- `restore`: Restore an existing backup.
---
+
## hal backup create
This will create a tarball of your halconfig directory, being careful to rewrite file paths, so when the tarball is expanded by Halyard on another machine it will still be able to reference any files you have explicitly linked with your halconfig - e.g. --kubeconfig-file for Kubernetes, or --json-path for GCE.
#### Usage
+
```
hal backup create
```
-
---
+
## hal backup restore
Restore an existing backup. This backup does _not_ necessarily have to come from the machine it is being restored on - since all files referenced by your halconfig are included in the halconfig backup. As a result of this, keep in mind that after restoring a backup, all your required files are now in $halconfig/.backup/required-files.
#### Usage
+
```
hal backup restore [parameters]
```
#### Parameters
- * `--backup-path`: (*Required*) This is the path to the .tar file created by running `hal backup create`.
+- `--backup-path`: (_Required_) This is the path to the .tar file created by running `hal backup create`.
---
+
## hal config
Configure, validate, and view your halconfig.
#### Usage
+
```
hal config [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--set-current-deployment`: If supplied, set the current active deployment to the supplied value, creating it if need-be.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--set-current-deployment`: If supplied, set the current active deployment to the supplied value, creating it if need-be.
#### Subcommands
- * `artifact`: Configure, validate, and view the specified artifact provider.
- * `canary`: Configure your canary analysis settings for Spinnaker.
- * `ci`: Configure, validate, and view the specified Continuous Integration service.
- * `deploy`: Display the configured Spinnaker deployment.
- * `edit`: Configure top-level, global configuration parameters.
- * `features`: Display the state of Spinnaker's feature flags.
- * `generate`: Generate the full Spinnaker config for your current deployment. This does _not_ apply that configuration to your running Spinnaker installation. That either needs to be done manually, or with `hal deploy apply`.
- * `list`: Lists all deployments
- * `metric-stores`: Configure Spinnaker's metric stores. Metrics stores are used to store metrics for the various Spinnaker micro-services. These metrics are not related in any way to canary deployments. The technologies backing both are similar, but metrics stores are places to push metrics regarding Spinnaker metrics, whereas canary metrics stores are used to pull metrics to analyze deployments. This configuration only affects the publishing of metrics against whichever metric stores you enable (it can be more than one).
- * `notification`: Display the state of Spinnaker's notification settings.
- * `provider`: Configure, validate, and view the specified provider.
- * `pubsub`: Configure, validate, and view the specified pubsub.
- * `repository`: Configure, validate, and view the specified repository.
- * `security`: Configure Spinnaker's security. This includes external SSL, authentication mechanisms, and authorization policies.
- * `stats`: Show Spinnaker's stats settings.
- * `storage`: Show Spinnaker's persistent storage configuration.
- * `version`: Configure & view the current deployment of Spinnaker's version.
- * `webhook`: Show Spinnaker's webhook configuration.
+
+- `artifact`: Configure, validate, and view the specified artifact provider.
+- `canary`: Configure your canary analysis settings for Spinnaker.
+- `ci`: Configure, validate, and view the specified Continuous Integration service.
+- `deploy`: Display the configured Spinnaker deployment.
+- `edit`: Configure top-level, global configuration parameters.
+- `features`: Display the state of Spinnaker's feature flags.
+- `generate`: Generate the full Spinnaker config for your current deployment. This does _not_ apply that configuration to your running Spinnaker installation. That either needs to be done manually, or with `hal deploy apply`.
+- `list`: Lists all deployments
+- `metric-stores`: Configure Spinnaker's metric stores. Metrics stores are used to store metrics for the various Spinnaker micro-services. These metrics are not related in any way to canary deployments. The technologies backing both are similar, but metrics stores are places to push metrics regarding Spinnaker metrics, whereas canary metrics stores are used to pull metrics to analyze deployments. This configuration only affects the publishing of metrics against whichever metric stores you enable (it can be more than one).
+- `notification`: Display the state of Spinnaker's notification settings.
+- `provider`: Configure, validate, and view the specified provider.
+- `pubsub`: Configure, validate, and view the specified pubsub.
+- `repository`: Configure, validate, and view the specified repository.
+- `security`: Configure Spinnaker's security. This includes external SSL, authentication mechanisms, and authorization policies.
+- `stats`: Show Spinnaker's stats settings.
+- `storage`: Show Spinnaker's persistent storage configuration.
+- `version`: Configure & view the current deployment of Spinnaker's version.
+- `webhook`: Show Spinnaker's webhook configuration.
---
+
## hal config artifact
Configure, validate, and view the specified artifact provider.
#### Usage
+
```
hal config artifact [subcommands]
```
#### Subcommands
- * `bitbucket`: Manage and view Spinnaker configuration for the bitbucket provider
- * `gcs`: Manage and view Spinnaker configuration for the gcs provider
- * `github`: Manage and view Spinnaker configuration for the github provider
- * `gitlab`: Manage and view Spinnaker configuration for the gitlab provider
- * `gitrepo`: Manage and view Spinnaker configuration for the gitrepo provider
- * `helm`: Manage and view Spinnaker configuration for the helm provider
- * `http`: Manage and view Spinnaker configuration for the http provider
- * `maven`: Manage and view Spinnaker configuration for the maven provider
- * `oracle`: Manage and view Spinnaker configuration for the oracle provider
- * `s3`: Manage and view Spinnaker configuration for the s3 provider
- * `templates`: Show Spinnaker's configured artifact templates.
+
+- `bitbucket`: Manage and view Spinnaker configuration for the bitbucket provider
+- `gcs`: Manage and view Spinnaker configuration for the gcs provider
+- `github`: Manage and view Spinnaker configuration for the github provider
+- `gitlab`: Manage and view Spinnaker configuration for the gitlab provider
+- `gitrepo`: Manage and view Spinnaker configuration for the gitrepo provider
+- `helm`: Manage and view Spinnaker configuration for the helm provider
+- `http`: Manage and view Spinnaker configuration for the http provider
+- `maven`: Manage and view Spinnaker configuration for the maven provider
+- `oracle`: Manage and view Spinnaker configuration for the oracle provider
+- `s3`: Manage and view Spinnaker configuration for the s3 provider
+- `templates`: Show Spinnaker's configured artifact templates.
---
+
## hal config artifact bitbucket
Manage and view Spinnaker configuration for the bitbucket provider
#### Usage
+
```
hal config artifact bitbucket [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `account`: Manage and view Spinnaker configuration for the bitbucket artifact provider's account
- * `disable`: Set the bitbucket artifact provider as disabled
- * `enable`: Set the bitbucket artifact provider as enabled
+
+- `account`: Manage and view Spinnaker configuration for the bitbucket artifact provider's account
+- `disable`: Set the bitbucket artifact provider as disabled
+- `enable`: Set the bitbucket artifact provider as enabled
---
+
## hal config artifact bitbucket account
Manage and view Spinnaker configuration for the bitbucket artifact provider's account
#### Usage
+
```
hal config artifact bitbucket account ACCOUNT [parameters] [subcommands]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `add`: Add an artifact account to the bitbucket artifact provider.
- * `delete`: Delete a specific bitbucket artifact account by name.
- * `edit`: Edit an artifact account in the bitbucket artifact provider.
- * `get`: Get the specified account details for the bitbucket provider.
- * `list`: List the artifact account names for the bitbucket artifact provider.
+
+- `add`: Add an artifact account to the bitbucket artifact provider.
+- `delete`: Delete a specific bitbucket artifact account by name.
+- `edit`: Edit an artifact account in the bitbucket artifact provider.
+- `get`: Get the specified account details for the bitbucket provider.
+- `list`: List the artifact account names for the bitbucket artifact provider.
---
+
## hal config artifact bitbucket account add
Add an artifact account to the bitbucket artifact provider.
#### Usage
+
```
hal config artifact bitbucket account add ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--password`: (*Sensitive data* - user will be prompted on standard input) Bitbucket password
- * `--username`: Bitbucket username
- * `--username-password-file`: File containing "username:password" to use for Bitbucket authentication
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--password`: (_Sensitive data_ - user will be prompted on standard input) Bitbucket password
+- `--username`: Bitbucket username
+- `--username-password-file`: File containing "username:password" to use for Bitbucket authentication
---
+
## hal config artifact bitbucket account delete
Delete a specific bitbucket artifact account by name.
#### Usage
+
```
hal config artifact bitbucket account delete ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config artifact bitbucket account edit
Edit an artifact account in the bitbucket artifact provider.
#### Usage
+
```
hal config artifact bitbucket account edit ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--password`: (*Sensitive data* - user will be prompted on standard input) Bitbucket password
- * `--username`: Bitbucket username
- * `--username-password-file`: File containing "username:password" to use for Bitbucket authentication
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--password`: (_Sensitive data_ - user will be prompted on standard input) Bitbucket password
+- `--username`: Bitbucket username
+- `--username-password-file`: File containing "username:password" to use for Bitbucket authentication
---
+
## hal config artifact bitbucket account get
Get the specified account details for the bitbucket provider.
#### Usage
+
```
hal config artifact bitbucket account get ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config artifact bitbucket account list
List the artifact account names for the bitbucket artifact provider.
#### Usage
+
```
hal config artifact bitbucket account list [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config artifact bitbucket disable
Set the bitbucket artifact provider as disabled
#### Usage
+
```
hal config artifact bitbucket disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config artifact bitbucket enable
Set the bitbucket artifact provider as enabled
#### Usage
+
```
hal config artifact bitbucket enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config artifact gcs
Manage and view Spinnaker configuration for the gcs provider
#### Usage
+
```
hal config artifact gcs [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `account`: Manage and view Spinnaker configuration for the gcs artifact provider's account
- * `disable`: Set the gcs artifact provider as disabled
- * `enable`: Set the gcs artifact provider as enabled
+
+- `account`: Manage and view Spinnaker configuration for the gcs artifact provider's account
+- `disable`: Set the gcs artifact provider as disabled
+- `enable`: Set the gcs artifact provider as enabled
---
+
## hal config artifact gcs account
Manage and view Spinnaker configuration for the gcs artifact provider's account
#### Usage
+
```
hal config artifact gcs account ACCOUNT [parameters] [subcommands]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `add`: Add an artifact account to the gcs artifact provider.
- * `delete`: Delete a specific gcs artifact account by name.
- * `edit`: Edit an artifact account in the gcs artifact provider.
- * `get`: Get the specified account details for the gcs provider.
- * `list`: List the artifact account names for the gcs artifact provider.
+
+- `add`: Add an artifact account to the gcs artifact provider.
+- `delete`: Delete a specific gcs artifact account by name.
+- `edit`: Edit an artifact account in the gcs artifact provider.
+- `get`: Get the specified account details for the gcs provider.
+- `list`: List the artifact account names for the gcs artifact provider.
---
+
## hal config artifact gcs account add
Add an artifact account to the gcs artifact provider.
#### Usage
+
```
hal config artifact gcs account add ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--json-path`: The path to a JSON service account that Spinnaker will use as credentials. This is only needed if Spinnaker is not deployed on a Google Compute Engine VM, or needs permissions not afforded to the VM it is running on. See [https://cloud.google.com/compute/docs/access/service-accounts](https://cloud.google.com/compute/docs/access/service-accounts) for more information.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--json-path`: The path to a JSON service account that Spinnaker will use as credentials. This is only needed if Spinnaker is not deployed on a Google Compute Engine VM, or needs permissions not afforded to the VM it is running on. See [https://cloud.google.com/compute/docs/access/service-accounts](https://cloud.google.com/compute/docs/access/service-accounts) for more information.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config artifact gcs account delete
Delete a specific gcs artifact account by name.
#### Usage
+
```
hal config artifact gcs account delete ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config artifact gcs account edit
Edit an artifact account in the gcs artifact provider.
#### Usage
+
```
hal config artifact gcs account edit ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--json-path`: The path to a JSON service account that Spinnaker will use as credentials. This is only needed if Spinnaker is not deployed on a Google Compute Engine VM, or needs permissions not afforded to the VM it is running on. See [https://cloud.google.com/compute/docs/access/service-accounts](https://cloud.google.com/compute/docs/access/service-accounts) for more information.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--json-path`: The path to a JSON service account that Spinnaker will use as credentials. This is only needed if Spinnaker is not deployed on a Google Compute Engine VM, or needs permissions not afforded to the VM it is running on. See [https://cloud.google.com/compute/docs/access/service-accounts](https://cloud.google.com/compute/docs/access/service-accounts) for more information.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config artifact gcs account get
Get the specified account details for the gcs provider.
#### Usage
+
```
hal config artifact gcs account get ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config artifact gcs account list
List the artifact account names for the gcs artifact provider.
#### Usage
+
```
hal config artifact gcs account list [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config artifact gcs disable
Set the gcs artifact provider as disabled
#### Usage
+
```
hal config artifact gcs disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config artifact gcs enable
Set the gcs artifact provider as enabled
#### Usage
+
```
hal config artifact gcs enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config artifact github
Manage and view Spinnaker configuration for the github provider
#### Usage
+
```
hal config artifact github [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `account`: Manage and view Spinnaker configuration for the github artifact provider's account
- * `disable`: Set the github artifact provider as disabled
- * `enable`: Set the github artifact provider as enabled
+
+- `account`: Manage and view Spinnaker configuration for the github artifact provider's account
+- `disable`: Set the github artifact provider as disabled
+- `enable`: Set the github artifact provider as enabled
---
+
## hal config artifact github account
Manage and view Spinnaker configuration for the github artifact provider's account
#### Usage
+
```
hal config artifact github account ACCOUNT [parameters] [subcommands]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `add`: Add an artifact account to the github artifact provider.
- * `delete`: Delete a specific github artifact account by name.
- * `edit`: Edit an artifact account in the github artifact provider.
- * `get`: Get the specified account details for the github provider.
- * `list`: List the artifact account names for the github artifact provider.
+
+- `add`: Add an artifact account to the github artifact provider.
+- `delete`: Delete a specific github artifact account by name.
+- `edit`: Edit an artifact account in the github artifact provider.
+- `get`: Get the specified account details for the github provider.
+- `list`: List the artifact account names for the github artifact provider.
---
+
## hal config artifact github account add
Add an artifact account to the github artifact provider.
#### Usage
+
```
hal config artifact github account add ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--password`: (*Sensitive data* - user will be prompted on standard input) GitHub password
- * `--token`: (*Sensitive data* - user will be prompted on standard input) GitHub token
- * `--token-file`: File containing a GitHub authentication token
- * `--username`: GitHub username
- * `--username-password-file`: File containing "username:password" to use for GitHub authentication
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--password`: (_Sensitive data_ - user will be prompted on standard input) GitHub password
+- `--token`: (_Sensitive data_ - user will be prompted on standard input) GitHub token
+- `--token-file`: File containing a GitHub authentication token
+- `--username`: GitHub username
+- `--username-password-file`: File containing "username:password" to use for GitHub authentication
---
+
## hal config artifact github account delete
Delete a specific github artifact account by name.
#### Usage
+
```
hal config artifact github account delete ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config artifact github account edit
Edit an artifact account in the github artifact provider.
#### Usage
+
```
hal config artifact github account edit ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--password`: (*Sensitive data* - user will be prompted on standard input) GitHub password
- * `--token`: (*Sensitive data* - user will be prompted on standard input) GitHub token
- * `--token-file`: File containing a GitHub authentication token
- * `--username`: GitHub username
- * `--username-password-file`: File containing "username:password" to use for GitHub authentication
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--password`: (_Sensitive data_ - user will be prompted on standard input) GitHub password
+- `--token`: (_Sensitive data_ - user will be prompted on standard input) GitHub token
+- `--token-file`: File containing a GitHub authentication token
+- `--username`: GitHub username
+- `--username-password-file`: File containing "username:password" to use for GitHub authentication
---
+
## hal config artifact github account get
Get the specified account details for the github provider.
#### Usage
+
```
hal config artifact github account get ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config artifact github account list
List the artifact account names for the github artifact provider.
#### Usage
+
```
hal config artifact github account list [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config artifact github disable
Set the github artifact provider as disabled
#### Usage
+
```
hal config artifact github disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config artifact github enable
Set the github artifact provider as enabled
#### Usage
+
```
hal config artifact github enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config artifact gitlab
Manage and view Spinnaker configuration for the gitlab provider
#### Usage
+
```
hal config artifact gitlab [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `account`: Manage and view Spinnaker configuration for the gitlab artifact provider's account
- * `disable`: Set the gitlab artifact provider as disabled
- * `enable`: Set the gitlab artifact provider as enabled
+
+- `account`: Manage and view Spinnaker configuration for the gitlab artifact provider's account
+- `disable`: Set the gitlab artifact provider as disabled
+- `enable`: Set the gitlab artifact provider as enabled
---
+
## hal config artifact gitlab account
Manage and view Spinnaker configuration for the gitlab artifact provider's account
#### Usage
+
```
hal config artifact gitlab account ACCOUNT [parameters] [subcommands]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `add`: Add an artifact account to the gitlab artifact provider.
- * `delete`: Delete a specific gitlab artifact account by name.
- * `edit`: Edit an artifact account in the gitlab artifact provider.
- * `get`: Get the specified account details for the gitlab provider.
- * `list`: List the artifact account names for the gitlab artifact provider.
+
+- `add`: Add an artifact account to the gitlab artifact provider.
+- `delete`: Delete a specific gitlab artifact account by name.
+- `edit`: Edit an artifact account in the gitlab artifact provider.
+- `get`: Get the specified account details for the gitlab provider.
+- `list`: List the artifact account names for the gitlab artifact provider.
---
+
## hal config artifact gitlab account add
Add an artifact account to the gitlab artifact provider.
#### Usage
+
```
hal config artifact gitlab account add ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--token`: (*Sensitive data* - user will be prompted on standard input) Gitlab token
- * `--token-file`: File containing a Gitlab authentication token
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--token`: (_Sensitive data_ - user will be prompted on standard input) Gitlab token
+- `--token-file`: File containing a Gitlab authentication token
---
+
## hal config artifact gitlab account delete
Delete a specific gitlab artifact account by name.
#### Usage
+
```
hal config artifact gitlab account delete ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config artifact gitlab account edit
Edit an artifact account in the gitlab artifact provider.
#### Usage
+
```
hal config artifact gitlab account edit ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--token`: (*Sensitive data* - user will be prompted on standard input) Gitlab token
- * `--token-file`: File containing a Gitlab authentication token
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--token`: (_Sensitive data_ - user will be prompted on standard input) Gitlab token
+- `--token-file`: File containing a Gitlab authentication token
---
+
## hal config artifact gitlab account get
Get the specified account details for the gitlab provider.
#### Usage
+
```
hal config artifact gitlab account get ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config artifact gitlab account list
List the artifact account names for the gitlab artifact provider.
#### Usage
+
```
hal config artifact gitlab account list [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config artifact gitlab disable
Set the gitlab artifact provider as disabled
#### Usage
+
```
hal config artifact gitlab disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config artifact gitlab enable
Set the gitlab artifact provider as enabled
#### Usage
+
```
hal config artifact gitlab enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config artifact gitrepo
Manage and view Spinnaker configuration for the gitrepo provider
#### Usage
+
```
hal config artifact gitrepo [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `account`: Manage and view Spinnaker configuration for the gitrepo artifact provider's account
- * `disable`: Set the gitrepo artifact provider as disabled
- * `enable`: Set the gitrepo artifact provider as enabled
+
+- `account`: Manage and view Spinnaker configuration for the gitrepo artifact provider's account
+- `disable`: Set the gitrepo artifact provider as disabled
+- `enable`: Set the gitrepo artifact provider as enabled
---
+
## hal config artifact gitrepo account
Manage and view Spinnaker configuration for the gitrepo artifact provider's account
#### Usage
+
```
hal config artifact gitrepo account ACCOUNT [parameters] [subcommands]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `add`: Add an artifact account to the gitrepo artifact provider.
- * `delete`: Delete a specific gitrepo artifact account by name.
- * `edit`: Edit an artifact account in the gitrepo artifact provider.
- * `get`: Get the specified account details for the gitrepo provider.
- * `list`: List the artifact account names for the gitrepo artifact provider.
+
+- `add`: Add an artifact account to the gitrepo artifact provider.
+- `delete`: Delete a specific gitrepo artifact account by name.
+- `edit`: Edit an artifact account in the gitrepo artifact provider.
+- `get`: Get the specified account details for the gitrepo provider.
+- `list`: List the artifact account names for the gitrepo artifact provider.
---
+
## hal config artifact gitrepo account add
Add an artifact account to the gitrepo artifact provider.
#### Usage
+
```
hal config artifact gitrepo account add ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--password`: (*Sensitive data* - user will be prompted on standard input) Git password
- * `--ssh-known-hosts-file-path`: File containing the known and trusted SSH hosts.
- * `--ssh-private-key-file-path`: Path to the ssh private key in PEM format
- * `--ssh-private-key-passphrase`: (*Sensitive data* - user will be prompted on standard input) Passphrase for encrypted private key
- * `--ssh-trust-unknown-hosts`: Setting this to true allows Spinnaker to authenticate with unknown hosts
- * `--token`: (*Sensitive data* - user will be prompted on standard input) Git token
- * `--token-file`: File containing a Git authentication token
- * `--username`: Git username
- * `--username-password-file`: File containing "username:password" to use for Git authentication
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--password`: (_Sensitive data_ - user will be prompted on standard input) Git password
+- `--ssh-known-hosts-file-path`: File containing the known and trusted SSH hosts.
+- `--ssh-private-key-file-path`: Path to the ssh private key in PEM format
+- `--ssh-private-key-passphrase`: (_Sensitive data_ - user will be prompted on standard input) Passphrase for encrypted private key
+- `--ssh-trust-unknown-hosts`: Setting this to true allows Spinnaker to authenticate with unknown hosts
+- `--token`: (_Sensitive data_ - user will be prompted on standard input) Git token
+- `--token-file`: File containing a Git authentication token
+- `--username`: Git username
+- `--username-password-file`: File containing "username:password" to use for Git authentication
---
+
## hal config artifact gitrepo account delete
Delete a specific gitrepo artifact account by name.
#### Usage
+
```
hal config artifact gitrepo account delete ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config artifact gitrepo account edit
Edit an artifact account in the gitrepo artifact provider.
#### Usage
+
```
hal config artifact gitrepo account edit ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--password`: (*Sensitive data* - user will be prompted on standard input) Git password
- * `--ssh-known-hosts-file-path`: File containing the known and trusted SSH hosts
- * `--ssh-private-key-file-path`: Path to the ssh private key in PEM format
- * `--ssh-private-key-passphrase`: (*Sensitive data* - user will be prompted on standard input) Passphrase for encrypted private key
- * `--ssh-trust-unknown-hosts`: Setting this to true allows Spinnaker to authenticate with unknown hosts
- * `--token`: (*Sensitive data* - user will be prompted on standard input) Git token
- * `--token-file`: File containing a Git authentication token
- * `--username`: Git username
- * `--username-password-file`: File containing "username:password" to use for Git authentication
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--password`: (_Sensitive data_ - user will be prompted on standard input) Git password
+- `--ssh-known-hosts-file-path`: File containing the known and trusted SSH hosts
+- `--ssh-private-key-file-path`: Path to the ssh private key in PEM format
+- `--ssh-private-key-passphrase`: (_Sensitive data_ - user will be prompted on standard input) Passphrase for encrypted private key
+- `--ssh-trust-unknown-hosts`: Setting this to true allows Spinnaker to authenticate with unknown hosts
+- `--token`: (_Sensitive data_ - user will be prompted on standard input) Git token
+- `--token-file`: File containing a Git authentication token
+- `--username`: Git username
+- `--username-password-file`: File containing "username:password" to use for Git authentication
---
+
## hal config artifact gitrepo account get
Get the specified account details for the gitrepo provider.
#### Usage
+
```
hal config artifact gitrepo account get ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config artifact gitrepo account list
List the artifact account names for the gitrepo artifact provider.
#### Usage
+
```
hal config artifact gitrepo account list [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config artifact gitrepo disable
Set the gitrepo artifact provider as disabled
#### Usage
+
```
hal config artifact gitrepo disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config artifact gitrepo enable
Set the gitrepo artifact provider as enabled
#### Usage
+
```
hal config artifact gitrepo enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config artifact helm
Manage and view Spinnaker configuration for the helm provider
#### Usage
+
```
hal config artifact helm [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `account`: Manage and view Spinnaker configuration for the helm artifact provider's account
- * `disable`: Set the helm artifact provider as disabled
- * `enable`: Set the helm artifact provider as enabled
+
+- `account`: Manage and view Spinnaker configuration for the helm artifact provider's account
+- `disable`: Set the helm artifact provider as disabled
+- `enable`: Set the helm artifact provider as enabled
---
+
## hal config artifact helm account
Manage and view Spinnaker configuration for the helm artifact provider's account
#### Usage
+
```
hal config artifact helm account ACCOUNT [parameters] [subcommands]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `add`: Add an artifact account to the helm artifact provider.
- * `delete`: Delete a specific helm artifact account by name.
- * `edit`: Edit an artifact account in the helm artifact provider.
- * `get`: Get the specified account details for the helm provider.
- * `list`: List the artifact account names for the helm artifact provider.
+
+- `add`: Add an artifact account to the helm artifact provider.
+- `delete`: Delete a specific helm artifact account by name.
+- `edit`: Edit an artifact account in the helm artifact provider.
+- `get`: Get the specified account details for the helm provider.
+- `list`: List the artifact account names for the helm artifact provider.
---
+
## hal config artifact helm account add
Add an artifact account to the helm artifact provider.
#### Usage
+
```
hal config artifact helm account add ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--password`: (*Sensitive data* - user will be prompted on standard input) Helm chart repository basic auth password
- * `--repository`: Helm chart repository
- * `--username`: Helm chart repository basic auth username
- * `--username-password-file`: File containing "username:password" to use for helm chart repository basic auth
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--password`: (_Sensitive data_ - user will be prompted on standard input) Helm chart repository basic auth password
+- `--repository`: Helm chart repository
+- `--username`: Helm chart repository basic auth username
+- `--username-password-file`: File containing "username:password" to use for helm chart repository basic auth
---
+
## hal config artifact helm account delete
Delete a specific helm artifact account by name.
#### Usage
+
```
hal config artifact helm account delete ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config artifact helm account edit
Edit an artifact account in the helm artifact provider.
#### Usage
+
```
hal config artifact helm account edit ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--password`: (*Sensitive data* - user will be prompted on standard input) Helm chart repository basic auth password
- * `--repository`: Helm chart repository
- * `--username`: Helm chart repository basic auth username
- * `--username-password-file`: File containing "username:password" to use for helm chart repository basic auth
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--password`: (_Sensitive data_ - user will be prompted on standard input) Helm chart repository basic auth password
+- `--repository`: Helm chart repository
+- `--username`: Helm chart repository basic auth username
+- `--username-password-file`: File containing "username:password" to use for helm chart repository basic auth
---
+
## hal config artifact helm account get
Get the specified account details for the helm provider.
#### Usage
+
```
hal config artifact helm account get ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config artifact helm account list
List the artifact account names for the helm artifact provider.
#### Usage
+
```
hal config artifact helm account list [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config artifact helm disable
Set the helm artifact provider as disabled
#### Usage
+
```
hal config artifact helm disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config artifact helm enable
Set the helm artifact provider as enabled
#### Usage
+
```
hal config artifact helm enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config artifact http
Manage and view Spinnaker configuration for the http provider
#### Usage
+
```
hal config artifact http [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `account`: Manage and view Spinnaker configuration for the http artifact provider's account
- * `disable`: Set the http artifact provider as disabled
- * `enable`: Set the http artifact provider as enabled
+
+- `account`: Manage and view Spinnaker configuration for the http artifact provider's account
+- `disable`: Set the http artifact provider as disabled
+- `enable`: Set the http artifact provider as enabled
---
+
## hal config artifact http account
Manage and view Spinnaker configuration for the http artifact provider's account
#### Usage
+
```
hal config artifact http account ACCOUNT [parameters] [subcommands]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `add`: Add an artifact account to the http artifact provider.
- * `delete`: Delete a specific http artifact account by name.
- * `edit`: Edit an artifact account in the http artifact provider.
- * `get`: Get the specified account details for the http provider.
- * `list`: List the artifact account names for the http artifact provider.
+
+- `add`: Add an artifact account to the http artifact provider.
+- `delete`: Delete a specific http artifact account by name.
+- `edit`: Edit an artifact account in the http artifact provider.
+- `get`: Get the specified account details for the http provider.
+- `list`: List the artifact account names for the http artifact provider.
---
+
## hal config artifact http account add
Add an artifact account to the http artifact provider.
#### Usage
+
```
hal config artifact http account add ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--password`: (*Sensitive data* - user will be prompted on standard input) HTTP basic auth password
- * `--username`: HTTP basic auth username
- * `--username-password-file`: File containing "username:password" to use for HTTP basic auth
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--password`: (_Sensitive data_ - user will be prompted on standard input) HTTP basic auth password
+- `--username`: HTTP basic auth username
+- `--username-password-file`: File containing "username:password" to use for HTTP basic auth
---
+
## hal config artifact http account delete
Delete a specific http artifact account by name.
#### Usage
+
```
hal config artifact http account delete ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config artifact http account edit
Edit an artifact account in the http artifact provider.
#### Usage
+
```
hal config artifact http account edit ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--password`: (*Sensitive data* - user will be prompted on standard input) Http password
- * `--username`: Http username
- * `--username-password-file`: File containing "username:password" to use for Http authentication
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--password`: (_Sensitive data_ - user will be prompted on standard input) Http password
+- `--username`: Http username
+- `--username-password-file`: File containing "username:password" to use for Http authentication
---
+
## hal config artifact http account get
Get the specified account details for the http provider.
#### Usage
+
```
hal config artifact http account get ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config artifact http account list
List the artifact account names for the http artifact provider.
#### Usage
+
```
hal config artifact http account list [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config artifact http disable
Set the http artifact provider as disabled
#### Usage
+
```
hal config artifact http disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config artifact http enable
Set the http artifact provider as enabled
#### Usage
+
```
hal config artifact http enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config artifact maven
Manage and view Spinnaker configuration for the maven provider
#### Usage
+
```
hal config artifact maven [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `account`: Manage and view Spinnaker configuration for the maven artifact provider's account
- * `disable`: Set the maven artifact provider as disabled
- * `enable`: Set the maven artifact provider as enabled
+
+- `account`: Manage and view Spinnaker configuration for the maven artifact provider's account
+- `disable`: Set the maven artifact provider as disabled
+- `enable`: Set the maven artifact provider as enabled
---
+
## hal config artifact maven account
Manage and view Spinnaker configuration for the maven artifact provider's account
#### Usage
+
```
hal config artifact maven account ACCOUNT [parameters] [subcommands]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `add`: Add an artifact account to the maven artifact provider.
- * `delete`: Delete a specific maven artifact account by name.
- * `edit`: Edit an artifact account in the maven artifact provider.
- * `get`: Get the specified account details for the maven provider.
- * `list`: List the artifact account names for the maven artifact provider.
+
+- `add`: Add an artifact account to the maven artifact provider.
+- `delete`: Delete a specific maven artifact account by name.
+- `edit`: Edit an artifact account in the maven artifact provider.
+- `get`: Get the specified account details for the maven provider.
+- `list`: List the artifact account names for the maven artifact provider.
---
+
## hal config artifact maven account add
Add an artifact account to the maven artifact provider.
#### Usage
+
```
hal config artifact maven account add ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--repository-url`: (*Required*) Full URI for the Maven repository ie. `[http://some.host.com/repository/path](http://some.host.com/repository/path)`
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--repository-url`: (_Required_) Full URI for the Maven repository ie. `[http://some.host.com/repository/path](http://some.host.com/repository/path)`
---
+
## hal config artifact maven account delete
Delete a specific maven artifact account by name.
#### Usage
+
```
hal config artifact maven account delete ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config artifact maven account edit
Edit an artifact account in the maven artifact provider.
#### Usage
+
```
hal config artifact maven account edit ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--repository-url`: Full URI for the Maven repository ie. `[http://some.host.com/repository/path](http://some.host.com/repository/path)`
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--repository-url`: Full URI for the Maven repository ie. `[http://some.host.com/repository/path](http://some.host.com/repository/path)`
---
+
## hal config artifact maven account get
Get the specified account details for the maven provider.
#### Usage
+
```
hal config artifact maven account get ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config artifact maven account list
List the artifact account names for the maven artifact provider.
#### Usage
+
```
hal config artifact maven account list [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config artifact maven disable
Set the maven artifact provider as disabled
#### Usage
+
```
hal config artifact maven disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config artifact maven enable
Set the maven artifact provider as enabled
#### Usage
+
```
hal config artifact maven enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config artifact oracle
Manage and view Spinnaker configuration for the oracle provider
#### Usage
+
```
hal config artifact oracle [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `account`: Manage and view Spinnaker configuration for the oracle artifact provider's account
- * `disable`: Set the oracle artifact provider as disabled
- * `enable`: Set the oracle artifact provider as enabled
+
+- `account`: Manage and view Spinnaker configuration for the oracle artifact provider's account
+- `disable`: Set the oracle artifact provider as disabled
+- `enable`: Set the oracle artifact provider as enabled
---
+
## hal config artifact oracle account
Manage and view Spinnaker configuration for the oracle artifact provider's account
#### Usage
+
```
hal config artifact oracle account ACCOUNT [parameters] [subcommands]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `add`: Add an artifact account to the oracle artifact provider.
- * `delete`: Delete a specific oracle artifact account by name.
- * `edit`: Edit an artifact account in the oracle artifact provider.
- * `get`: Get the specified account details for the oracle provider.
- * `list`: List the artifact account names for the oracle artifact provider.
+
+- `add`: Add an artifact account to the oracle artifact provider.
+- `delete`: Delete a specific oracle artifact account by name.
+- `edit`: Edit an artifact account in the oracle artifact provider.
+- `get`: Get the specified account details for the oracle provider.
+- `list`: List the artifact account names for the oracle artifact provider.
---
+
## hal config artifact oracle account add
Add an artifact account to the oracle artifact provider.
#### Usage
+
```
hal config artifact oracle account add ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--fingerprint`: Fingerprint of the public key
- * `--namespace`: The namespace the bucket and objects should be created in
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--private-key-passphrase`: (*Sensitive data* - user will be prompted on standard input) Passphrase used for the private key, if it is encrypted
- * `--region`: An Oracle region (e.g., us-phoenix-1)
- * `--ssh-private-key-file-path`: Path to the private key in PEM format
- * `--tenancy-id`: Provide the OCID of the Oracle Tenancy to use.
- * `--user-id`: Provide the OCID of the Oracle User you're authenticating as
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--fingerprint`: Fingerprint of the public key
+- `--namespace`: The namespace the bucket and objects should be created in
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--private-key-passphrase`: (_Sensitive data_ - user will be prompted on standard input) Passphrase used for the private key, if it is encrypted
+- `--region`: An Oracle region (e.g., us-phoenix-1)
+- `--ssh-private-key-file-path`: Path to the private key in PEM format
+- `--tenancy-id`: Provide the OCID of the Oracle Tenancy to use.
+- `--user-id`: Provide the OCID of the Oracle User you're authenticating as
---
+
## hal config artifact oracle account delete
Delete a specific oracle artifact account by name.
#### Usage
+
```
hal config artifact oracle account delete ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config artifact oracle account edit
Edit an artifact account in the oracle artifact provider.
#### Usage
+
```
hal config artifact oracle account edit ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--fingerprint`: Fingerprint of the public key
- * `--namespace`: The namespace the bucket and objects should be created in
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--private-key-passphrase`: (*Sensitive data* - user will be prompted on standard input) Passphrase used for the private key, if it is encrypted
- * `--region`: An Oracle region (e.g., us-phoenix-1)
- * `--ssh-private-key-file-path`: Path to the private key in PEM format
- * `--tenancy-id`: Provide the OCID of the Oracle Tenancy to use.
- * `--user-id`: Provide the OCID of the Oracle User you're authenticating as
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--fingerprint`: Fingerprint of the public key
+- `--namespace`: The namespace the bucket and objects should be created in
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--private-key-passphrase`: (_Sensitive data_ - user will be prompted on standard input) Passphrase used for the private key, if it is encrypted
+- `--region`: An Oracle region (e.g., us-phoenix-1)
+- `--ssh-private-key-file-path`: Path to the private key in PEM format
+- `--tenancy-id`: Provide the OCID of the Oracle Tenancy to use.
+- `--user-id`: Provide the OCID of the Oracle User you're authenticating as
---
+
## hal config artifact oracle account get
Get the specified account details for the oracle provider.
#### Usage
+
```
hal config artifact oracle account get ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config artifact oracle account list
List the artifact account names for the oracle artifact provider.
#### Usage
+
```
hal config artifact oracle account list [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config artifact oracle disable
Set the oracle artifact provider as disabled
#### Usage
+
```
hal config artifact oracle disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config artifact oracle enable
Set the oracle artifact provider as enabled
#### Usage
+
```
hal config artifact oracle enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config artifact s3
Manage and view Spinnaker configuration for the s3 provider
#### Usage
+
```
hal config artifact s3 [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `account`: Manage and view Spinnaker configuration for the s3 artifact provider's account
- * `disable`: Set the s3 artifact provider as disabled
- * `enable`: Set the s3 artifact provider as enabled
+
+- `account`: Manage and view Spinnaker configuration for the s3 artifact provider's account
+- `disable`: Set the s3 artifact provider as disabled
+- `enable`: Set the s3 artifact provider as enabled
---
+
## hal config artifact s3 account
Manage and view Spinnaker configuration for the s3 artifact provider's account
#### Usage
+
```
hal config artifact s3 account ACCOUNT [parameters] [subcommands]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `add`: Add an artifact account to the s3 artifact provider.
- * `delete`: Delete a specific s3 artifact account by name.
- * `edit`: Edit an artifact account in the s3 artifact provider.
- * `get`: Get the specified account details for the s3 provider.
- * `list`: List the artifact account names for the s3 artifact provider.
+
+- `add`: Add an artifact account to the s3 artifact provider.
+- `delete`: Delete a specific s3 artifact account by name.
+- `edit`: Edit an artifact account in the s3 artifact provider.
+- `get`: Get the specified account details for the s3 provider.
+- `list`: List the artifact account names for the s3 artifact provider.
---
+
## hal config artifact s3 account add
Add an artifact account to the s3 artifact provider.
#### Usage
+
```
hal config artifact s3 account add ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--api-endpoint`: S3 api endpoint; only required when using an S3 clone such as Minio
- * `--api-region`: S3 api region; only required when using an S3 clone such as Minio
- * `--aws-access-key-id`: Your AWS Access Key ID. If not provided, Halyard/Spinnaker will try to find AWS credentials as described at [http://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/credentials.html#credentials-default](http://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/credentials.html#credentials-default)
- * `--aws-secret-access-key`: (*Sensitive data* - user will be prompted on standard input) Your AWS Secret Key.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--region`: S3 region
+- `--api-endpoint`: S3 api endpoint; only required when using an S3 clone such as Minio
+- `--api-region`: S3 api region; only required when using an S3 clone such as Minio
+- `--aws-access-key-id`: Your AWS Access Key ID. If not provided, Halyard/Spinnaker will try to find AWS credentials as described at [http://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/credentials.html#credentials-default](http://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/credentials.html#credentials-default)
+- `--aws-secret-access-key`: (_Sensitive data_ - user will be prompted on standard input) Your AWS Secret Key.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--region`: S3 region
---
+
## hal config artifact s3 account delete
Delete a specific s3 artifact account by name.
#### Usage
+
```
hal config artifact s3 account delete ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config artifact s3 account edit
Edit an artifact account in the s3 artifact provider.
#### Usage
+
```
hal config artifact s3 account edit ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--api-endpoint`: S3 api endpoint; only required when using an S3 clone such as Minio
- * `--api-region`: S3 api region; only required when using an S3 clone such as Minio
- * `--aws-access-key-id`: Your AWS Access Key ID. If not provided, Halyard/Spinnaker will try to find AWS credentials as described at [http://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/credentials.html#credentials-default](http://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/credentials.html#credentials-default)
- * `--aws-secret-access-key`: (*Sensitive data* - user will be prompted on standard input) Your AWS Secret Key.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--region`: S3 region
+- `--api-endpoint`: S3 api endpoint; only required when using an S3 clone such as Minio
+- `--api-region`: S3 api region; only required when using an S3 clone such as Minio
+- `--aws-access-key-id`: Your AWS Access Key ID. If not provided, Halyard/Spinnaker will try to find AWS credentials as described at [http://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/credentials.html#credentials-default](http://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/credentials.html#credentials-default)
+- `--aws-secret-access-key`: (_Sensitive data_ - user will be prompted on standard input) Your AWS Secret Key.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--region`: S3 region
---
+
## hal config artifact s3 account get
Get the specified account details for the s3 provider.
#### Usage
+
```
hal config artifact s3 account get ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config artifact s3 account list
List the artifact account names for the s3 artifact provider.
#### Usage
+
```
hal config artifact s3 account list [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config artifact s3 disable
Set the s3 artifact provider as disabled
#### Usage
+
```
hal config artifact s3 disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config artifact s3 enable
Set the s3 artifact provider as enabled
#### Usage
+
```
hal config artifact s3 enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config artifact templates
Show Spinnaker's configured artifact templates.
#### Usage
+
```
hal config artifact templates [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `add`: Add an artifact template
- * `delete`: Delete an artifact template
- * `edit`: Edit an artifact template
- * `list`: List an artifact templates
+
+- `add`: Add an artifact template
+- `delete`: Delete an artifact template
+- `edit`: Edit an artifact template
+- `list`: List an artifact templates
---
+
## hal config artifact templates add
Add an artifact template
#### Usage
+
```
hal config artifact templates add TEMPLATE [parameters]
```
#### Parameters
+
`TEMPLATE`: The name of the artifact template to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--template-path`: (*Required*) The path to the Jinja template to use for artifact extraction
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--template-path`: (_Required_) The path to the Jinja template to use for artifact extraction
---
+
## hal config artifact templates delete
Delete an artifact template
#### Usage
+
```
hal config artifact templates delete TEMPLATE [parameters]
```
#### Parameters
+
`TEMPLATE`: The name of the artifact template to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config artifact templates edit
Edit an artifact template
#### Usage
+
```
hal config artifact templates edit TEMPLATE [parameters]
```
#### Parameters
+
`TEMPLATE`: The name of the artifact template to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--template-path`: The path to the Jinja template to use for artifact extraction
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--template-path`: The path to the Jinja template to use for artifact extraction
---
+
## hal config artifact templates list
List an artifact templates
#### Usage
+
```
hal config artifact templates list [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config canary
Configure your canary analysis settings for Spinnaker.
#### Usage
+
```
hal config canary [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `aws`: Configure your canary analysis AWS service integration settings for Spinnaker.
- * `datadog`: Configure your canary analysis Datadog service integration settings for Spinnaker.
- * `disable`: Set Spinnaker's canary analysis to disabled.
- * `edit`: Edit Spinnaker's canary analysis settings.
- * `enable`: Set Spinnaker's canary analysis to enabled.
- * `google`: Configure your canary analysis Google service integration settings for Spinnaker.
- * `newrelic`: Configure your canary analysis New Relic service integration settings for Spinnaker.
- * `prometheus`: Configure your canary analysis Prometheus service integration settings for Spinnaker.
- * `signalfx`: Configure your canary analysis SignalFx service integration settings for Spinnaker.
+
+- `aws`: Configure your canary analysis AWS service integration settings for Spinnaker.
+- `datadog`: Configure your canary analysis Datadog service integration settings for Spinnaker.
+- `disable`: Set Spinnaker's canary analysis to disabled.
+- `edit`: Edit Spinnaker's canary analysis settings.
+- `enable`: Set Spinnaker's canary analysis to enabled.
+- `google`: Configure your canary analysis Google service integration settings for Spinnaker.
+- `newrelic`: Configure your canary analysis New Relic service integration settings for Spinnaker.
+- `prometheus`: Configure your canary analysis Prometheus service integration settings for Spinnaker.
+- `signalfx`: Configure your canary analysis SignalFx service integration settings for Spinnaker.
---
+
## hal config canary aws
Configure your canary analysis AWS service integration settings for Spinnaker.
#### Usage
+
```
hal config canary aws [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `account`: Manage and view Spinnaker configuration for the AWS service integration's canary accounts.
- * `disable`: Set Spinnaker's canary analysis AWS service integration to disabled.
- * `edit`: Edit Spinnaker's canary analysis AWS service integration settings.
- * `enable`: Set Spinnaker's canary analysis AWS service integration to enabled.
+
+- `account`: Manage and view Spinnaker configuration for the AWS service integration's canary accounts.
+- `disable`: Set Spinnaker's canary analysis AWS service integration to disabled.
+- `edit`: Edit Spinnaker's canary analysis AWS service integration settings.
+- `enable`: Set Spinnaker's canary analysis AWS service integration to enabled.
---
+
## hal config canary aws account
Manage and view Spinnaker configuration for the AWS service integration's canary accounts.
#### Usage
+
```
hal config canary aws account ACCOUNT [parameters] [subcommands]
```
#### Parameters
+
`ACCOUNT`: The name of the canary account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `add`: Add a canary account to the AWS service integration.
- * `delete`: Delete a specific AWS canary account by name.
- * `edit`: Edit a canary account in the AWS service integration.
- * `get`: Get the specified canary account details for the AWS service integration.
- * `list`: List the canary account names for the AWS service integration.
+
+- `add`: Add a canary account to the AWS service integration.
+- `delete`: Delete a specific AWS canary account by name.
+- `edit`: Edit a canary account in the AWS service integration.
+- `get`: Get the specified canary account details for the AWS service integration.
+- `list`: List the canary account names for the AWS service integration.
---
+
## hal config canary aws account add
Add a canary account to the AWS service integration.
#### Usage
+
```
hal config canary aws account add ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the canary account to operate on.
- * `--access-key-id`: The default access key used to communicate with AWS.
- * `--bucket`: The name of a storage bucket that your specified account has access to. If you specify a globally unique bucket name that doesn't exist yet, Kayenta will create that bucket for you.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--endpoint`: The endpoint used to reach the service implementing the AWS api. Typical use is with Minio.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--profile-name`: The profile name to use when resolving AWS credentials. Typically found in ~/.aws/credentials (*Default*: `default`).
- * `--region`: The region to use.
- * `--root-folder`: The root folder in the chosen bucket to place all of the canary service's persistent data in (*Default*: `kayenta`).
- * `--secret-access-key`: (*Sensitive data* - user will be prompted on standard input) The secret key used to communicate with AWS.
+- `--access-key-id`: The default access key used to communicate with AWS.
+- `--bucket`: The name of a storage bucket that your specified account has access to. If you specify a globally unique bucket name that doesn't exist yet, Kayenta will create that bucket for you.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--endpoint`: The endpoint used to reach the service implementing the AWS api. Typical use is with Minio.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--profile-name`: The profile name to use when resolving AWS credentials. Typically found in ~/.aws/credentials (_Default_: `default`).
+- `--region`: The region to use.
+- `--root-folder`: The root folder in the chosen bucket to place all of the canary service's persistent data in (_Default_: `kayenta`).
+- `--secret-access-key`: (_Sensitive data_ - user will be prompted on standard input) The secret key used to communicate with AWS.
---
+
## hal config canary aws account delete
Delete a specific AWS canary account by name.
#### Usage
+
```
hal config canary aws account delete ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the canary account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config canary aws account edit
Edit a canary account in the AWS service integration.
#### Usage
+
```
hal config canary aws account edit ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the canary account to operate on.
- * `--access-key-id`: The default access key used to communicate with AWS.
- * `--bucket`: The name of a storage bucket that your specified account has access to. If you specify a globally unique bucket name that doesn't exist yet, Kayenta will create that bucket for you.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--endpoint`: The endpoint used to reach the service implementing the AWS api. Typical use is with Minio.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--profile-name`: The profile name to use when resolving AWS credentials. Typically found in ~/.aws/credentials (*Default*: `default`).
- * `--region`: The region to use.
- * `--root-folder`: The root folder in the chosen bucket to place all of the canary service's persistent data in (*Default*: `kayenta`).
- * `--secret-access-key`: (*Sensitive data* - user will be prompted on standard input) The secret key used to communicate with AWS.
+- `--access-key-id`: The default access key used to communicate with AWS.
+- `--bucket`: The name of a storage bucket that your specified account has access to. If you specify a globally unique bucket name that doesn't exist yet, Kayenta will create that bucket for you.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--endpoint`: The endpoint used to reach the service implementing the AWS api. Typical use is with Minio.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--profile-name`: The profile name to use when resolving AWS credentials. Typically found in ~/.aws/credentials (_Default_: `default`).
+- `--region`: The region to use.
+- `--root-folder`: The root folder in the chosen bucket to place all of the canary service's persistent data in (_Default_: `kayenta`).
+- `--secret-access-key`: (_Sensitive data_ - user will be prompted on standard input) The secret key used to communicate with AWS.
---
+
## hal config canary aws account get
Get the specified canary account details for the AWS service integration.
#### Usage
+
```
hal config canary aws account get ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the canary account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config canary aws account list
List the canary account names for the AWS service integration.
#### Usage
+
```
hal config canary aws account list [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config canary aws disable
Set Spinnaker's canary analysis AWS service integration to disabled.
#### Usage
+
```
hal config canary aws disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config canary aws edit
Edit Spinnaker's canary analysis AWS service integration settings.
#### Usage
+
```
hal config canary aws edit [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--s3-enabled`: Whether or not to enable S3 as a persistent store (*Default*: `false`).
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--s3-enabled`: Whether or not to enable S3 as a persistent store (_Default_: `false`).
---
+
## hal config canary aws enable
Set Spinnaker's canary analysis AWS service integration to enabled.
#### Usage
+
```
hal config canary aws enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config canary datadog
Configure your canary analysis Datadog service integration settings for Spinnaker.
#### Usage
+
```
hal config canary datadog [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `account`: Manage and view Spinnaker configuration for the Datadog service integration's canary accounts.
- * `disable`: Set Spinnaker's canary analysis Datadog service integration to disabled.
- * `enable`: Set Spinnaker's canary analysis Datadog service integration to enabled.
+
+- `account`: Manage and view Spinnaker configuration for the Datadog service integration's canary accounts.
+- `disable`: Set Spinnaker's canary analysis Datadog service integration to disabled.
+- `enable`: Set Spinnaker's canary analysis Datadog service integration to enabled.
---
+
## hal config canary datadog account
Manage and view Spinnaker configuration for the Datadog service integration's canary accounts.
#### Usage
+
```
hal config canary datadog account ACCOUNT [parameters] [subcommands]
```
#### Parameters
+
`ACCOUNT`: The name of the canary account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `add`: Add a canary account to the Datadog service integration.
- * `delete`: Delete a specific Datadog canary account by name.
- * `edit`: Edit a canary account in the Datadog service integration.
- * `get`: Get the specified canary account details for the Datadog service integration.
- * `list`: List the canary account names for the Datadog service integration.
+
+- `add`: Add a canary account to the Datadog service integration.
+- `delete`: Delete a specific Datadog canary account by name.
+- `edit`: Edit a canary account in the Datadog service integration.
+- `get`: Get the specified canary account details for the Datadog service integration.
+- `list`: List the canary account names for the Datadog service integration.
---
+
## hal config canary datadog account add
Add a canary account to the Datadog service integration.
#### Usage
+
```
hal config canary datadog account add ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the canary account to operate on.
- * `--api-key`: (*Required*) (*Sensitive data* - user will be prompted on standard input) Your org's unique Datadog API key. See [https://app.datadoghq.com/account/settings#api](https://app.datadoghq.com/account/settings#api).
- * `--application-key`: (*Required*) (*Sensitive data* - user will be prompted on standard input) Your Datadog application key. See [https://app.datadoghq.com/account/settings#api](https://app.datadoghq.com/account/settings#api).
- * `--base-url`: (*Required*) The base URL to the Datadog server.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--api-key`: (_Required_) (_Sensitive data_ - user will be prompted on standard input) Your org's unique Datadog API key. See [https://app.datadoghq.com/account/settings#api](https://app.datadoghq.com/account/settings#api).
+- `--application-key`: (_Required_) (_Sensitive data_ - user will be prompted on standard input) Your Datadog application key. See [https://app.datadoghq.com/account/settings#api](https://app.datadoghq.com/account/settings#api).
+- `--base-url`: (_Required_) The base URL to the Datadog server.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config canary datadog account delete
Delete a specific Datadog canary account by name.
#### Usage
+
```
hal config canary datadog account delete ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the canary account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config canary datadog account edit
Edit a canary account in the Datadog service integration.
#### Usage
+
```
hal config canary datadog account edit ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the canary account to operate on.
- * `--api-key`: (*Sensitive data* - user will be prompted on standard input) Your org's unique Datadog API key. See [https://app.datadoghq.com/account/settings#api](https://app.datadoghq.com/account/settings#api).
- * `--application-key`: (*Sensitive data* - user will be prompted on standard input) Your Datadog application key. See [https://app.datadoghq.com/account/settings#api](https://app.datadoghq.com/account/settings#api).
- * `--base-url`: The base URL to the Datadog server.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--api-key`: (_Sensitive data_ - user will be prompted on standard input) Your org's unique Datadog API key. See [https://app.datadoghq.com/account/settings#api](https://app.datadoghq.com/account/settings#api).
+- `--application-key`: (_Sensitive data_ - user will be prompted on standard input) Your Datadog application key. See [https://app.datadoghq.com/account/settings#api](https://app.datadoghq.com/account/settings#api).
+- `--base-url`: The base URL to the Datadog server.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config canary datadog account get
Get the specified canary account details for the Datadog service integration.
#### Usage
+
```
hal config canary datadog account get ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the canary account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config canary datadog account list
List the canary account names for the Datadog service integration.
#### Usage
+
```
hal config canary datadog account list [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config canary datadog disable
Set Spinnaker's canary analysis Datadog service integration to disabled.
#### Usage
+
```
hal config canary datadog disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config canary datadog enable
Set Spinnaker's canary analysis Datadog service integration to enabled.
#### Usage
+
```
hal config canary datadog enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config canary disable
Set Spinnaker's canary analysis to disabled.
#### Usage
+
```
hal config canary disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config canary edit
Edit Spinnaker's canary analysis settings.
#### Usage
+
```
hal config canary edit [parameters]
```
#### Parameters
- * `--atlasWebComponentsUrl`: Location of web components to use for Atlas metric configuration.
- * `--default-judge`: Name of canary judge to use by default (*Default*: `NetflixACAJudge-v1.0`).
- * `--default-metrics-account`: Name of metrics account to use by default.
- * `--default-metrics-store`: Name of metrics store to use by default (e.g. atlas, datadog, prometheus, stackdriver).
- * `--default-storage-account`: Name of storage account to use by default.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--redux-logger-enabled`: Whether or not to enable redux logging in the canary module in deck (*Default*: `true`).
- * `--show-all-configs-enabled`: Whether or not to show all canary configs in deck, or just those scoped to the current application (*Default*: `true`).
- * `--stages-enabled`: Whether or not to enable canary stages in deck (*Default*: `true`).
- * `--templates-enabled`: Whether or not to enable custom filter templates for canary configs in deck (*Default*: `true`).
+- `--atlasWebComponentsUrl`: Location of web components to use for Atlas metric configuration.
+- `--default-judge`: Name of canary judge to use by default (_Default_: `NetflixACAJudge-v1.0`).
+- `--default-metrics-account`: Name of metrics account to use by default.
+- `--default-metrics-store`: Name of metrics store to use by default (e.g. atlas, datadog, prometheus, stackdriver).
+- `--default-storage-account`: Name of storage account to use by default.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--redux-logger-enabled`: Whether or not to enable redux logging in the canary module in deck (_Default_: `true`).
+- `--show-all-configs-enabled`: Whether or not to show all canary configs in deck, or just those scoped to the current application (_Default_: `true`).
+- `--stages-enabled`: Whether or not to enable canary stages in deck (_Default_: `true`).
+- `--templates-enabled`: Whether or not to enable custom filter templates for canary configs in deck (_Default_: `true`).
---
+
## hal config canary enable
Set Spinnaker's canary analysis to enabled.
#### Usage
+
```
hal config canary enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config canary google
Configure your canary analysis Google service integration settings for Spinnaker.
#### Usage
+
```
hal config canary google [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `account`: Manage and view Spinnaker configuration for the Google service integration's canary accounts.
- * `disable`: Set Spinnaker's canary analysis Google service integration to disabled.
- * `edit`: Edit Spinnaker's canary analysis Google service integration settings.
- * `enable`: Set Spinnaker's canary analysis Google service integration to enabled.
+
+- `account`: Manage and view Spinnaker configuration for the Google service integration's canary accounts.
+- `disable`: Set Spinnaker's canary analysis Google service integration to disabled.
+- `edit`: Edit Spinnaker's canary analysis Google service integration settings.
+- `enable`: Set Spinnaker's canary analysis Google service integration to enabled.
---
+
## hal config canary google account
Manage and view Spinnaker configuration for the Google service integration's canary accounts.
#### Usage
+
```
hal config canary google account ACCOUNT [parameters] [subcommands]
```
#### Parameters
+
`ACCOUNT`: The name of the canary account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `add`: Add a canary account to the Google service integration.
- * `delete`: Delete a specific Google canary account by name.
- * `edit`: Edit a canary account in the Google service integration.
- * `get`: Get the specified canary account details for the Google service integration.
- * `list`: List the canary account names for the Google service integration.
+
+- `add`: Add a canary account to the Google service integration.
+- `delete`: Delete a specific Google canary account by name.
+- `edit`: Edit a canary account in the Google service integration.
+- `get`: Get the specified canary account details for the Google service integration.
+- `list`: List the canary account names for the Google service integration.
---
+
## hal config canary google account add
Add a canary account to the Google service integration.
#### Usage
+
```
hal config canary google account add ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the canary account to operate on.
- * `--bucket`: The name of a storage bucket that your specified account has access to. If you specify a globally unique bucket name that doesn't exist yet, Kayenta will create that bucket for you.
- * `--bucket-location`: This is only required if the bucket you specify doesn't exist yet. In that case, the bucket will be created in that location. See [https://cloud.google.com/storage/docs/managing-buckets#manage-class-location](https://cloud.google.com/storage/docs/managing-buckets#manage-class-location).
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--json-path`: The path to a JSON service account that Spinnaker will use as credentials. This is only needed if Spinnaker is not deployed on a Google Compute Engine VM, or needs permissions not afforded to the VM it is running on. See [https://cloud.google.com/compute/docs/access/service-accounts](https://cloud.google.com/compute/docs/access/service-accounts) for more information.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--project`: (*Required*) The Google Cloud Platform project the canary service will use to consume GCS and Stackdriver.
- * `--root-folder`: The root folder in the chosen bucket to place all of the canary service's persistent data in (*Default*: `kayenta`).
+- `--bucket`: The name of a storage bucket that your specified account has access to. If you specify a globally unique bucket name that doesn't exist yet, Kayenta will create that bucket for you.
+- `--bucket-location`: This is only required if the bucket you specify doesn't exist yet. In that case, the bucket will be created in that location. See [https://cloud.google.com/storage/docs/managing-buckets#manage-class-location](https://cloud.google.com/storage/docs/managing-buckets#manage-class-location).
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--json-path`: The path to a JSON service account that Spinnaker will use as credentials. This is only needed if Spinnaker is not deployed on a Google Compute Engine VM, or needs permissions not afforded to the VM it is running on. See [https://cloud.google.com/compute/docs/access/service-accounts](https://cloud.google.com/compute/docs/access/service-accounts) for more information.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--project`: (_Required_) The Google Cloud Platform project the canary service will use to consume GCS and Stackdriver.
+- `--root-folder`: The root folder in the chosen bucket to place all of the canary service's persistent data in (_Default_: `kayenta`).
---
+
## hal config canary google account delete
Delete a specific Google canary account by name.
#### Usage
+
```
hal config canary google account delete ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the canary account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config canary google account edit
Edit a canary account in the Google service integration.
#### Usage
+
```
hal config canary google account edit ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the canary account to operate on.
- * `--bucket`: The name of a storage bucket that your specified account has access to. If you specify a globally unique bucket name that doesn't exist yet, Kayenta will create that bucket for you.
- * `--bucket-location`: This is only required if the bucket you specify doesn't exist yet. In that case, the bucket will be created in that location. See [https://cloud.google.com/storage/docs/managing-buckets#manage-class-location](https://cloud.google.com/storage/docs/managing-buckets#manage-class-location).
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--json-path`: The path to a JSON service account that Spinnaker will use as credentials. This is only needed if Spinnaker is not deployed on a Google Compute Engine VM, or needs permissions not afforded to the VM it is running on. See [https://cloud.google.com/compute/docs/access/service-accounts](https://cloud.google.com/compute/docs/access/service-accounts) for more information.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--project`: The Google Cloud Platform project the canary service will use to consume GCS and Stackdriver.
- * `--root-folder`: The root folder in the chosen bucket to place all of the canary service's persistent data in (*Default*: `kayenta`).
+- `--bucket`: The name of a storage bucket that your specified account has access to. If you specify a globally unique bucket name that doesn't exist yet, Kayenta will create that bucket for you.
+- `--bucket-location`: This is only required if the bucket you specify doesn't exist yet. In that case, the bucket will be created in that location. See [https://cloud.google.com/storage/docs/managing-buckets#manage-class-location](https://cloud.google.com/storage/docs/managing-buckets#manage-class-location).
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--json-path`: The path to a JSON service account that Spinnaker will use as credentials. This is only needed if Spinnaker is not deployed on a Google Compute Engine VM, or needs permissions not afforded to the VM it is running on. See [https://cloud.google.com/compute/docs/access/service-accounts](https://cloud.google.com/compute/docs/access/service-accounts) for more information.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--project`: The Google Cloud Platform project the canary service will use to consume GCS and Stackdriver.
+- `--root-folder`: The root folder in the chosen bucket to place all of the canary service's persistent data in (_Default_: `kayenta`).
---
+
## hal config canary google account get
Get the specified canary account details for the Google service integration.
#### Usage
+
```
hal config canary google account get ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the canary account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config canary google account list
List the canary account names for the Google service integration.
#### Usage
+
```
hal config canary google account list [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config canary google disable
Set Spinnaker's canary analysis Google service integration to disabled.
#### Usage
+
```
hal config canary google disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config canary google edit
Edit Spinnaker's canary analysis Google service integration settings.
#### Usage
+
```
hal config canary google edit [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--gcs-enabled`: Whether or not to enable GCS as a persistent store (*Default*: `false`).
- * `--metadata-caching-interval-ms`: Number of milliseconds to wait in between caching the names of available metric types (for use in building canary configs; *Default*: `60000`).
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--stackdriver-enabled`: Whether or not to enable Stackdriver as a metrics service (*Default*: `false`).
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--gcs-enabled`: Whether or not to enable GCS as a persistent store (_Default_: `false`).
+- `--metadata-caching-interval-ms`: Number of milliseconds to wait in between caching the names of available metric types (for use in building canary configs; _Default_: `60000`).
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--stackdriver-enabled`: Whether or not to enable Stackdriver as a metrics service (_Default_: `false`).
---
+
## hal config canary google enable
Set Spinnaker's canary analysis Google service integration to enabled.
#### Usage
+
```
hal config canary google enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config canary newrelic
Configure your canary analysis New Relic service integration settings for Spinnaker.
#### Usage
+
```
hal config canary newrelic [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `account`: Manage and view Spinnaker configuration for the newrelic service integration's canary accounts.
- * `disable`: Set Spinnaker's canary analysis newrelic service integration to disabled.
- * `enable`: Set Spinnaker's canary analysis newrelic service integration to enabled.
+
+- `account`: Manage and view Spinnaker configuration for the newrelic service integration's canary accounts.
+- `disable`: Set Spinnaker's canary analysis newrelic service integration to disabled.
+- `enable`: Set Spinnaker's canary analysis newrelic service integration to enabled.
---
+
## hal config canary newrelic account
Manage and view Spinnaker configuration for the newrelic service integration's canary accounts.
#### Usage
+
```
hal config canary newrelic account ACCOUNT [parameters] [subcommands]
```
#### Parameters
+
`ACCOUNT`: The name of the canary account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `add`: Add a canary account to the NewRelic service integration.
- * `delete`: Delete a specific newrelic canary account by name.
- * `edit`: Edit a canary account in the newrelic service integration.
- * `get`: Get the specified canary account details for the newrelic service integration.
- * `list`: List the canary account names for the newrelic service integration.
+
+- `add`: Add a canary account to the NewRelic service integration.
+- `delete`: Delete a specific newrelic canary account by name.
+- `edit`: Edit a canary account in the newrelic service integration.
+- `get`: Get the specified canary account details for the newrelic service integration.
+- `list`: List the canary account names for the newrelic service integration.
---
+
## hal config canary newrelic account add
Add a canary account to the NewRelic service integration.
#### Usage
+
```
hal config canary newrelic account add ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the canary account to operate on.
- * `--api-key`: (*Required*) (*Sensitive data* - user will be prompted on standard input) Your account's unique New Relic Insights API key. See [https://docs.newrelic.com/docs/insights/insights-api/get-data/query-insights-event-data-api](https://docs.newrelic.com/docs/insights/insights-api/get-data/query-insights-event-data-api).
- * `--application-key`: (*Required*) Your New Relic account id. See [https://docs.newrelic.com/docs/accounts/install-new-relic/account-setup/account-id](https://docs.newrelic.com/docs/accounts/install-new-relic/account-setup/account-id).
- * `--base-url`: (*Required*) The base URL to the New Relic Insights server.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--api-key`: (_Required_) (_Sensitive data_ - user will be prompted on standard input) Your account's unique New Relic Insights API key. See [https://docs.newrelic.com/docs/insights/insights-api/get-data/query-insights-event-data-api](https://docs.newrelic.com/docs/insights/insights-api/get-data/query-insights-event-data-api).
+- `--application-key`: (_Required_) Your New Relic account id. See [https://docs.newrelic.com/docs/accounts/install-new-relic/account-setup/account-id](https://docs.newrelic.com/docs/accounts/install-new-relic/account-setup/account-id).
+- `--base-url`: (_Required_) The base URL to the New Relic Insights server.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config canary newrelic account delete
Delete a specific newrelic canary account by name.
#### Usage
+
```
hal config canary newrelic account delete ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the canary account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config canary newrelic account edit
Edit a canary account in the newrelic service integration.
#### Usage
+
```
hal config canary newrelic account edit ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the canary account to operate on.
- * `--api-key`: (*Sensitive data* - user will be prompted on standard input) Your account's unique New Relic Insights API key. See [https://docs.newrelic.com/docs/insights/insights-api/get-data/query-insights-event-data-api](https://docs.newrelic.com/docs/insights/insights-api/get-data/query-insights-event-data-api).
- * `--application-key`: Your New Relic account id. See [https://docs.newrelic.com/docs/accounts/install-new-relic/account-setup/account-id](https://docs.newrelic.com/docs/accounts/install-new-relic/account-setup/account-id).
- * `--base-url`: The base URL to the New Relic Insights server.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--api-key`: (_Sensitive data_ - user will be prompted on standard input) Your account's unique New Relic Insights API key. See [https://docs.newrelic.com/docs/insights/insights-api/get-data/query-insights-event-data-api](https://docs.newrelic.com/docs/insights/insights-api/get-data/query-insights-event-data-api).
+- `--application-key`: Your New Relic account id. See [https://docs.newrelic.com/docs/accounts/install-new-relic/account-setup/account-id](https://docs.newrelic.com/docs/accounts/install-new-relic/account-setup/account-id).
+- `--base-url`: The base URL to the New Relic Insights server.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config canary newrelic account get
Get the specified canary account details for the newrelic service integration.
#### Usage
+
```
hal config canary newrelic account get ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the canary account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config canary newrelic account list
List the canary account names for the newrelic service integration.
#### Usage
+
```
hal config canary newrelic account list [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config canary newrelic disable
Set Spinnaker's canary analysis newrelic service integration to disabled.
#### Usage
+
```
hal config canary newrelic disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config canary newrelic enable
Set Spinnaker's canary analysis newrelic service integration to enabled.
#### Usage
+
```
hal config canary newrelic enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config canary prometheus
Configure your canary analysis Prometheus service integration settings for Spinnaker.
#### Usage
+
```
hal config canary prometheus [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `account`: Manage and view Spinnaker configuration for the Prometheus service integration's canary accounts.
- * `disable`: Set Spinnaker's canary analysis Prometheus service integration to disabled.
- * `edit`: Edit Spinnaker's canary analysis Prometheus service integration settings.
- * `enable`: Set Spinnaker's canary analysis Prometheus service integration to enabled.
+
+- `account`: Manage and view Spinnaker configuration for the Prometheus service integration's canary accounts.
+- `disable`: Set Spinnaker's canary analysis Prometheus service integration to disabled.
+- `edit`: Edit Spinnaker's canary analysis Prometheus service integration settings.
+- `enable`: Set Spinnaker's canary analysis Prometheus service integration to enabled.
---
+
## hal config canary prometheus account
Manage and view Spinnaker configuration for the Prometheus service integration's canary accounts.
#### Usage
+
```
hal config canary prometheus account ACCOUNT [parameters] [subcommands]
```
#### Parameters
+
`ACCOUNT`: The name of the canary account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `add`: Add a canary account to the Prometheus service integration.
- * `delete`: Delete a specific Prometheus canary account by name.
- * `edit`: Edit a canary account in the Prometheus service integration.
- * `get`: Get the specified canary account details for the Prometheus service integration.
- * `list`: List the canary account names for the Prometheus service integration.
+
+- `add`: Add a canary account to the Prometheus service integration.
+- `delete`: Delete a specific Prometheus canary account by name.
+- `edit`: Edit a canary account in the Prometheus service integration.
+- `get`: Get the specified canary account details for the Prometheus service integration.
+- `list`: List the canary account names for the Prometheus service integration.
---
+
## hal config canary prometheus account add
Add a canary account to the Prometheus service integration.
#### Usage
+
```
hal config canary prometheus account add ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the canary account to operate on.
- * `--base-url`: (*Required*) The base URL to the Prometheus server.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--password`: (*Sensitive data* - user will be prompted on standard input) A basic auth password.
- * `--username`: A basic auth username.
- * `--username-password-file`: The path to a file containing "username:password".
+- `--base-url`: (_Required_) The base URL to the Prometheus server.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--password`: (_Sensitive data_ - user will be prompted on standard input) A basic auth password.
+- `--username`: A basic auth username.
+- `--username-password-file`: The path to a file containing "username:password".
---
+
## hal config canary prometheus account delete
Delete a specific Prometheus canary account by name.
#### Usage
+
```
hal config canary prometheus account delete ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the canary account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config canary prometheus account edit
Edit a canary account in the Prometheus service integration.
#### Usage
+
```
hal config canary prometheus account edit ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the canary account to operate on.
- * `--base-url`: The base URL to the Prometheus server.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--password`: (*Sensitive data* - user will be prompted on standard input) A basic auth password.
- * `--username`: A basic auth username.
- * `--username-password-file`: The path to a file containing "username:password".
+- `--base-url`: The base URL to the Prometheus server.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--password`: (_Sensitive data_ - user will be prompted on standard input) A basic auth password.
+- `--username`: A basic auth username.
+- `--username-password-file`: The path to a file containing "username:password".
---
+
## hal config canary prometheus account get
Get the specified canary account details for the Prometheus service integration.
#### Usage
+
```
hal config canary prometheus account get ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the canary account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config canary prometheus account list
List the canary account names for the Prometheus service integration.
#### Usage
+
```
hal config canary prometheus account list [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config canary prometheus disable
Set Spinnaker's canary analysis Prometheus service integration to disabled.
#### Usage
+
```
hal config canary prometheus disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config canary prometheus edit
Edit Spinnaker's canary analysis Prometheus service integration settings.
#### Usage
+
```
hal config canary prometheus edit [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--metadata-caching-interval-ms`: Number of milliseconds to wait in between caching the names of available metric types (for use in building canary configs; *Default*: `60000`).
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--metadata-caching-interval-ms`: Number of milliseconds to wait in between caching the names of available metric types (for use in building canary configs; _Default_: `60000`).
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config canary prometheus enable
Set Spinnaker's canary analysis Prometheus service integration to enabled.
#### Usage
+
```
hal config canary prometheus enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config canary signalfx
Configure your canary analysis SignalFx service integration settings for Spinnaker.
#### Usage
+
```
hal config canary signalfx [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `account`: Manage and view Spinnaker configuration for the Signalfx service integration's canary accounts.
- * `disable`: Set Spinnaker's canary analysis Signalfx service integration to disabled.
- * `enable`: Set Spinnaker's canary analysis Signalfx service integration to enabled.
+
+- `account`: Manage and view Spinnaker configuration for the Signalfx service integration's canary accounts.
+- `disable`: Set Spinnaker's canary analysis Signalfx service integration to disabled.
+- `enable`: Set Spinnaker's canary analysis Signalfx service integration to enabled.
---
+
## hal config canary signalfx account
Manage and view Spinnaker configuration for the Signalfx service integration's canary accounts.
#### Usage
+
```
hal config canary signalfx account ACCOUNT [parameters] [subcommands]
```
#### Parameters
+
`ACCOUNT`: The name of the canary account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `add`: Add a canary account to the Signalfx service integration.
- * `delete`: Delete a specific Signalfx canary account by name.
- * `edit`: Edit a canary account in the Signalfx service integration.
- * `get`: Get the specified canary account details for the Signalfx service integration.
- * `list`: List the canary account names for the Signalfx service integration.
+
+- `add`: Add a canary account to the Signalfx service integration.
+- `delete`: Delete a specific Signalfx canary account by name.
+- `edit`: Edit a canary account in the Signalfx service integration.
+- `get`: Get the specified canary account details for the Signalfx service integration.
+- `list`: List the canary account names for the Signalfx service integration.
---
+
## hal config canary signalfx account add
Add a canary account to the Signalfx service integration.
#### Usage
+
```
hal config canary signalfx account add ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the canary account to operate on.
- * `--access-token`: (*Required*) (*Sensitive data* - user will be prompted on standard input) The SignalFx access token.
- * `--base-url`: The base URL to the SignalFx server. Defaults to [https://stream.signalfx.com](https://stream.signalfx.com)
- * `--default-location-key`: Location key is used to filter by deployment region. If omitted requests must supply the _location_key if it is needed.
- * `--default-scope-key`: Scope key is used to distinguish between base and canary deployments. If omitted every request must supply the _scope_key param in extended scope params
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--access-token`: (_Required_) (_Sensitive data_ - user will be prompted on standard input) The SignalFx access token.
+- `--base-url`: The base URL to the SignalFx server. Defaults to [https://stream.signalfx.com](https://stream.signalfx.com)
+- `--default-location-key`: Location key is used to filter by deployment region. If omitted requests must supply the \_location_key if it is needed.
+- `--default-scope-key`: Scope key is used to distinguish between base and canary deployments. If omitted every request must supply the \_scope_key param in extended scope params
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config canary signalfx account delete
Delete a specific Signalfx canary account by name.
#### Usage
+
```
hal config canary signalfx account delete ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the canary account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config canary signalfx account edit
Edit a canary account in the Signalfx service integration.
#### Usage
+
```
hal config canary signalfx account edit ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the canary account to operate on.
- * `--access-token`: (*Sensitive data* - user will be prompted on standard input) The SignalFx access token.
- * `--base-url`: The base URL to the SignalFx server. Defaults to [https://stream.signalfx.com](https://stream.signalfx.com)
- * `--default-location-key`: Location key is used to filter by deployment region. If omitted requests must supply the _location_key if it is needed.
- * `--default-scope-key`: Scope key is used to distinguish between base and canary deployments. If omitted every request must supply the _scope_key param in extended scope params
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--access-token`: (_Sensitive data_ - user will be prompted on standard input) The SignalFx access token.
+- `--base-url`: The base URL to the SignalFx server. Defaults to [https://stream.signalfx.com](https://stream.signalfx.com)
+- `--default-location-key`: Location key is used to filter by deployment region. If omitted requests must supply the \_location_key if it is needed.
+- `--default-scope-key`: Scope key is used to distinguish between base and canary deployments. If omitted every request must supply the \_scope_key param in extended scope params
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config canary signalfx account get
Get the specified canary account details for the Signalfx service integration.
#### Usage
+
```
hal config canary signalfx account get ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the canary account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config canary signalfx account list
List the canary account names for the Signalfx service integration.
#### Usage
+
```
hal config canary signalfx account list [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config canary signalfx disable
Set Spinnaker's canary analysis Signalfx service integration to disabled.
#### Usage
+
```
hal config canary signalfx disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config canary signalfx enable
Set Spinnaker's canary analysis Signalfx service integration to enabled.
#### Usage
+
```
hal config canary signalfx enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config ci
Configure, validate, and view the specified Continuous Integration service.
#### Usage
+
```
hal config ci [subcommands]
```
#### Subcommands
- * `codebuild`: Manage and view Spinnaker configuration for AWS CodeBuild
- * `concourse`: Manage and view Spinnaker configuration for the concourse ci
- * `gcb`: Manage and view Spinnaker configuration for Google Cloud Build
- * `jenkins`: Manage and view Spinnaker configuration for the jenkins ci
- * `travis`: Manage and view Spinnaker configuration for the travis ci
- * `wercker`: Manage and view Spinnaker configuration for the wercker ci
+
+- `codebuild`: Manage and view Spinnaker configuration for AWS CodeBuild
+- `concourse`: Manage and view Spinnaker configuration for the concourse ci
+- `gcb`: Manage and view Spinnaker configuration for Google Cloud Build
+- `jenkins`: Manage and view Spinnaker configuration for the jenkins ci
+- `travis`: Manage and view Spinnaker configuration for the travis ci
+- `wercker`: Manage and view Spinnaker configuration for the wercker ci
---
+
## hal config ci codebuild
Manage and view Spinnaker configuration for AWS CodeBuild
#### Usage
+
```
hal config ci codebuild [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `account`: Manage and view Spinnaker configuration for AWS CodeBuild service account.
- * `disable`: Set the codebuild ci as disabled
- * `edit`: Set CI provider-wide properties for AWS CodeBuild
- * `enable`: Set the codebuild ci as enabled
+
+- `account`: Manage and view Spinnaker configuration for AWS CodeBuild service account.
+- `disable`: Set the codebuild ci as disabled
+- `edit`: Set CI provider-wide properties for AWS CodeBuild
+- `enable`: Set the codebuild ci as enabled
---
+
## hal config ci codebuild account
Manage and view Spinnaker configuration for AWS CodeBuild service account.
#### Usage
+
```
hal config ci codebuild account ACCOUNT [parameters] [subcommands]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `add`: Add a AWS CodeBuild account.
- * `delete`: Delete a AWS CodeBuild account.
- * `edit`: Edit a AWS CodeBuild account.
- * `get`: Get the account details for AWS CodeBuild.
- * `list`: List the AWS CodeBuild accounts.
+
+- `add`: Add a AWS CodeBuild account.
+- `delete`: Delete a AWS CodeBuild account.
+- `edit`: Edit a AWS CodeBuild account.
+- `get`: Get the account details for AWS CodeBuild.
+- `list`: List the AWS CodeBuild accounts.
---
+
## hal config ci codebuild account add
Add a AWS CodeBuild account.
#### Usage
+
```
hal config ci codebuild account add ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--account-id`: The AWS account ID that will be used to trigger CodeBuild build.
- * `--assume-role`: If set, Halyard will configure a credentials provider that uses AWS Security Token Service to assume the specified role.
+
+- `--account-id`: The AWS account ID that will be used to trigger CodeBuild build.
+- `--assume-role`: If set, Halyard will configure a credentials provider that uses AWS Security Token Service to assume the specified role.
Example: "user/spinnaker" or "role/spinnakerManaged"
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--region`: (*Required*) The AWS region in which your CodeBuild projects live.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--region`: (_Required_) The AWS region in which your CodeBuild projects live.
---
+
## hal config ci codebuild account delete
Delete a AWS CodeBuild account.
#### Usage
+
```
hal config ci codebuild account delete ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config ci codebuild account edit
Edit a AWS CodeBuild account.
#### Usage
+
```
hal config ci codebuild account edit ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--account-id`: The AWS account ID that will be used to trigger CodeBuild build.
- * `--assume-role`: If set, Halyard will configure a credentials provider that uses AWS Security Token Service to assume the specified role.
+
+- `--account-id`: The AWS account ID that will be used to trigger CodeBuild build.
+- `--assume-role`: If set, Halyard will configure a credentials provider that uses AWS Security Token Service to assume the specified role.
Example: "user/spinnaker" or "role/spinnakerManaged"
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--region`: The AWS region in which your CodeBuild projects live.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--region`: The AWS region in which your CodeBuild projects live.
---
+
## hal config ci codebuild account get
Get the account details for AWS CodeBuild.
#### Usage
+
```
hal config ci codebuild account get ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config ci codebuild account list
List the AWS CodeBuild accounts.
#### Usage
+
```
hal config ci codebuild account list [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config ci codebuild disable
Set the codebuild ci as disabled
#### Usage
+
```
hal config ci codebuild disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config ci codebuild edit
Set CI provider-wide properties for AWS CodeBuild
#### Usage
+
```
hal config ci codebuild edit [parameters]
```
#### Parameters
- * `--access-key-id`: Your AWS Access Key ID. If not provided, Halyard/Spinnaker will try to find AWS credentials as described at [http://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/credentials.html#credentials-default](http://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/credentials.html#credentials-default)
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--secret-access-key`: (*Sensitive data* - user will be prompted on standard input) Your AWS Secret Key.
+- `--access-key-id`: Your AWS Access Key ID. If not provided, Halyard/Spinnaker will try to find AWS credentials as described at [http://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/credentials.html#credentials-default](http://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/credentials.html#credentials-default)
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--secret-access-key`: (_Sensitive data_ - user will be prompted on standard input) Your AWS Secret Key.
---
+
## hal config ci codebuild enable
Set the codebuild ci as enabled
#### Usage
+
```
hal config ci codebuild enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config ci concourse
Manage and view Spinnaker configuration for the concourse ci
#### Usage
+
```
hal config ci concourse [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `disable`: Set the concourse ci as disabled
- * `enable`: Set the concourse ci as enabled
- * `master`: Manage and view Spinnaker configuration for the concourse Continuous Integration services's master
+
+- `disable`: Set the concourse ci as disabled
+- `enable`: Set the concourse ci as enabled
+- `master`: Manage and view Spinnaker configuration for the concourse Continuous Integration services's master
---
+
## hal config ci concourse disable
Set the concourse ci as disabled
#### Usage
+
```
hal config ci concourse disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config ci concourse enable
Set the concourse ci as enabled
#### Usage
+
```
hal config ci concourse enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config ci concourse master
Manage and view Spinnaker configuration for the concourse Continuous Integration services's master
#### Usage
+
```
hal config ci concourse master MASTER [parameters] [subcommands]
```
#### Parameters
+
`MASTER`: The name of the master to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `add`: Add a master for the concourse Continuous Integration service.
- * `delete`: Delete a specific concourse master by name.
- * `edit`: Edit a master for the concourse Continuous Integration service.
- * `get`: Get the specified master details for concourse.
- * `list`: List the master names for concourse.
+
+- `add`: Add a master for the concourse Continuous Integration service.
+- `delete`: Delete a specific concourse master by name.
+- `edit`: Edit a master for the concourse Continuous Integration service.
+- `get`: Get the specified master details for concourse.
+- `list`: List the master names for concourse.
---
+
## hal config ci concourse master add
Add a master for the concourse Continuous Integration service.
#### Usage
+
```
hal config ci concourse master add MASTER [parameters]
```
#### Parameters
+
`MASTER`: The name of the master to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--password`: (*Required*) (*Sensitive data* - user will be prompted on standard input) The password of the concourse user to authenticate as.
- * `--read-permissions`: (*Default*: `[]`) A user must have at least one of these roles in order to view this build master or use it as a trigger source.
- * `--url`: (*Required*) The url your concourse search is reachable at.
- * `--username`: (*Required*) The username of the concourse user to authenticate as.
- * `--write-permissions`: (*Default*: `[]`) A user must have at least one of these roles in order to be able to run jobs on this build master.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--password`: (_Required_) (_Sensitive data_ - user will be prompted on standard input) The password of the concourse user to authenticate as.
+- `--read-permissions`: (_Default_: `[]`) A user must have at least one of these roles in order to view this build master or use it as a trigger source.
+- `--url`: (_Required_) The url your concourse search is reachable at.
+- `--username`: (_Required_) The username of the concourse user to authenticate as.
+- `--write-permissions`: (_Default_: `[]`) A user must have at least one of these roles in order to be able to run jobs on this build master.
---
+
## hal config ci concourse master delete
Delete a specific concourse master by name.
#### Usage
+
```
hal config ci concourse master delete MASTER [parameters]
```
#### Parameters
+
`MASTER`: The name of the master to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config ci concourse master edit
Edit a master for the concourse Continuous Integration service.
#### Usage
+
```
hal config ci concourse master edit MASTER [parameters]
```
#### Parameters
+
`MASTER`: The name of the master to operate on.
- * `--add-read-permission`: Add this permission to the list of read permissions.
- * `--add-write-permission`: Add this permission to the list of write permissions.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--password`: (*Sensitive data* - user will be prompted on standard input) The password of the concourse user to authenticate as.
- * `--read-permissions`: A user must have at least one of these roles in order to view this build master or use it as a trigger source.
- * `--remove-read-permission`: Remove this permission from the list of read permissions.
- * `--remove-write-permission`: Remove this permission from the list of write permissions.
- * `--url`: The url your concourse search is reachable at.
- * `--username`: The username of the concourse user to authenticate as.
- * `--write-permissions`: A user must have at least one of these roles in order to be able to run jobs on this build master.
+- `--add-read-permission`: Add this permission to the list of read permissions.
+- `--add-write-permission`: Add this permission to the list of write permissions.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--password`: (_Sensitive data_ - user will be prompted on standard input) The password of the concourse user to authenticate as.
+- `--read-permissions`: A user must have at least one of these roles in order to view this build master or use it as a trigger source.
+- `--remove-read-permission`: Remove this permission from the list of read permissions.
+- `--remove-write-permission`: Remove this permission from the list of write permissions.
+- `--url`: The url your concourse search is reachable at.
+- `--username`: The username of the concourse user to authenticate as.
+- `--write-permissions`: A user must have at least one of these roles in order to be able to run jobs on this build master.
---
+
## hal config ci concourse master get
Get the specified master details for concourse.
#### Usage
+
```
hal config ci concourse master get MASTER [parameters]
```
#### Parameters
+
`MASTER`: The name of the master to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config ci concourse master list
List the master names for concourse.
#### Usage
+
```
hal config ci concourse master list [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config ci gcb
Manage and view Spinnaker configuration for Google Cloud Build
#### Usage
+
```
hal config ci gcb [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `account`: Manage and view Spinnaker configuration for the Google Cloud Build service account.
- * `disable`: Set the gcb ci as disabled
- * `enable`: Set the gcb ci as enabled
+
+- `account`: Manage and view Spinnaker configuration for the Google Cloud Build service account.
+- `disable`: Set the gcb ci as disabled
+- `enable`: Set the gcb ci as enabled
---
+
## hal config ci gcb account
Manage and view Spinnaker configuration for the Google Cloud Build service account.
#### Usage
+
```
hal config ci gcb account ACCOUNT [parameters] [subcommands]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `add`: Add a Google Cloud Build account.
- * `delete`: Delete a Google Cloud Build account.
- * `edit`: Edit a Google Cloud Build account.
- * `list`: List the Google Cloud Build accounts.
+
+- `add`: Add a Google Cloud Build account.
+- `delete`: Delete a Google Cloud Build account.
+- `edit`: Edit a Google Cloud Build account.
+- `list`: List the Google Cloud Build accounts.
---
+
## hal config ci gcb account add
Add a Google Cloud Build account.
#### Usage
+
```
hal config ci gcb account add ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--json-key`: The path to a JSON service account that Spinnaker will use as credentials.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--project`: (*Required*) The name of the GCP project in which to trigger and monitor builds.
- * `--subscription-name`: The name of the PubSub subscription on which to listen for build changes.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--json-key`: The path to a JSON service account that Spinnaker will use as credentials.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--project`: (_Required_) The name of the GCP project in which to trigger and monitor builds.
+- `--subscription-name`: The name of the PubSub subscription on which to listen for build changes.
---
+
## hal config ci gcb account delete
Delete a Google Cloud Build account.
#### Usage
+
```
hal config ci gcb account delete ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config ci gcb account edit
Edit a Google Cloud Build account.
#### Usage
+
```
hal config ci gcb account edit ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--json-key`: The path to a JSON service account that Spinnaker will use as credentials.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--project`: The name of the GCP project in which to trigger and monitor builds.
- * `--subscription-name`: The name of the PubSub subscription on which to listen for build changes.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--json-key`: The path to a JSON service account that Spinnaker will use as credentials.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--project`: The name of the GCP project in which to trigger and monitor builds.
+- `--subscription-name`: The name of the PubSub subscription on which to listen for build changes.
---
+
## hal config ci gcb account list
List the Google Cloud Build accounts.
#### Usage
+
```
hal config ci gcb account list [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config ci gcb disable
Set the gcb ci as disabled
#### Usage
+
```
hal config ci gcb disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config ci gcb enable
Set the gcb ci as enabled
#### Usage
+
```
hal config ci gcb enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config ci jenkins
Manage and view Spinnaker configuration for the jenkins ci
#### Usage
+
```
hal config ci jenkins [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `disable`: Set the jenkins ci as disabled
- * `enable`: Set the jenkins ci as enabled
- * `master`: Manage and view Spinnaker configuration for the jenkins Continuous Integration services's master
+
+- `disable`: Set the jenkins ci as disabled
+- `enable`: Set the jenkins ci as enabled
+- `master`: Manage and view Spinnaker configuration for the jenkins Continuous Integration services's master
---
+
## hal config ci jenkins disable
Set the jenkins ci as disabled
#### Usage
+
```
hal config ci jenkins disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config ci jenkins enable
Set the jenkins ci as enabled
#### Usage
+
```
hal config ci jenkins enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config ci jenkins master
Manage and view Spinnaker configuration for the jenkins Continuous Integration services's master
#### Usage
+
```
hal config ci jenkins master MASTER [parameters] [subcommands]
```
#### Parameters
+
`MASTER`: The name of the master to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `add`: Add a master for the jenkins Continuous Integration service.
- * `delete`: Delete a specific jenkins master by name.
- * `edit`: Edit a master for the jenkins Continuous Integration service.
- * `get`: Get the specified master details for jenkins.
- * `list`: List the master names for jenkins.
+
+- `add`: Add a master for the jenkins Continuous Integration service.
+- `delete`: Delete a specific jenkins master by name.
+- `edit`: Edit a master for the jenkins Continuous Integration service.
+- `get`: Get the specified master details for jenkins.
+- `list`: List the master names for jenkins.
---
+
## hal config ci jenkins master add
Add a master for the jenkins Continuous Integration service.
#### Usage
+
```
hal config ci jenkins master add MASTER [parameters]
```
#### Parameters
+
`MASTER`: The name of the master to operate on.
- * `--address`: (*Required*) The address your jenkins master is reachable at.
- * `--csrf`: Whether or not to negotiate CSRF tokens when calling Jenkins.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--password`: (*Sensitive data* - user will be prompted on standard input) The password of the jenkins user to authenticate as.
- * `--read-permissions`: (*Default*: `[]`) A user must have at least one of these roles in order to view this build master or use it as a trigger source.
- * `--username`: The username of the jenkins user to authenticate as.
- * `--write-permissions`: (*Default*: `[]`) A user must have at least one of these roles in order to be able to run jobs on this build master.
+- `--address`: (_Required_) The address your jenkins master is reachable at.
+- `--csrf`: Whether or not to negotiate CSRF tokens when calling Jenkins.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--password`: (_Sensitive data_ - user will be prompted on standard input) The password of the jenkins user to authenticate as.
+- `--read-permissions`: (_Default_: `[]`) A user must have at least one of these roles in order to view this build master or use it as a trigger source.
+- `--username`: The username of the jenkins user to authenticate as.
+- `--write-permissions`: (_Default_: `[]`) A user must have at least one of these roles in order to be able to run jobs on this build master.
---
+
## hal config ci jenkins master delete
Delete a specific jenkins master by name.
#### Usage
+
```
hal config ci jenkins master delete MASTER [parameters]
```
#### Parameters
+
`MASTER`: The name of the master to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config ci jenkins master edit
Edit a master for the jenkins Continuous Integration service.
#### Usage
+
```
hal config ci jenkins master edit MASTER [parameters]
```
#### Parameters
+
`MASTER`: The name of the master to operate on.
- * `--add-read-permission`: Add this permission to the list of read permissions.
- * `--add-write-permission`: Add this permission to the list of write permissions.
- * `--address`: The address your jenkins master is reachable at.
- * `--csrf`: Whether or not to negotiate CSRF tokens when calling Jenkins.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--password`: (*Sensitive data* - user will be prompted on standard input) The password of the jenkins user to authenticate as.
- * `--read-permissions`: A user must have at least one of these roles in order to view this build master or use it as a trigger source.
- * `--remove-read-permission`: Remove this permission from the list of read permissions.
- * `--remove-write-permission`: Remove this permission from the list of write permissions.
- * `--username`: The username of the jenkins user to authenticate as.
- * `--write-permissions`: A user must have at least one of these roles in order to be able to run jobs on this build master.
+- `--add-read-permission`: Add this permission to the list of read permissions.
+- `--add-write-permission`: Add this permission to the list of write permissions.
+- `--address`: The address your jenkins master is reachable at.
+- `--csrf`: Whether or not to negotiate CSRF tokens when calling Jenkins.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--password`: (_Sensitive data_ - user will be prompted on standard input) The password of the jenkins user to authenticate as.
+- `--read-permissions`: A user must have at least one of these roles in order to view this build master or use it as a trigger source.
+- `--remove-read-permission`: Remove this permission from the list of read permissions.
+- `--remove-write-permission`: Remove this permission from the list of write permissions.
+- `--username`: The username of the jenkins user to authenticate as.
+- `--write-permissions`: A user must have at least one of these roles in order to be able to run jobs on this build master.
---
+
## hal config ci jenkins master get
Get the specified master details for jenkins.
#### Usage
+
```
hal config ci jenkins master get MASTER [parameters]
```
#### Parameters
+
`MASTER`: The name of the master to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config ci jenkins master list
List the master names for jenkins.
#### Usage
+
```
hal config ci jenkins master list [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config ci travis
Manage and view Spinnaker configuration for the travis ci
#### Usage
+
```
hal config ci travis [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `disable`: Set the travis ci as disabled
- * `enable`: Set the travis ci as enabled
- * `master`: Manage and view Spinnaker configuration for the travis Continuous Integration services's master
+
+- `disable`: Set the travis ci as disabled
+- `enable`: Set the travis ci as enabled
+- `master`: Manage and view Spinnaker configuration for the travis Continuous Integration services's master
---
+
## hal config ci travis disable
Set the travis ci as disabled
#### Usage
+
```
hal config ci travis disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config ci travis enable
Set the travis ci as enabled
#### Usage
+
```
hal config ci travis enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config ci travis master
Manage and view Spinnaker configuration for the travis Continuous Integration services's master
#### Usage
+
```
hal config ci travis master MASTER [parameters] [subcommands]
```
#### Parameters
+
`MASTER`: The name of the master to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `add`: Add a master for the travis Continuous Integration service.
- * `delete`: Delete a specific travis master by name.
- * `edit`: Edit a master for the travis Continuous Integration service.
- * `get`: Get the specified master details for travis.
- * `list`: List the master names for travis.
+
+- `add`: Add a master for the travis Continuous Integration service.
+- `delete`: Delete a specific travis master by name.
+- `edit`: Edit a master for the travis Continuous Integration service.
+- `get`: Get the specified master details for travis.
+- `list`: List the master names for travis.
---
+
## hal config ci travis master add
Add a master for the travis Continuous Integration service.
#### Usage
+
```
hal config ci travis master add MASTER [parameters]
```
#### Parameters
+
`MASTER`: The name of the master to operate on.
- * `--address`: (*Required*) The address of the travis API ([https://api.travis-ci.org](https://api.travis-ci.org)).
- * `--base-url`: (*Required*) The base URL to the travis UI ([https://travis-ci.org](https://travis-ci.org)).
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--github-token`: (*Sensitive data* - user will be prompted on standard input) The github token to authentiacte against travis with.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--number-of-repositories`: How many repositories the travis integration should fetch from the api each time the poller runs. Should be set a bit higher than the expected maximum number of repositories built within the poll interval.
- * `--read-permissions`: (*Default*: `[]`) A user must have at least one of these roles in order to view this build master or use it as a trigger source.
- * `--write-permissions`: (*Default*: `[]`) A user must have at least one of these roles in order to be able to run jobs on this build master.
+- `--address`: (_Required_) The address of the travis API ([https://api.travis-ci.org](https://api.travis-ci.org)).
+- `--base-url`: (_Required_) The base URL to the travis UI ([https://travis-ci.org](https://travis-ci.org)).
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--github-token`: (_Sensitive data_ - user will be prompted on standard input) The github token to authentiacte against travis with.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--number-of-repositories`: How many repositories the travis integration should fetch from the api each time the poller runs. Should be set a bit higher than the expected maximum number of repositories built within the poll interval.
+- `--read-permissions`: (_Default_: `[]`) A user must have at least one of these roles in order to view this build master or use it as a trigger source.
+- `--write-permissions`: (_Default_: `[]`) A user must have at least one of these roles in order to be able to run jobs on this build master.
---
+
## hal config ci travis master delete
Delete a specific travis master by name.
#### Usage
+
```
hal config ci travis master delete MASTER [parameters]
```
#### Parameters
+
`MASTER`: The name of the master to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config ci travis master edit
Edit a master for the travis Continuous Integration service.
#### Usage
+
```
hal config ci travis master edit MASTER [parameters]
```
#### Parameters
+
`MASTER`: The name of the master to operate on.
- * `--add-read-permission`: Add this permission to the list of read permissions.
- * `--add-write-permission`: Add this permission to the list of write permissions.
- * `--address`: The address of the travis API ([https://api.travis-ci.org](https://api.travis-ci.org)).
- * `--base-url`: The base URL to the travis UI ([https://travis-ci.org](https://travis-ci.org)).
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--github-token`: (*Sensitive data* - user will be prompted on standard input) The github token to authentiacte against travis with.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--number-of-repositories`: How many repositories the travis integration should fetch from the api each time the poller runs. Should be set a bit higher than the expected maximum number of repositories built within the poll interval.
- * `--read-permissions`: A user must have at least one of these roles in order to view this build master or use it as a trigger source.
- * `--remove-read-permission`: Remove this permission from the list of read permissions.
- * `--remove-write-permission`: Remove this permission from the list of write permissions.
- * `--write-permissions`: A user must have at least one of these roles in order to be able to run jobs on this build master.
+- `--add-read-permission`: Add this permission to the list of read permissions.
+- `--add-write-permission`: Add this permission to the list of write permissions.
+- `--address`: The address of the travis API ([https://api.travis-ci.org](https://api.travis-ci.org)).
+- `--base-url`: The base URL to the travis UI ([https://travis-ci.org](https://travis-ci.org)).
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--github-token`: (_Sensitive data_ - user will be prompted on standard input) The github token to authentiacte against travis with.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--number-of-repositories`: How many repositories the travis integration should fetch from the api each time the poller runs. Should be set a bit higher than the expected maximum number of repositories built within the poll interval.
+- `--read-permissions`: A user must have at least one of these roles in order to view this build master or use it as a trigger source.
+- `--remove-read-permission`: Remove this permission from the list of read permissions.
+- `--remove-write-permission`: Remove this permission from the list of write permissions.
+- `--write-permissions`: A user must have at least one of these roles in order to be able to run jobs on this build master.
---
+
## hal config ci travis master get
Get the specified master details for travis.
#### Usage
+
```
hal config ci travis master get MASTER [parameters]
```
#### Parameters
+
`MASTER`: The name of the master to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config ci travis master list
List the master names for travis.
#### Usage
+
```
hal config ci travis master list [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config ci wercker
Manage and view Spinnaker configuration for the wercker ci
#### Usage
+
```
hal config ci wercker [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `disable`: Set the wercker ci as disabled
- * `enable`: Set the wercker ci as enabled
- * `master`: Manage and view Spinnaker configuration for the wercker Continuous Integration services's master
+
+- `disable`: Set the wercker ci as disabled
+- `enable`: Set the wercker ci as enabled
+- `master`: Manage and view Spinnaker configuration for the wercker Continuous Integration services's master
---
+
## hal config ci wercker disable
Set the wercker ci as disabled
#### Usage
+
```
hal config ci wercker disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config ci wercker enable
Set the wercker ci as enabled
#### Usage
+
```
hal config ci wercker enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config ci wercker master
Manage and view Spinnaker configuration for the wercker Continuous Integration services's master
#### Usage
+
```
hal config ci wercker master MASTER [parameters] [subcommands]
```
#### Parameters
+
`MASTER`: The name of the master to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `add`: Add a master for the wercker Continuous Integration service.
- * `delete`: Delete a specific wercker master by name.
- * `edit`: Edit a master for the wercker Continuous Integration service.
- * `get`: Get the specified master details for wercker.
- * `list`: List the master names for wercker.
+
+- `add`: Add a master for the wercker Continuous Integration service.
+- `delete`: Delete a specific wercker master by name.
+- `edit`: Edit a master for the wercker Continuous Integration service.
+- `get`: Get the specified master details for wercker.
+- `list`: List the master names for wercker.
---
+
## hal config ci wercker master add
Add a master for the wercker Continuous Integration service.
#### Usage
+
```
hal config ci wercker master add MASTER [parameters]
```
#### Parameters
+
`MASTER`: The name of the master to operate on.
- * `--address`: (*Required*) The address your Wercker master is reachable at.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--read-permissions`: (*Default*: `[]`) A user must have at least one of these roles in order to view this build master or use it as a trigger source.
- * `--token`: (*Sensitive data* - user will be prompted on standard input) The personal token of the Wercker user to authenticate as.
- * `--user`: The username of the Wercker user to authenticate as.
- * `--write-permissions`: (*Default*: `[]`) A user must have at least one of these roles in order to be able to run jobs on this build master.
+- `--address`: (_Required_) The address your Wercker master is reachable at.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--read-permissions`: (_Default_: `[]`) A user must have at least one of these roles in order to view this build master or use it as a trigger source.
+- `--token`: (_Sensitive data_ - user will be prompted on standard input) The personal token of the Wercker user to authenticate as.
+- `--user`: The username of the Wercker user to authenticate as.
+- `--write-permissions`: (_Default_: `[]`) A user must have at least one of these roles in order to be able to run jobs on this build master.
---
+
## hal config ci wercker master delete
Delete a specific wercker master by name.
#### Usage
+
```
hal config ci wercker master delete MASTER [parameters]
```
#### Parameters
+
`MASTER`: The name of the master to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config ci wercker master edit
Edit a master for the wercker Continuous Integration service.
#### Usage
+
```
hal config ci wercker master edit MASTER [parameters]
```
#### Parameters
+
`MASTER`: The name of the master to operate on.
- * `--add-read-permission`: Add this permission to the list of read permissions.
- * `--add-write-permission`: Add this permission to the list of write permissions.
- * `--address`: The address your Wercker master is reachable at.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--read-permissions`: A user must have at least one of these roles in order to view this build master or use it as a trigger source.
- * `--remove-read-permission`: Remove this permission from the list of read permissions.
- * `--remove-write-permission`: Remove this permission from the list of write permissions.
- * `--token`: (*Sensitive data* - user will be prompted on standard input) The personal token of the Wercker user to authenticate as.
- * `--user`: The username of the Wercker user to authenticate as.
- * `--write-permissions`: A user must have at least one of these roles in order to be able to run jobs on this build master.
+- `--add-read-permission`: Add this permission to the list of read permissions.
+- `--add-write-permission`: Add this permission to the list of write permissions.
+- `--address`: The address your Wercker master is reachable at.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--read-permissions`: A user must have at least one of these roles in order to view this build master or use it as a trigger source.
+- `--remove-read-permission`: Remove this permission from the list of read permissions.
+- `--remove-write-permission`: Remove this permission from the list of write permissions.
+- `--token`: (_Sensitive data_ - user will be prompted on standard input) The personal token of the Wercker user to authenticate as.
+- `--user`: The username of the Wercker user to authenticate as.
+- `--write-permissions`: A user must have at least one of these roles in order to be able to run jobs on this build master.
---
+
## hal config ci wercker master get
Get the specified master details for wercker.
#### Usage
+
```
hal config ci wercker master get MASTER [parameters]
```
#### Parameters
+
`MASTER`: The name of the master to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config ci wercker master list
List the master names for wercker.
#### Usage
+
```
hal config ci wercker master list [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config deploy
Display the configured Spinnaker deployment.
#### Usage
+
```
hal config deploy [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `component-sizing`: Configure, validate, and view the component sizings for the Spinnaker services.
- * `edit`: Edit Spinnaker's deployment footprint and configuration.
- * `ha`: Configure, validate, and view the specified high availability Spinnaker service configuration.
+
+- `component-sizing`: Configure, validate, and view the component sizings for the Spinnaker services.
+- `edit`: Edit Spinnaker's deployment footprint and configuration.
+- `ha`: Configure, validate, and view the specified high availability Spinnaker service configuration.
---
+
## hal config deploy component-sizing
Configure, validate, and view the component sizings for the Spinnaker services.
#### Usage
+
```
hal config deploy component-sizing [subcommands]
```
#### Subcommands
- * `clouddriver`: Manage and view Spinnaker component sizing configuration for clouddriver
- * `clouddriver-bootstrap`: Manage and view Spinnaker component sizing configuration for clouddriver-bootstrap
- * `clouddriver-caching`: Manage and view Spinnaker component sizing configuration for clouddriver-caching
- * `clouddriver-ro`: Manage and view Spinnaker component sizing configuration for clouddriver-ro
- * `clouddriver-ro-deck`: Manage and view Spinnaker component sizing configuration for clouddriver-ro-deck
- * `clouddriver-rw`: Manage and view Spinnaker component sizing configuration for clouddriver-rw
- * `consul-client`: Manage and view Spinnaker component sizing configuration for consul-client
- * `consul-server`: Manage and view Spinnaker component sizing configuration for consul-server
- * `deck`: Manage and view Spinnaker component sizing configuration for deck
- * `echo`: Manage and view Spinnaker component sizing configuration for echo
- * `echo-scheduler`: Manage and view Spinnaker component sizing configuration for echo-scheduler
- * `echo-worker`: Manage and view Spinnaker component sizing configuration for echo-worker
- * `fiat`: Manage and view Spinnaker component sizing configuration for fiat
- * `front50`: Manage and view Spinnaker component sizing configuration for front50
- * `gate`: Manage and view Spinnaker component sizing configuration for gate
- * `igor`: Manage and view Spinnaker component sizing configuration for igor
- * `kayenta`: Manage and view Spinnaker component sizing configuration for kayenta
- * `monitoring-daemon`: Manage and view Spinnaker component sizing configuration for monitoring-daemon
- * `orca`: Manage and view Spinnaker component sizing configuration for orca
- * `orca-bootstrap`: Manage and view Spinnaker component sizing configuration for orca-bootstrap
- * `redis`: Manage and view Spinnaker component sizing configuration for redis
- * `redis-bootstrap`: Manage and view Spinnaker component sizing configuration for redis-bootstrap
- * `rosco`: Manage and view Spinnaker component sizing configuration for rosco
- * `vault-client`: Manage and view Spinnaker component sizing configuration for vault-client
- * `vault-server`: Manage and view Spinnaker component sizing configuration for vault-server
+
+- `clouddriver`: Manage and view Spinnaker component sizing configuration for clouddriver
+- `clouddriver-bootstrap`: Manage and view Spinnaker component sizing configuration for clouddriver-bootstrap
+- `clouddriver-caching`: Manage and view Spinnaker component sizing configuration for clouddriver-caching
+- `clouddriver-ro`: Manage and view Spinnaker component sizing configuration for clouddriver-ro
+- `clouddriver-ro-deck`: Manage and view Spinnaker component sizing configuration for clouddriver-ro-deck
+- `clouddriver-rw`: Manage and view Spinnaker component sizing configuration for clouddriver-rw
+- `consul-client`: Manage and view Spinnaker component sizing configuration for consul-client
+- `consul-server`: Manage and view Spinnaker component sizing configuration for consul-server
+- `deck`: Manage and view Spinnaker component sizing configuration for deck
+- `echo`: Manage and view Spinnaker component sizing configuration for echo
+- `echo-scheduler`: Manage and view Spinnaker component sizing configuration for echo-scheduler
+- `echo-worker`: Manage and view Spinnaker component sizing configuration for echo-worker
+- `fiat`: Manage and view Spinnaker component sizing configuration for fiat
+- `front50`: Manage and view Spinnaker component sizing configuration for front50
+- `gate`: Manage and view Spinnaker component sizing configuration for gate
+- `igor`: Manage and view Spinnaker component sizing configuration for igor
+- `kayenta`: Manage and view Spinnaker component sizing configuration for kayenta
+- `monitoring-daemon`: Manage and view Spinnaker component sizing configuration for monitoring-daemon
+- `orca`: Manage and view Spinnaker component sizing configuration for orca
+- `orca-bootstrap`: Manage and view Spinnaker component sizing configuration for orca-bootstrap
+- `redis`: Manage and view Spinnaker component sizing configuration for redis
+- `redis-bootstrap`: Manage and view Spinnaker component sizing configuration for redis-bootstrap
+- `rosco`: Manage and view Spinnaker component sizing configuration for rosco
+- `vault-client`: Manage and view Spinnaker component sizing configuration for vault-client
+- `vault-server`: Manage and view Spinnaker component sizing configuration for vault-server
---
+
## hal config deploy component-sizing clouddriver
Manage and view Spinnaker component sizing configuration for clouddriver
#### Usage
+
```
hal config deploy component-sizing clouddriver [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `delete`: Delete the custom component sizings for service clouddriver
- * `edit`: Edit the component sizing for service clouddriver, such as the number of replicas and the resources limits.
+
+- `delete`: Delete the custom component sizings for service clouddriver
+- `edit`: Edit the component sizing for service clouddriver, such as the number of replicas and the resources limits.
---
+
## hal config deploy component-sizing clouddriver delete
Delete the custom component sizings for service clouddriver
#### Usage
+
```
hal config deploy component-sizing clouddriver delete [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config deploy component-sizing clouddriver edit
Edit the component sizing for service clouddriver, such as the number of replicas and the resources limits.
#### Usage
+
```
hal config deploy component-sizing clouddriver edit [parameters]
```
#### Parameters
- * `--container-limits-cpu`: Sets the cpu limit for the container running the spinnaker service. Example: 1.
- * `--container-limits-memory`: Sets the memory limit for the container running the spinnaker service. Example: 1Gi.
- * `--container-requests-cpu`: Sets the cpu request for the container running the spinnaker service. Example: 250m.
- * `--container-requests-memory`: Sets the memory request for the container running the spinnaker service. Example: 512Mi.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--pod-limits-cpu`: Sets the cpu limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1.
- * `--pod-limits-memory`: Sets the memory limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1Gi.
- * `--pod-requests-cpu`: Sets the cpu request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 250m.
- * `--pod-requests-memory`: Sets the memory request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 512Mi.
- * `--replicas`: (*Default*: `1`) Set the number of replicas (pods) to be created for this service.
+- `--container-limits-cpu`: Sets the cpu limit for the container running the spinnaker service. Example: 1.
+- `--container-limits-memory`: Sets the memory limit for the container running the spinnaker service. Example: 1Gi.
+- `--container-requests-cpu`: Sets the cpu request for the container running the spinnaker service. Example: 250m.
+- `--container-requests-memory`: Sets the memory request for the container running the spinnaker service. Example: 512Mi.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--pod-limits-cpu`: Sets the cpu limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1.
+- `--pod-limits-memory`: Sets the memory limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1Gi.
+- `--pod-requests-cpu`: Sets the cpu request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 250m.
+- `--pod-requests-memory`: Sets the memory request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 512Mi.
+- `--replicas`: (_Default_: `1`) Set the number of replicas (pods) to be created for this service.
---
+
## hal config deploy component-sizing clouddriver-bootstrap
Manage and view Spinnaker component sizing configuration for clouddriver-bootstrap
#### Usage
+
```
hal config deploy component-sizing clouddriver-bootstrap [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `delete`: Delete the custom component sizings for service clouddriver-bootstrap
- * `edit`: Edit the component sizing for service clouddriver-bootstrap, such as the number of replicas and the resources limits.
+
+- `delete`: Delete the custom component sizings for service clouddriver-bootstrap
+- `edit`: Edit the component sizing for service clouddriver-bootstrap, such as the number of replicas and the resources limits.
---
+
## hal config deploy component-sizing clouddriver-bootstrap delete
Delete the custom component sizings for service clouddriver-bootstrap
#### Usage
+
```
hal config deploy component-sizing clouddriver-bootstrap delete [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config deploy component-sizing clouddriver-bootstrap edit
Edit the component sizing for service clouddriver-bootstrap, such as the number of replicas and the resources limits.
#### Usage
+
```
hal config deploy component-sizing clouddriver-bootstrap edit [parameters]
```
#### Parameters
- * `--container-limits-cpu`: Sets the cpu limit for the container running the spinnaker service. Example: 1.
- * `--container-limits-memory`: Sets the memory limit for the container running the spinnaker service. Example: 1Gi.
- * `--container-requests-cpu`: Sets the cpu request for the container running the spinnaker service. Example: 250m.
- * `--container-requests-memory`: Sets the memory request for the container running the spinnaker service. Example: 512Mi.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--pod-limits-cpu`: Sets the cpu limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1.
- * `--pod-limits-memory`: Sets the memory limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1Gi.
- * `--pod-requests-cpu`: Sets the cpu request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 250m.
- * `--pod-requests-memory`: Sets the memory request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 512Mi.
- * `--replicas`: (*Default*: `1`) Set the number of replicas (pods) to be created for this service.
+- `--container-limits-cpu`: Sets the cpu limit for the container running the spinnaker service. Example: 1.
+- `--container-limits-memory`: Sets the memory limit for the container running the spinnaker service. Example: 1Gi.
+- `--container-requests-cpu`: Sets the cpu request for the container running the spinnaker service. Example: 250m.
+- `--container-requests-memory`: Sets the memory request for the container running the spinnaker service. Example: 512Mi.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--pod-limits-cpu`: Sets the cpu limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1.
+- `--pod-limits-memory`: Sets the memory limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1Gi.
+- `--pod-requests-cpu`: Sets the cpu request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 250m.
+- `--pod-requests-memory`: Sets the memory request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 512Mi.
+- `--replicas`: (_Default_: `1`) Set the number of replicas (pods) to be created for this service.
---
+
## hal config deploy component-sizing clouddriver-caching
Manage and view Spinnaker component sizing configuration for clouddriver-caching
#### Usage
+
```
hal config deploy component-sizing clouddriver-caching [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `delete`: Delete the custom component sizings for service clouddriver-caching
- * `edit`: Edit the component sizing for service clouddriver-caching, such as the number of replicas and the resources limits.
+
+- `delete`: Delete the custom component sizings for service clouddriver-caching
+- `edit`: Edit the component sizing for service clouddriver-caching, such as the number of replicas and the resources limits.
---
+
## hal config deploy component-sizing clouddriver-caching delete
Delete the custom component sizings for service clouddriver-caching
#### Usage
+
```
hal config deploy component-sizing clouddriver-caching delete [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config deploy component-sizing clouddriver-caching edit
Edit the component sizing for service clouddriver-caching, such as the number of replicas and the resources limits.
#### Usage
+
```
hal config deploy component-sizing clouddriver-caching edit [parameters]
```
#### Parameters
- * `--container-limits-cpu`: Sets the cpu limit for the container running the spinnaker service. Example: 1.
- * `--container-limits-memory`: Sets the memory limit for the container running the spinnaker service. Example: 1Gi.
- * `--container-requests-cpu`: Sets the cpu request for the container running the spinnaker service. Example: 250m.
- * `--container-requests-memory`: Sets the memory request for the container running the spinnaker service. Example: 512Mi.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--pod-limits-cpu`: Sets the cpu limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1.
- * `--pod-limits-memory`: Sets the memory limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1Gi.
- * `--pod-requests-cpu`: Sets the cpu request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 250m.
- * `--pod-requests-memory`: Sets the memory request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 512Mi.
- * `--replicas`: (*Default*: `1`) Set the number of replicas (pods) to be created for this service.
+- `--container-limits-cpu`: Sets the cpu limit for the container running the spinnaker service. Example: 1.
+- `--container-limits-memory`: Sets the memory limit for the container running the spinnaker service. Example: 1Gi.
+- `--container-requests-cpu`: Sets the cpu request for the container running the spinnaker service. Example: 250m.
+- `--container-requests-memory`: Sets the memory request for the container running the spinnaker service. Example: 512Mi.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--pod-limits-cpu`: Sets the cpu limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1.
+- `--pod-limits-memory`: Sets the memory limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1Gi.
+- `--pod-requests-cpu`: Sets the cpu request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 250m.
+- `--pod-requests-memory`: Sets the memory request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 512Mi.
+- `--replicas`: (_Default_: `1`) Set the number of replicas (pods) to be created for this service.
---
+
## hal config deploy component-sizing clouddriver-ro
Manage and view Spinnaker component sizing configuration for clouddriver-ro
#### Usage
+
```
hal config deploy component-sizing clouddriver-ro [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `delete`: Delete the custom component sizings for service clouddriver-ro
- * `edit`: Edit the component sizing for service clouddriver-ro, such as the number of replicas and the resources limits.
+
+- `delete`: Delete the custom component sizings for service clouddriver-ro
+- `edit`: Edit the component sizing for service clouddriver-ro, such as the number of replicas and the resources limits.
---
+
## hal config deploy component-sizing clouddriver-ro delete
Delete the custom component sizings for service clouddriver-ro
#### Usage
+
```
hal config deploy component-sizing clouddriver-ro delete [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config deploy component-sizing clouddriver-ro edit
Edit the component sizing for service clouddriver-ro, such as the number of replicas and the resources limits.
#### Usage
+
```
hal config deploy component-sizing clouddriver-ro edit [parameters]
```
#### Parameters
- * `--container-limits-cpu`: Sets the cpu limit for the container running the spinnaker service. Example: 1.
- * `--container-limits-memory`: Sets the memory limit for the container running the spinnaker service. Example: 1Gi.
- * `--container-requests-cpu`: Sets the cpu request for the container running the spinnaker service. Example: 250m.
- * `--container-requests-memory`: Sets the memory request for the container running the spinnaker service. Example: 512Mi.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--pod-limits-cpu`: Sets the cpu limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1.
- * `--pod-limits-memory`: Sets the memory limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1Gi.
- * `--pod-requests-cpu`: Sets the cpu request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 250m.
- * `--pod-requests-memory`: Sets the memory request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 512Mi.
- * `--replicas`: (*Default*: `1`) Set the number of replicas (pods) to be created for this service.
+- `--container-limits-cpu`: Sets the cpu limit for the container running the spinnaker service. Example: 1.
+- `--container-limits-memory`: Sets the memory limit for the container running the spinnaker service. Example: 1Gi.
+- `--container-requests-cpu`: Sets the cpu request for the container running the spinnaker service. Example: 250m.
+- `--container-requests-memory`: Sets the memory request for the container running the spinnaker service. Example: 512Mi.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--pod-limits-cpu`: Sets the cpu limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1.
+- `--pod-limits-memory`: Sets the memory limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1Gi.
+- `--pod-requests-cpu`: Sets the cpu request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 250m.
+- `--pod-requests-memory`: Sets the memory request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 512Mi.
+- `--replicas`: (_Default_: `1`) Set the number of replicas (pods) to be created for this service.
---
+
## hal config deploy component-sizing clouddriver-ro-deck
Manage and view Spinnaker component sizing configuration for clouddriver-ro-deck
#### Usage
+
```
hal config deploy component-sizing clouddriver-ro-deck [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `delete`: Delete the custom component sizings for service clouddriver-ro-deck
- * `edit`: Edit the component sizing for service clouddriver-ro-deck, such as the number of replicas and the resources limits.
+
+- `delete`: Delete the custom component sizings for service clouddriver-ro-deck
+- `edit`: Edit the component sizing for service clouddriver-ro-deck, such as the number of replicas and the resources limits.
---
+
## hal config deploy component-sizing clouddriver-ro-deck delete
Delete the custom component sizings for service clouddriver-ro-deck
#### Usage
+
```
hal config deploy component-sizing clouddriver-ro-deck delete [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config deploy component-sizing clouddriver-ro-deck edit
Edit the component sizing for service clouddriver-ro-deck, such as the number of replicas and the resources limits.
#### Usage
+
```
hal config deploy component-sizing clouddriver-ro-deck edit [parameters]
```
#### Parameters
- * `--container-limits-cpu`: Sets the cpu limit for the container running the spinnaker service. Example: 1.
- * `--container-limits-memory`: Sets the memory limit for the container running the spinnaker service. Example: 1Gi.
- * `--container-requests-cpu`: Sets the cpu request for the container running the spinnaker service. Example: 250m.
- * `--container-requests-memory`: Sets the memory request for the container running the spinnaker service. Example: 512Mi.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--pod-limits-cpu`: Sets the cpu limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1.
- * `--pod-limits-memory`: Sets the memory limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1Gi.
- * `--pod-requests-cpu`: Sets the cpu request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 250m.
- * `--pod-requests-memory`: Sets the memory request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 512Mi.
- * `--replicas`: (*Default*: `1`) Set the number of replicas (pods) to be created for this service.
+- `--container-limits-cpu`: Sets the cpu limit for the container running the spinnaker service. Example: 1.
+- `--container-limits-memory`: Sets the memory limit for the container running the spinnaker service. Example: 1Gi.
+- `--container-requests-cpu`: Sets the cpu request for the container running the spinnaker service. Example: 250m.
+- `--container-requests-memory`: Sets the memory request for the container running the spinnaker service. Example: 512Mi.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--pod-limits-cpu`: Sets the cpu limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1.
+- `--pod-limits-memory`: Sets the memory limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1Gi.
+- `--pod-requests-cpu`: Sets the cpu request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 250m.
+- `--pod-requests-memory`: Sets the memory request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 512Mi.
+- `--replicas`: (_Default_: `1`) Set the number of replicas (pods) to be created for this service.
---
+
## hal config deploy component-sizing clouddriver-rw
Manage and view Spinnaker component sizing configuration for clouddriver-rw
#### Usage
+
```
hal config deploy component-sizing clouddriver-rw [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `delete`: Delete the custom component sizings for service clouddriver-rw
- * `edit`: Edit the component sizing for service clouddriver-rw, such as the number of replicas and the resources limits.
+
+- `delete`: Delete the custom component sizings for service clouddriver-rw
+- `edit`: Edit the component sizing for service clouddriver-rw, such as the number of replicas and the resources limits.
---
+
## hal config deploy component-sizing clouddriver-rw delete
Delete the custom component sizings for service clouddriver-rw
#### Usage
+
```
hal config deploy component-sizing clouddriver-rw delete [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config deploy component-sizing clouddriver-rw edit
Edit the component sizing for service clouddriver-rw, such as the number of replicas and the resources limits.
#### Usage
+
```
hal config deploy component-sizing clouddriver-rw edit [parameters]
```
#### Parameters
- * `--container-limits-cpu`: Sets the cpu limit for the container running the spinnaker service. Example: 1.
- * `--container-limits-memory`: Sets the memory limit for the container running the spinnaker service. Example: 1Gi.
- * `--container-requests-cpu`: Sets the cpu request for the container running the spinnaker service. Example: 250m.
- * `--container-requests-memory`: Sets the memory request for the container running the spinnaker service. Example: 512Mi.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--pod-limits-cpu`: Sets the cpu limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1.
- * `--pod-limits-memory`: Sets the memory limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1Gi.
- * `--pod-requests-cpu`: Sets the cpu request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 250m.
- * `--pod-requests-memory`: Sets the memory request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 512Mi.
- * `--replicas`: (*Default*: `1`) Set the number of replicas (pods) to be created for this service.
+- `--container-limits-cpu`: Sets the cpu limit for the container running the spinnaker service. Example: 1.
+- `--container-limits-memory`: Sets the memory limit for the container running the spinnaker service. Example: 1Gi.
+- `--container-requests-cpu`: Sets the cpu request for the container running the spinnaker service. Example: 250m.
+- `--container-requests-memory`: Sets the memory request for the container running the spinnaker service. Example: 512Mi.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--pod-limits-cpu`: Sets the cpu limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1.
+- `--pod-limits-memory`: Sets the memory limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1Gi.
+- `--pod-requests-cpu`: Sets the cpu request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 250m.
+- `--pod-requests-memory`: Sets the memory request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 512Mi.
+- `--replicas`: (_Default_: `1`) Set the number of replicas (pods) to be created for this service.
---
+
## hal config deploy component-sizing consul-client
Manage and view Spinnaker component sizing configuration for consul-client
#### Usage
+
```
hal config deploy component-sizing consul-client [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `delete`: Delete the custom component sizings for service consul-client
- * `edit`: Edit the component sizing for service consul-client, such as the number of replicas and the resources limits.
+
+- `delete`: Delete the custom component sizings for service consul-client
+- `edit`: Edit the component sizing for service consul-client, such as the number of replicas and the resources limits.
---
+
## hal config deploy component-sizing consul-client delete
Delete the custom component sizings for service consul-client
#### Usage
+
```
hal config deploy component-sizing consul-client delete [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config deploy component-sizing consul-client edit
Edit the component sizing for service consul-client, such as the number of replicas and the resources limits.
#### Usage
+
```
hal config deploy component-sizing consul-client edit [parameters]
```
#### Parameters
- * `--container-limits-cpu`: Sets the cpu limit for the container running the spinnaker service. Example: 1.
- * `--container-limits-memory`: Sets the memory limit for the container running the spinnaker service. Example: 1Gi.
- * `--container-requests-cpu`: Sets the cpu request for the container running the spinnaker service. Example: 250m.
- * `--container-requests-memory`: Sets the memory request for the container running the spinnaker service. Example: 512Mi.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--pod-limits-cpu`: Sets the cpu limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1.
- * `--pod-limits-memory`: Sets the memory limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1Gi.
- * `--pod-requests-cpu`: Sets the cpu request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 250m.
- * `--pod-requests-memory`: Sets the memory request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 512Mi.
- * `--replicas`: (*Default*: `1`) Set the number of replicas (pods) to be created for this service.
+- `--container-limits-cpu`: Sets the cpu limit for the container running the spinnaker service. Example: 1.
+- `--container-limits-memory`: Sets the memory limit for the container running the spinnaker service. Example: 1Gi.
+- `--container-requests-cpu`: Sets the cpu request for the container running the spinnaker service. Example: 250m.
+- `--container-requests-memory`: Sets the memory request for the container running the spinnaker service. Example: 512Mi.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--pod-limits-cpu`: Sets the cpu limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1.
+- `--pod-limits-memory`: Sets the memory limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1Gi.
+- `--pod-requests-cpu`: Sets the cpu request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 250m.
+- `--pod-requests-memory`: Sets the memory request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 512Mi.
+- `--replicas`: (_Default_: `1`) Set the number of replicas (pods) to be created for this service.
---
+
## hal config deploy component-sizing consul-server
Manage and view Spinnaker component sizing configuration for consul-server
#### Usage
+
```
hal config deploy component-sizing consul-server [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `delete`: Delete the custom component sizings for service consul-server
- * `edit`: Edit the component sizing for service consul-server, such as the number of replicas and the resources limits.
+
+- `delete`: Delete the custom component sizings for service consul-server
+- `edit`: Edit the component sizing for service consul-server, such as the number of replicas and the resources limits.
---
+
## hal config deploy component-sizing consul-server delete
Delete the custom component sizings for service consul-server
#### Usage
+
```
hal config deploy component-sizing consul-server delete [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config deploy component-sizing consul-server edit
Edit the component sizing for service consul-server, such as the number of replicas and the resources limits.
#### Usage
+
```
hal config deploy component-sizing consul-server edit [parameters]
```
#### Parameters
- * `--container-limits-cpu`: Sets the cpu limit for the container running the spinnaker service. Example: 1.
- * `--container-limits-memory`: Sets the memory limit for the container running the spinnaker service. Example: 1Gi.
- * `--container-requests-cpu`: Sets the cpu request for the container running the spinnaker service. Example: 250m.
- * `--container-requests-memory`: Sets the memory request for the container running the spinnaker service. Example: 512Mi.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--pod-limits-cpu`: Sets the cpu limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1.
- * `--pod-limits-memory`: Sets the memory limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1Gi.
- * `--pod-requests-cpu`: Sets the cpu request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 250m.
- * `--pod-requests-memory`: Sets the memory request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 512Mi.
- * `--replicas`: (*Default*: `1`) Set the number of replicas (pods) to be created for this service.
+- `--container-limits-cpu`: Sets the cpu limit for the container running the spinnaker service. Example: 1.
+- `--container-limits-memory`: Sets the memory limit for the container running the spinnaker service. Example: 1Gi.
+- `--container-requests-cpu`: Sets the cpu request for the container running the spinnaker service. Example: 250m.
+- `--container-requests-memory`: Sets the memory request for the container running the spinnaker service. Example: 512Mi.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--pod-limits-cpu`: Sets the cpu limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1.
+- `--pod-limits-memory`: Sets the memory limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1Gi.
+- `--pod-requests-cpu`: Sets the cpu request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 250m.
+- `--pod-requests-memory`: Sets the memory request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 512Mi.
+- `--replicas`: (_Default_: `1`) Set the number of replicas (pods) to be created for this service.
---
+
## hal config deploy component-sizing deck
Manage and view Spinnaker component sizing configuration for deck
#### Usage
+
```
hal config deploy component-sizing deck [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `delete`: Delete the custom component sizings for service deck
- * `edit`: Edit the component sizing for service deck, such as the number of replicas and the resources limits.
+
+- `delete`: Delete the custom component sizings for service deck
+- `edit`: Edit the component sizing for service deck, such as the number of replicas and the resources limits.
---
+
## hal config deploy component-sizing deck delete
Delete the custom component sizings for service deck
#### Usage
+
```
hal config deploy component-sizing deck delete [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config deploy component-sizing deck edit
Edit the component sizing for service deck, such as the number of replicas and the resources limits.
#### Usage
+
```
hal config deploy component-sizing deck edit [parameters]
```
#### Parameters
- * `--container-limits-cpu`: Sets the cpu limit for the container running the spinnaker service. Example: 1.
- * `--container-limits-memory`: Sets the memory limit for the container running the spinnaker service. Example: 1Gi.
- * `--container-requests-cpu`: Sets the cpu request for the container running the spinnaker service. Example: 250m.
- * `--container-requests-memory`: Sets the memory request for the container running the spinnaker service. Example: 512Mi.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--pod-limits-cpu`: Sets the cpu limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1.
- * `--pod-limits-memory`: Sets the memory limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1Gi.
- * `--pod-requests-cpu`: Sets the cpu request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 250m.
- * `--pod-requests-memory`: Sets the memory request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 512Mi.
- * `--replicas`: (*Default*: `1`) Set the number of replicas (pods) to be created for this service.
+- `--container-limits-cpu`: Sets the cpu limit for the container running the spinnaker service. Example: 1.
+- `--container-limits-memory`: Sets the memory limit for the container running the spinnaker service. Example: 1Gi.
+- `--container-requests-cpu`: Sets the cpu request for the container running the spinnaker service. Example: 250m.
+- `--container-requests-memory`: Sets the memory request for the container running the spinnaker service. Example: 512Mi.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--pod-limits-cpu`: Sets the cpu limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1.
+- `--pod-limits-memory`: Sets the memory limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1Gi.
+- `--pod-requests-cpu`: Sets the cpu request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 250m.
+- `--pod-requests-memory`: Sets the memory request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 512Mi.
+- `--replicas`: (_Default_: `1`) Set the number of replicas (pods) to be created for this service.
---
+
## hal config deploy component-sizing echo
Manage and view Spinnaker component sizing configuration for echo
#### Usage
+
```
hal config deploy component-sizing echo [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `delete`: Delete the custom component sizings for service echo
- * `edit`: Edit the component sizing for service echo, such as the number of replicas and the resources limits.
+
+- `delete`: Delete the custom component sizings for service echo
+- `edit`: Edit the component sizing for service echo, such as the number of replicas and the resources limits.
---
+
## hal config deploy component-sizing echo delete
Delete the custom component sizings for service echo
#### Usage
+
```
hal config deploy component-sizing echo delete [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config deploy component-sizing echo edit
Edit the component sizing for service echo, such as the number of replicas and the resources limits.
#### Usage
+
```
hal config deploy component-sizing echo edit [parameters]
```
#### Parameters
- * `--container-limits-cpu`: Sets the cpu limit for the container running the spinnaker service. Example: 1.
- * `--container-limits-memory`: Sets the memory limit for the container running the spinnaker service. Example: 1Gi.
- * `--container-requests-cpu`: Sets the cpu request for the container running the spinnaker service. Example: 250m.
- * `--container-requests-memory`: Sets the memory request for the container running the spinnaker service. Example: 512Mi.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--pod-limits-cpu`: Sets the cpu limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1.
- * `--pod-limits-memory`: Sets the memory limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1Gi.
- * `--pod-requests-cpu`: Sets the cpu request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 250m.
- * `--pod-requests-memory`: Sets the memory request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 512Mi.
- * `--replicas`: (*Default*: `1`) Set the number of replicas (pods) to be created for this service.
+- `--container-limits-cpu`: Sets the cpu limit for the container running the spinnaker service. Example: 1.
+- `--container-limits-memory`: Sets the memory limit for the container running the spinnaker service. Example: 1Gi.
+- `--container-requests-cpu`: Sets the cpu request for the container running the spinnaker service. Example: 250m.
+- `--container-requests-memory`: Sets the memory request for the container running the spinnaker service. Example: 512Mi.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--pod-limits-cpu`: Sets the cpu limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1.
+- `--pod-limits-memory`: Sets the memory limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1Gi.
+- `--pod-requests-cpu`: Sets the cpu request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 250m.
+- `--pod-requests-memory`: Sets the memory request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 512Mi.
+- `--replicas`: (_Default_: `1`) Set the number of replicas (pods) to be created for this service.
---
+
## hal config deploy component-sizing echo-scheduler
Manage and view Spinnaker component sizing configuration for echo-scheduler
#### Usage
+
```
hal config deploy component-sizing echo-scheduler [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `delete`: Delete the custom component sizings for service echo-scheduler
- * `edit`: Edit the component sizing for service echo-scheduler, such as the number of replicas and the resources limits.
+
+- `delete`: Delete the custom component sizings for service echo-scheduler
+- `edit`: Edit the component sizing for service echo-scheduler, such as the number of replicas and the resources limits.
---
+
## hal config deploy component-sizing echo-scheduler delete
Delete the custom component sizings for service echo-scheduler
#### Usage
+
```
hal config deploy component-sizing echo-scheduler delete [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config deploy component-sizing echo-scheduler edit
Edit the component sizing for service echo-scheduler, such as the number of replicas and the resources limits.
#### Usage
+
```
hal config deploy component-sizing echo-scheduler edit [parameters]
```
#### Parameters
- * `--container-limits-cpu`: Sets the cpu limit for the container running the spinnaker service. Example: 1.
- * `--container-limits-memory`: Sets the memory limit for the container running the spinnaker service. Example: 1Gi.
- * `--container-requests-cpu`: Sets the cpu request for the container running the spinnaker service. Example: 250m.
- * `--container-requests-memory`: Sets the memory request for the container running the spinnaker service. Example: 512Mi.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--pod-limits-cpu`: Sets the cpu limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1.
- * `--pod-limits-memory`: Sets the memory limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1Gi.
- * `--pod-requests-cpu`: Sets the cpu request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 250m.
- * `--pod-requests-memory`: Sets the memory request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 512Mi.
- * `--replicas`: (*Default*: `1`) Set the number of replicas (pods) to be created for this service.
+- `--container-limits-cpu`: Sets the cpu limit for the container running the spinnaker service. Example: 1.
+- `--container-limits-memory`: Sets the memory limit for the container running the spinnaker service. Example: 1Gi.
+- `--container-requests-cpu`: Sets the cpu request for the container running the spinnaker service. Example: 250m.
+- `--container-requests-memory`: Sets the memory request for the container running the spinnaker service. Example: 512Mi.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--pod-limits-cpu`: Sets the cpu limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1.
+- `--pod-limits-memory`: Sets the memory limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1Gi.
+- `--pod-requests-cpu`: Sets the cpu request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 250m.
+- `--pod-requests-memory`: Sets the memory request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 512Mi.
+- `--replicas`: (_Default_: `1`) Set the number of replicas (pods) to be created for this service.
---
+
## hal config deploy component-sizing echo-worker
Manage and view Spinnaker component sizing configuration for echo-worker
#### Usage
+
```
hal config deploy component-sizing echo-worker [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `delete`: Delete the custom component sizings for service echo-worker
- * `edit`: Edit the component sizing for service echo-worker, such as the number of replicas and the resources limits.
+
+- `delete`: Delete the custom component sizings for service echo-worker
+- `edit`: Edit the component sizing for service echo-worker, such as the number of replicas and the resources limits.
---
+
## hal config deploy component-sizing echo-worker delete
Delete the custom component sizings for service echo-worker
#### Usage
+
```
hal config deploy component-sizing echo-worker delete [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config deploy component-sizing echo-worker edit
Edit the component sizing for service echo-worker, such as the number of replicas and the resources limits.
#### Usage
+
```
hal config deploy component-sizing echo-worker edit [parameters]
```
#### Parameters
- * `--container-limits-cpu`: Sets the cpu limit for the container running the spinnaker service. Example: 1.
- * `--container-limits-memory`: Sets the memory limit for the container running the spinnaker service. Example: 1Gi.
- * `--container-requests-cpu`: Sets the cpu request for the container running the spinnaker service. Example: 250m.
- * `--container-requests-memory`: Sets the memory request for the container running the spinnaker service. Example: 512Mi.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--pod-limits-cpu`: Sets the cpu limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1.
- * `--pod-limits-memory`: Sets the memory limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1Gi.
- * `--pod-requests-cpu`: Sets the cpu request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 250m.
- * `--pod-requests-memory`: Sets the memory request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 512Mi.
- * `--replicas`: (*Default*: `1`) Set the number of replicas (pods) to be created for this service.
+- `--container-limits-cpu`: Sets the cpu limit for the container running the spinnaker service. Example: 1.
+- `--container-limits-memory`: Sets the memory limit for the container running the spinnaker service. Example: 1Gi.
+- `--container-requests-cpu`: Sets the cpu request for the container running the spinnaker service. Example: 250m.
+- `--container-requests-memory`: Sets the memory request for the container running the spinnaker service. Example: 512Mi.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--pod-limits-cpu`: Sets the cpu limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1.
+- `--pod-limits-memory`: Sets the memory limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1Gi.
+- `--pod-requests-cpu`: Sets the cpu request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 250m.
+- `--pod-requests-memory`: Sets the memory request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 512Mi.
+- `--replicas`: (_Default_: `1`) Set the number of replicas (pods) to be created for this service.
---
+
## hal config deploy component-sizing fiat
Manage and view Spinnaker component sizing configuration for fiat
#### Usage
+
```
hal config deploy component-sizing fiat [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `delete`: Delete the custom component sizings for service fiat
- * `edit`: Edit the component sizing for service fiat, such as the number of replicas and the resources limits.
+
+- `delete`: Delete the custom component sizings for service fiat
+- `edit`: Edit the component sizing for service fiat, such as the number of replicas and the resources limits.
---
+
## hal config deploy component-sizing fiat delete
Delete the custom component sizings for service fiat
#### Usage
+
```
hal config deploy component-sizing fiat delete [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config deploy component-sizing fiat edit
Edit the component sizing for service fiat, such as the number of replicas and the resources limits.
#### Usage
+
```
hal config deploy component-sizing fiat edit [parameters]
```
#### Parameters
- * `--container-limits-cpu`: Sets the cpu limit for the container running the spinnaker service. Example: 1.
- * `--container-limits-memory`: Sets the memory limit for the container running the spinnaker service. Example: 1Gi.
- * `--container-requests-cpu`: Sets the cpu request for the container running the spinnaker service. Example: 250m.
- * `--container-requests-memory`: Sets the memory request for the container running the spinnaker service. Example: 512Mi.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--pod-limits-cpu`: Sets the cpu limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1.
- * `--pod-limits-memory`: Sets the memory limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1Gi.
- * `--pod-requests-cpu`: Sets the cpu request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 250m.
- * `--pod-requests-memory`: Sets the memory request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 512Mi.
- * `--replicas`: (*Default*: `1`) Set the number of replicas (pods) to be created for this service.
+- `--container-limits-cpu`: Sets the cpu limit for the container running the spinnaker service. Example: 1.
+- `--container-limits-memory`: Sets the memory limit for the container running the spinnaker service. Example: 1Gi.
+- `--container-requests-cpu`: Sets the cpu request for the container running the spinnaker service. Example: 250m.
+- `--container-requests-memory`: Sets the memory request for the container running the spinnaker service. Example: 512Mi.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--pod-limits-cpu`: Sets the cpu limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1.
+- `--pod-limits-memory`: Sets the memory limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1Gi.
+- `--pod-requests-cpu`: Sets the cpu request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 250m.
+- `--pod-requests-memory`: Sets the memory request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 512Mi.
+- `--replicas`: (_Default_: `1`) Set the number of replicas (pods) to be created for this service.
---
+
## hal config deploy component-sizing front50
Manage and view Spinnaker component sizing configuration for front50
#### Usage
+
```
hal config deploy component-sizing front50 [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `delete`: Delete the custom component sizings for service front50
- * `edit`: Edit the component sizing for service front50, such as the number of replicas and the resources limits.
+
+- `delete`: Delete the custom component sizings for service front50
+- `edit`: Edit the component sizing for service front50, such as the number of replicas and the resources limits.
---
+
## hal config deploy component-sizing front50 delete
Delete the custom component sizings for service front50
#### Usage
+
```
hal config deploy component-sizing front50 delete [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config deploy component-sizing front50 edit
Edit the component sizing for service front50, such as the number of replicas and the resources limits.
#### Usage
+
```
hal config deploy component-sizing front50 edit [parameters]
```
#### Parameters
- * `--container-limits-cpu`: Sets the cpu limit for the container running the spinnaker service. Example: 1.
- * `--container-limits-memory`: Sets the memory limit for the container running the spinnaker service. Example: 1Gi.
- * `--container-requests-cpu`: Sets the cpu request for the container running the spinnaker service. Example: 250m.
- * `--container-requests-memory`: Sets the memory request for the container running the spinnaker service. Example: 512Mi.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--pod-limits-cpu`: Sets the cpu limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1.
- * `--pod-limits-memory`: Sets the memory limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1Gi.
- * `--pod-requests-cpu`: Sets the cpu request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 250m.
- * `--pod-requests-memory`: Sets the memory request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 512Mi.
- * `--replicas`: (*Default*: `1`) Set the number of replicas (pods) to be created for this service.
+- `--container-limits-cpu`: Sets the cpu limit for the container running the spinnaker service. Example: 1.
+- `--container-limits-memory`: Sets the memory limit for the container running the spinnaker service. Example: 1Gi.
+- `--container-requests-cpu`: Sets the cpu request for the container running the spinnaker service. Example: 250m.
+- `--container-requests-memory`: Sets the memory request for the container running the spinnaker service. Example: 512Mi.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--pod-limits-cpu`: Sets the cpu limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1.
+- `--pod-limits-memory`: Sets the memory limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1Gi.
+- `--pod-requests-cpu`: Sets the cpu request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 250m.
+- `--pod-requests-memory`: Sets the memory request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 512Mi.
+- `--replicas`: (_Default_: `1`) Set the number of replicas (pods) to be created for this service.
---
+
## hal config deploy component-sizing gate
Manage and view Spinnaker component sizing configuration for gate
#### Usage
+
```
hal config deploy component-sizing gate [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `delete`: Delete the custom component sizings for service gate
- * `edit`: Edit the component sizing for service gate, such as the number of replicas and the resources limits.
+
+- `delete`: Delete the custom component sizings for service gate
+- `edit`: Edit the component sizing for service gate, such as the number of replicas and the resources limits.
---
+
## hal config deploy component-sizing gate delete
Delete the custom component sizings for service gate
#### Usage
+
```
hal config deploy component-sizing gate delete [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config deploy component-sizing gate edit
Edit the component sizing for service gate, such as the number of replicas and the resources limits.
#### Usage
+
```
hal config deploy component-sizing gate edit [parameters]
```
#### Parameters
- * `--container-limits-cpu`: Sets the cpu limit for the container running the spinnaker service. Example: 1.
- * `--container-limits-memory`: Sets the memory limit for the container running the spinnaker service. Example: 1Gi.
- * `--container-requests-cpu`: Sets the cpu request for the container running the spinnaker service. Example: 250m.
- * `--container-requests-memory`: Sets the memory request for the container running the spinnaker service. Example: 512Mi.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--pod-limits-cpu`: Sets the cpu limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1.
- * `--pod-limits-memory`: Sets the memory limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1Gi.
- * `--pod-requests-cpu`: Sets the cpu request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 250m.
- * `--pod-requests-memory`: Sets the memory request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 512Mi.
- * `--replicas`: (*Default*: `1`) Set the number of replicas (pods) to be created for this service.
+- `--container-limits-cpu`: Sets the cpu limit for the container running the spinnaker service. Example: 1.
+- `--container-limits-memory`: Sets the memory limit for the container running the spinnaker service. Example: 1Gi.
+- `--container-requests-cpu`: Sets the cpu request for the container running the spinnaker service. Example: 250m.
+- `--container-requests-memory`: Sets the memory request for the container running the spinnaker service. Example: 512Mi.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--pod-limits-cpu`: Sets the cpu limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1.
+- `--pod-limits-memory`: Sets the memory limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1Gi.
+- `--pod-requests-cpu`: Sets the cpu request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 250m.
+- `--pod-requests-memory`: Sets the memory request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 512Mi.
+- `--replicas`: (_Default_: `1`) Set the number of replicas (pods) to be created for this service.
---
+
## hal config deploy component-sizing igor
Manage and view Spinnaker component sizing configuration for igor
#### Usage
+
```
hal config deploy component-sizing igor [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `delete`: Delete the custom component sizings for service igor
- * `edit`: Edit the component sizing for service igor, such as the number of replicas and the resources limits.
+
+- `delete`: Delete the custom component sizings for service igor
+- `edit`: Edit the component sizing for service igor, such as the number of replicas and the resources limits.
---
+
## hal config deploy component-sizing igor delete
Delete the custom component sizings for service igor
#### Usage
+
```
hal config deploy component-sizing igor delete [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config deploy component-sizing igor edit
Edit the component sizing for service igor, such as the number of replicas and the resources limits.
#### Usage
+
```
hal config deploy component-sizing igor edit [parameters]
```
#### Parameters
- * `--container-limits-cpu`: Sets the cpu limit for the container running the spinnaker service. Example: 1.
- * `--container-limits-memory`: Sets the memory limit for the container running the spinnaker service. Example: 1Gi.
- * `--container-requests-cpu`: Sets the cpu request for the container running the spinnaker service. Example: 250m.
- * `--container-requests-memory`: Sets the memory request for the container running the spinnaker service. Example: 512Mi.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--pod-limits-cpu`: Sets the cpu limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1.
- * `--pod-limits-memory`: Sets the memory limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1Gi.
- * `--pod-requests-cpu`: Sets the cpu request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 250m.
- * `--pod-requests-memory`: Sets the memory request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 512Mi.
- * `--replicas`: (*Default*: `1`) Set the number of replicas (pods) to be created for this service.
+- `--container-limits-cpu`: Sets the cpu limit for the container running the spinnaker service. Example: 1.
+- `--container-limits-memory`: Sets the memory limit for the container running the spinnaker service. Example: 1Gi.
+- `--container-requests-cpu`: Sets the cpu request for the container running the spinnaker service. Example: 250m.
+- `--container-requests-memory`: Sets the memory request for the container running the spinnaker service. Example: 512Mi.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--pod-limits-cpu`: Sets the cpu limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1.
+- `--pod-limits-memory`: Sets the memory limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1Gi.
+- `--pod-requests-cpu`: Sets the cpu request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 250m.
+- `--pod-requests-memory`: Sets the memory request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 512Mi.
+- `--replicas`: (_Default_: `1`) Set the number of replicas (pods) to be created for this service.
---
+
## hal config deploy component-sizing kayenta
Manage and view Spinnaker component sizing configuration for kayenta
#### Usage
+
```
hal config deploy component-sizing kayenta [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `delete`: Delete the custom component sizings for service kayenta
- * `edit`: Edit the component sizing for service kayenta, such as the number of replicas and the resources limits.
+
+- `delete`: Delete the custom component sizings for service kayenta
+- `edit`: Edit the component sizing for service kayenta, such as the number of replicas and the resources limits.
---
+
## hal config deploy component-sizing kayenta delete
Delete the custom component sizings for service kayenta
#### Usage
+
```
hal config deploy component-sizing kayenta delete [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config deploy component-sizing kayenta edit
Edit the component sizing for service kayenta, such as the number of replicas and the resources limits.
#### Usage
+
```
hal config deploy component-sizing kayenta edit [parameters]
```
#### Parameters
- * `--container-limits-cpu`: Sets the cpu limit for the container running the spinnaker service. Example: 1.
- * `--container-limits-memory`: Sets the memory limit for the container running the spinnaker service. Example: 1Gi.
- * `--container-requests-cpu`: Sets the cpu request for the container running the spinnaker service. Example: 250m.
- * `--container-requests-memory`: Sets the memory request for the container running the spinnaker service. Example: 512Mi.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--pod-limits-cpu`: Sets the cpu limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1.
- * `--pod-limits-memory`: Sets the memory limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1Gi.
- * `--pod-requests-cpu`: Sets the cpu request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 250m.
- * `--pod-requests-memory`: Sets the memory request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 512Mi.
- * `--replicas`: (*Default*: `1`) Set the number of replicas (pods) to be created for this service.
+- `--container-limits-cpu`: Sets the cpu limit for the container running the spinnaker service. Example: 1.
+- `--container-limits-memory`: Sets the memory limit for the container running the spinnaker service. Example: 1Gi.
+- `--container-requests-cpu`: Sets the cpu request for the container running the spinnaker service. Example: 250m.
+- `--container-requests-memory`: Sets the memory request for the container running the spinnaker service. Example: 512Mi.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--pod-limits-cpu`: Sets the cpu limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1.
+- `--pod-limits-memory`: Sets the memory limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1Gi.
+- `--pod-requests-cpu`: Sets the cpu request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 250m.
+- `--pod-requests-memory`: Sets the memory request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 512Mi.
+- `--replicas`: (_Default_: `1`) Set the number of replicas (pods) to be created for this service.
---
+
## hal config deploy component-sizing monitoring-daemon
Manage and view Spinnaker component sizing configuration for monitoring-daemon
#### Usage
+
```
hal config deploy component-sizing monitoring-daemon [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `delete`: Delete the custom component sizings for service monitoring-daemon
- * `edit`: Edit the component sizing for service monitoring-daemon, such as the number of replicas and the resources limits.
+
+- `delete`: Delete the custom component sizings for service monitoring-daemon
+- `edit`: Edit the component sizing for service monitoring-daemon, such as the number of replicas and the resources limits.
---
+
## hal config deploy component-sizing monitoring-daemon delete
Delete the custom component sizings for service monitoring-daemon
#### Usage
+
```
hal config deploy component-sizing monitoring-daemon delete [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config deploy component-sizing monitoring-daemon edit
Edit the component sizing for service monitoring-daemon, such as the number of replicas and the resources limits.
#### Usage
+
```
hal config deploy component-sizing monitoring-daemon edit [parameters]
```
#### Parameters
- * `--container-limits-cpu`: Sets the cpu limit for the container running the spinnaker service. Example: 1.
- * `--container-limits-memory`: Sets the memory limit for the container running the spinnaker service. Example: 1Gi.
- * `--container-requests-cpu`: Sets the cpu request for the container running the spinnaker service. Example: 250m.
- * `--container-requests-memory`: Sets the memory request for the container running the spinnaker service. Example: 512Mi.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--pod-limits-cpu`: Sets the cpu limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1.
- * `--pod-limits-memory`: Sets the memory limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1Gi.
- * `--pod-requests-cpu`: Sets the cpu request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 250m.
- * `--pod-requests-memory`: Sets the memory request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 512Mi.
- * `--replicas`: (*Default*: `1`) Set the number of replicas (pods) to be created for this service.
+- `--container-limits-cpu`: Sets the cpu limit for the container running the spinnaker service. Example: 1.
+- `--container-limits-memory`: Sets the memory limit for the container running the spinnaker service. Example: 1Gi.
+- `--container-requests-cpu`: Sets the cpu request for the container running the spinnaker service. Example: 250m.
+- `--container-requests-memory`: Sets the memory request for the container running the spinnaker service. Example: 512Mi.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--pod-limits-cpu`: Sets the cpu limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1.
+- `--pod-limits-memory`: Sets the memory limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1Gi.
+- `--pod-requests-cpu`: Sets the cpu request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 250m.
+- `--pod-requests-memory`: Sets the memory request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 512Mi.
+- `--replicas`: (_Default_: `1`) Set the number of replicas (pods) to be created for this service.
---
+
## hal config deploy component-sizing orca
Manage and view Spinnaker component sizing configuration for orca
#### Usage
+
```
hal config deploy component-sizing orca [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `delete`: Delete the custom component sizings for service orca
- * `edit`: Edit the component sizing for service orca, such as the number of replicas and the resources limits.
+
+- `delete`: Delete the custom component sizings for service orca
+- `edit`: Edit the component sizing for service orca, such as the number of replicas and the resources limits.
---
+
## hal config deploy component-sizing orca delete
Delete the custom component sizings for service orca
#### Usage
+
```
hal config deploy component-sizing orca delete [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config deploy component-sizing orca edit
Edit the component sizing for service orca, such as the number of replicas and the resources limits.
#### Usage
+
```
hal config deploy component-sizing orca edit [parameters]
```
#### Parameters
- * `--container-limits-cpu`: Sets the cpu limit for the container running the spinnaker service. Example: 1.
- * `--container-limits-memory`: Sets the memory limit for the container running the spinnaker service. Example: 1Gi.
- * `--container-requests-cpu`: Sets the cpu request for the container running the spinnaker service. Example: 250m.
- * `--container-requests-memory`: Sets the memory request for the container running the spinnaker service. Example: 512Mi.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--pod-limits-cpu`: Sets the cpu limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1.
- * `--pod-limits-memory`: Sets the memory limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1Gi.
- * `--pod-requests-cpu`: Sets the cpu request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 250m.
- * `--pod-requests-memory`: Sets the memory request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 512Mi.
- * `--replicas`: (*Default*: `1`) Set the number of replicas (pods) to be created for this service.
+- `--container-limits-cpu`: Sets the cpu limit for the container running the spinnaker service. Example: 1.
+- `--container-limits-memory`: Sets the memory limit for the container running the spinnaker service. Example: 1Gi.
+- `--container-requests-cpu`: Sets the cpu request for the container running the spinnaker service. Example: 250m.
+- `--container-requests-memory`: Sets the memory request for the container running the spinnaker service. Example: 512Mi.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--pod-limits-cpu`: Sets the cpu limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1.
+- `--pod-limits-memory`: Sets the memory limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1Gi.
+- `--pod-requests-cpu`: Sets the cpu request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 250m.
+- `--pod-requests-memory`: Sets the memory request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 512Mi.
+- `--replicas`: (_Default_: `1`) Set the number of replicas (pods) to be created for this service.
---
+
## hal config deploy component-sizing orca-bootstrap
Manage and view Spinnaker component sizing configuration for orca-bootstrap
#### Usage
+
```
hal config deploy component-sizing orca-bootstrap [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `delete`: Delete the custom component sizings for service orca-bootstrap
- * `edit`: Edit the component sizing for service orca-bootstrap, such as the number of replicas and the resources limits.
+
+- `delete`: Delete the custom component sizings for service orca-bootstrap
+- `edit`: Edit the component sizing for service orca-bootstrap, such as the number of replicas and the resources limits.
---
+
## hal config deploy component-sizing orca-bootstrap delete
Delete the custom component sizings for service orca-bootstrap
#### Usage
+
```
hal config deploy component-sizing orca-bootstrap delete [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config deploy component-sizing orca-bootstrap edit
Edit the component sizing for service orca-bootstrap, such as the number of replicas and the resources limits.
#### Usage
+
```
hal config deploy component-sizing orca-bootstrap edit [parameters]
```
#### Parameters
- * `--container-limits-cpu`: Sets the cpu limit for the container running the spinnaker service. Example: 1.
- * `--container-limits-memory`: Sets the memory limit for the container running the spinnaker service. Example: 1Gi.
- * `--container-requests-cpu`: Sets the cpu request for the container running the spinnaker service. Example: 250m.
- * `--container-requests-memory`: Sets the memory request for the container running the spinnaker service. Example: 512Mi.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--pod-limits-cpu`: Sets the cpu limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1.
- * `--pod-limits-memory`: Sets the memory limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1Gi.
- * `--pod-requests-cpu`: Sets the cpu request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 250m.
- * `--pod-requests-memory`: Sets the memory request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 512Mi.
- * `--replicas`: (*Default*: `1`) Set the number of replicas (pods) to be created for this service.
+- `--container-limits-cpu`: Sets the cpu limit for the container running the spinnaker service. Example: 1.
+- `--container-limits-memory`: Sets the memory limit for the container running the spinnaker service. Example: 1Gi.
+- `--container-requests-cpu`: Sets the cpu request for the container running the spinnaker service. Example: 250m.
+- `--container-requests-memory`: Sets the memory request for the container running the spinnaker service. Example: 512Mi.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--pod-limits-cpu`: Sets the cpu limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1.
+- `--pod-limits-memory`: Sets the memory limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1Gi.
+- `--pod-requests-cpu`: Sets the cpu request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 250m.
+- `--pod-requests-memory`: Sets the memory request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 512Mi.
+- `--replicas`: (_Default_: `1`) Set the number of replicas (pods) to be created for this service.
---
+
## hal config deploy component-sizing redis
Manage and view Spinnaker component sizing configuration for redis
#### Usage
+
```
hal config deploy component-sizing redis [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `delete`: Delete the custom component sizings for service redis
- * `edit`: Edit the component sizing for service redis, such as the number of replicas and the resources limits.
+
+- `delete`: Delete the custom component sizings for service redis
+- `edit`: Edit the component sizing for service redis, such as the number of replicas and the resources limits.
---
+
## hal config deploy component-sizing redis delete
Delete the custom component sizings for service redis
#### Usage
+
```
hal config deploy component-sizing redis delete [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config deploy component-sizing redis edit
Edit the component sizing for service redis, such as the number of replicas and the resources limits.
#### Usage
+
```
hal config deploy component-sizing redis edit [parameters]
```
#### Parameters
- * `--container-limits-cpu`: Sets the cpu limit for the container running the spinnaker service. Example: 1.
- * `--container-limits-memory`: Sets the memory limit for the container running the spinnaker service. Example: 1Gi.
- * `--container-requests-cpu`: Sets the cpu request for the container running the spinnaker service. Example: 250m.
- * `--container-requests-memory`: Sets the memory request for the container running the spinnaker service. Example: 512Mi.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--pod-limits-cpu`: Sets the cpu limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1.
- * `--pod-limits-memory`: Sets the memory limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1Gi.
- * `--pod-requests-cpu`: Sets the cpu request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 250m.
- * `--pod-requests-memory`: Sets the memory request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 512Mi.
- * `--replicas`: (*Default*: `1`) Set the number of replicas (pods) to be created for this service.
+- `--container-limits-cpu`: Sets the cpu limit for the container running the spinnaker service. Example: 1.
+- `--container-limits-memory`: Sets the memory limit for the container running the spinnaker service. Example: 1Gi.
+- `--container-requests-cpu`: Sets the cpu request for the container running the spinnaker service. Example: 250m.
+- `--container-requests-memory`: Sets the memory request for the container running the spinnaker service. Example: 512Mi.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--pod-limits-cpu`: Sets the cpu limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1.
+- `--pod-limits-memory`: Sets the memory limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1Gi.
+- `--pod-requests-cpu`: Sets the cpu request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 250m.
+- `--pod-requests-memory`: Sets the memory request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 512Mi.
+- `--replicas`: (_Default_: `1`) Set the number of replicas (pods) to be created for this service.
---
+
## hal config deploy component-sizing redis-bootstrap
Manage and view Spinnaker component sizing configuration for redis-bootstrap
#### Usage
+
```
hal config deploy component-sizing redis-bootstrap [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `delete`: Delete the custom component sizings for service redis-bootstrap
- * `edit`: Edit the component sizing for service redis-bootstrap, such as the number of replicas and the resources limits.
+
+- `delete`: Delete the custom component sizings for service redis-bootstrap
+- `edit`: Edit the component sizing for service redis-bootstrap, such as the number of replicas and the resources limits.
---
+
## hal config deploy component-sizing redis-bootstrap delete
Delete the custom component sizings for service redis-bootstrap
#### Usage
+
```
hal config deploy component-sizing redis-bootstrap delete [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config deploy component-sizing redis-bootstrap edit
Edit the component sizing for service redis-bootstrap, such as the number of replicas and the resources limits.
#### Usage
+
```
hal config deploy component-sizing redis-bootstrap edit [parameters]
```
#### Parameters
- * `--container-limits-cpu`: Sets the cpu limit for the container running the spinnaker service. Example: 1.
- * `--container-limits-memory`: Sets the memory limit for the container running the spinnaker service. Example: 1Gi.
- * `--container-requests-cpu`: Sets the cpu request for the container running the spinnaker service. Example: 250m.
- * `--container-requests-memory`: Sets the memory request for the container running the spinnaker service. Example: 512Mi.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--pod-limits-cpu`: Sets the cpu limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1.
- * `--pod-limits-memory`: Sets the memory limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1Gi.
- * `--pod-requests-cpu`: Sets the cpu request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 250m.
- * `--pod-requests-memory`: Sets the memory request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 512Mi.
- * `--replicas`: (*Default*: `1`) Set the number of replicas (pods) to be created for this service.
+- `--container-limits-cpu`: Sets the cpu limit for the container running the spinnaker service. Example: 1.
+- `--container-limits-memory`: Sets the memory limit for the container running the spinnaker service. Example: 1Gi.
+- `--container-requests-cpu`: Sets the cpu request for the container running the spinnaker service. Example: 250m.
+- `--container-requests-memory`: Sets the memory request for the container running the spinnaker service. Example: 512Mi.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--pod-limits-cpu`: Sets the cpu limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1.
+- `--pod-limits-memory`: Sets the memory limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1Gi.
+- `--pod-requests-cpu`: Sets the cpu request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 250m.
+- `--pod-requests-memory`: Sets the memory request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 512Mi.
+- `--replicas`: (_Default_: `1`) Set the number of replicas (pods) to be created for this service.
---
+
## hal config deploy component-sizing rosco
Manage and view Spinnaker component sizing configuration for rosco
#### Usage
+
```
hal config deploy component-sizing rosco [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `delete`: Delete the custom component sizings for service rosco
- * `edit`: Edit the component sizing for service rosco, such as the number of replicas and the resources limits.
+
+- `delete`: Delete the custom component sizings for service rosco
+- `edit`: Edit the component sizing for service rosco, such as the number of replicas and the resources limits.
---
+
## hal config deploy component-sizing rosco delete
Delete the custom component sizings for service rosco
#### Usage
+
```
hal config deploy component-sizing rosco delete [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config deploy component-sizing rosco edit
Edit the component sizing for service rosco, such as the number of replicas and the resources limits.
#### Usage
+
```
hal config deploy component-sizing rosco edit [parameters]
```
#### Parameters
- * `--container-limits-cpu`: Sets the cpu limit for the container running the spinnaker service. Example: 1.
- * `--container-limits-memory`: Sets the memory limit for the container running the spinnaker service. Example: 1Gi.
- * `--container-requests-cpu`: Sets the cpu request for the container running the spinnaker service. Example: 250m.
- * `--container-requests-memory`: Sets the memory request for the container running the spinnaker service. Example: 512Mi.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--pod-limits-cpu`: Sets the cpu limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1.
- * `--pod-limits-memory`: Sets the memory limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1Gi.
- * `--pod-requests-cpu`: Sets the cpu request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 250m.
- * `--pod-requests-memory`: Sets the memory request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 512Mi.
- * `--replicas`: (*Default*: `1`) Set the number of replicas (pods) to be created for this service.
+- `--container-limits-cpu`: Sets the cpu limit for the container running the spinnaker service. Example: 1.
+- `--container-limits-memory`: Sets the memory limit for the container running the spinnaker service. Example: 1Gi.
+- `--container-requests-cpu`: Sets the cpu request for the container running the spinnaker service. Example: 250m.
+- `--container-requests-memory`: Sets the memory request for the container running the spinnaker service. Example: 512Mi.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--pod-limits-cpu`: Sets the cpu limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1.
+- `--pod-limits-memory`: Sets the memory limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1Gi.
+- `--pod-requests-cpu`: Sets the cpu request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 250m.
+- `--pod-requests-memory`: Sets the memory request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 512Mi.
+- `--replicas`: (_Default_: `1`) Set the number of replicas (pods) to be created for this service.
---
+
## hal config deploy component-sizing vault-client
Manage and view Spinnaker component sizing configuration for vault-client
#### Usage
+
```
hal config deploy component-sizing vault-client [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `delete`: Delete the custom component sizings for service vault-client
- * `edit`: Edit the component sizing for service vault-client, such as the number of replicas and the resources limits.
+
+- `delete`: Delete the custom component sizings for service vault-client
+- `edit`: Edit the component sizing for service vault-client, such as the number of replicas and the resources limits.
---
+
## hal config deploy component-sizing vault-client delete
Delete the custom component sizings for service vault-client
#### Usage
+
```
hal config deploy component-sizing vault-client delete [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config deploy component-sizing vault-client edit
Edit the component sizing for service vault-client, such as the number of replicas and the resources limits.
#### Usage
+
```
hal config deploy component-sizing vault-client edit [parameters]
```
#### Parameters
- * `--container-limits-cpu`: Sets the cpu limit for the container running the spinnaker service. Example: 1.
- * `--container-limits-memory`: Sets the memory limit for the container running the spinnaker service. Example: 1Gi.
- * `--container-requests-cpu`: Sets the cpu request for the container running the spinnaker service. Example: 250m.
- * `--container-requests-memory`: Sets the memory request for the container running the spinnaker service. Example: 512Mi.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--pod-limits-cpu`: Sets the cpu limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1.
- * `--pod-limits-memory`: Sets the memory limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1Gi.
- * `--pod-requests-cpu`: Sets the cpu request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 250m.
- * `--pod-requests-memory`: Sets the memory request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 512Mi.
- * `--replicas`: (*Default*: `1`) Set the number of replicas (pods) to be created for this service.
+- `--container-limits-cpu`: Sets the cpu limit for the container running the spinnaker service. Example: 1.
+- `--container-limits-memory`: Sets the memory limit for the container running the spinnaker service. Example: 1Gi.
+- `--container-requests-cpu`: Sets the cpu request for the container running the spinnaker service. Example: 250m.
+- `--container-requests-memory`: Sets the memory request for the container running the spinnaker service. Example: 512Mi.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--pod-limits-cpu`: Sets the cpu limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1.
+- `--pod-limits-memory`: Sets the memory limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1Gi.
+- `--pod-requests-cpu`: Sets the cpu request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 250m.
+- `--pod-requests-memory`: Sets the memory request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 512Mi.
+- `--replicas`: (_Default_: `1`) Set the number of replicas (pods) to be created for this service.
---
+
## hal config deploy component-sizing vault-server
Manage and view Spinnaker component sizing configuration for vault-server
#### Usage
+
```
hal config deploy component-sizing vault-server [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `delete`: Delete the custom component sizings for service vault-server
- * `edit`: Edit the component sizing for service vault-server, such as the number of replicas and the resources limits.
+
+- `delete`: Delete the custom component sizings for service vault-server
+- `edit`: Edit the component sizing for service vault-server, such as the number of replicas and the resources limits.
---
+
## hal config deploy component-sizing vault-server delete
Delete the custom component sizings for service vault-server
#### Usage
+
```
hal config deploy component-sizing vault-server delete [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config deploy component-sizing vault-server edit
Edit the component sizing for service vault-server, such as the number of replicas and the resources limits.
#### Usage
+
```
hal config deploy component-sizing vault-server edit [parameters]
```
#### Parameters
- * `--container-limits-cpu`: Sets the cpu limit for the container running the spinnaker service. Example: 1.
- * `--container-limits-memory`: Sets the memory limit for the container running the spinnaker service. Example: 1Gi.
- * `--container-requests-cpu`: Sets the cpu request for the container running the spinnaker service. Example: 250m.
- * `--container-requests-memory`: Sets the memory request for the container running the spinnaker service. Example: 512Mi.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--pod-limits-cpu`: Sets the cpu limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1.
- * `--pod-limits-memory`: Sets the memory limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1Gi.
- * `--pod-requests-cpu`: Sets the cpu request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 250m.
- * `--pod-requests-memory`: Sets the memory request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 512Mi.
- * `--replicas`: (*Default*: `1`) Set the number of replicas (pods) to be created for this service.
+- `--container-limits-cpu`: Sets the cpu limit for the container running the spinnaker service. Example: 1.
+- `--container-limits-memory`: Sets the memory limit for the container running the spinnaker service. Example: 1Gi.
+- `--container-requests-cpu`: Sets the cpu request for the container running the spinnaker service. Example: 250m.
+- `--container-requests-memory`: Sets the memory request for the container running the spinnaker service. Example: 512Mi.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--pod-limits-cpu`: Sets the cpu limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1.
+- `--pod-limits-memory`: Sets the memory limit for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 1Gi.
+- `--pod-requests-cpu`: Sets the cpu request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 250m.
+- `--pod-requests-memory`: Sets the memory request for the container running the spinnaker service, as well as any sidecar containers (e.g. the monitoring daemon). Example: 512Mi.
+- `--replicas`: (_Default_: `1`) Set the number of replicas (pods) to be created for this service.
---
+
## hal config deploy edit
Edit Spinnaker's deployment footprint and configuration.
#### Usage
+
```
hal config deploy edit [parameters]
```
#### Parameters
- * `--account-name`: The Spinnaker account that Spinnaker will be deployed to, assuming you are running a deployment of Spinnaker that requires an active cloud provider.
- * `--bootstrap-only`: A bootstrap-only account is the account in which Spinnaker itself is deployed. When true, this account will not be included the accounts managed by Spinnaker.
- * `--consul-address`: The address of a running Consul cluster. See [https://www.consul.io/](https://www.consul.io/).
-This is only required when Spinnaker is being deployed in non-Kubernetes clustered configuration.
- * `--consul-enabled`: Whether or not to use Consul as a service discovery mechanism to deploy Spinnaker.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--git-origin-user`: This is the git user your github fork exists under.
- * `--git-upstream-user`: This is the upstream git user you are configuring to pull changes from & push PRs to.
- * `--image-variant`: The container image variant type to use when deploying a distributed installation of Spinnaker.
- slim: Based on an Alpine image
- ubuntu: Based on Canonical's ubuntu:bionic image.
- java8: A variant of slim that uses the Java 8 runtime
- ubuntu-java8: A variant of ubuntu that uses the Java 8 runtime
-Default value: slim
- * `--liveness-probe-enabled`: When true, enable Kubernetes liveness probes on Spinnaker services deployed in a Distributed installation. See docs for more information: [https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/)
- * `--liveness-probe-initial-delay-seconds`: The number of seconds to wait before performing the first liveness probe. Should be set to the longest service startup time. See docs for more information: [https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/)
- * `--location`: This is the location spinnaker will be deployed to. When deploying to Kubernetes, use this flag to specify the namespace to deploy to (defaults to 'spinnaker')
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--type`: Distributed: Deploy Spinnaker with one server group per microservice, and a single shared Redis.
-LocalDebian: Download and run the Spinnaker debians on the machine running the Daemon.
-LocalGit: Download and run the Spinnaker git repos on the machine running the Daemon.
- * `--update-versions`: When set to "false", any *local* version of Spinnaker components will be used instead of attempting to update. This does not work for distributed installations of Spinnaker, where no *local* version exists.
- * `--vault-address`: The address of a running Vault datastore. See [https://www.vaultproject.io/](https://www.vaultproject.io/). This is only required when Spinnaker is being deployed in non-Kubernetes clustered configuration.
- * `--vault-enabled`: Whether or not to use Vault as a secret storage mechanism to deploy Spinnaker.
+- `--account-name`: The Spinnaker account that Spinnaker will be deployed to, assuming you are running a deployment of Spinnaker that requires an active cloud provider.
+- `--bootstrap-only`: A bootstrap-only account is the account in which Spinnaker itself is deployed. When true, this account will not be included the accounts managed by Spinnaker.
+- `--consul-address`: The address of a running Consul cluster. See [https://www.consul.io/](https://www.consul.io/).
+ This is only required when Spinnaker is being deployed in non-Kubernetes clustered configuration.
+- `--consul-enabled`: Whether or not to use Consul as a service discovery mechanism to deploy Spinnaker.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--git-origin-user`: This is the git user your github fork exists under.
+- `--git-upstream-user`: This is the upstream git user you are configuring to pull changes from & push PRs to.
+- `--image-variant`: The container image variant type to use when deploying a distributed installation of Spinnaker.
+ slim: Based on an Alpine image
+ ubuntu: Based on Canonical's ubuntu:bionic image.
+ java8: A variant of slim that uses the Java 8 runtime
+ ubuntu-java8: A variant of ubuntu that uses the Java 8 runtime
+ Default value: slim
+- `--liveness-probe-enabled`: When true, enable Kubernetes liveness probes on Spinnaker services deployed in a Distributed installation. See docs for more information: [https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/)
+- `--liveness-probe-initial-delay-seconds`: The number of seconds to wait before performing the first liveness probe. Should be set to the longest service startup time. See docs for more information: [https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/)
+- `--location`: This is the location spinnaker will be deployed to. When deploying to Kubernetes, use this flag to specify the namespace to deploy to (defaults to 'spinnaker')
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--type`: Distributed: Deploy Spinnaker with one server group per microservice, and a single shared Redis.
+ LocalDebian: Download and run the Spinnaker debians on the machine running the Daemon.
+ LocalGit: Download and run the Spinnaker git repos on the machine running the Daemon.
+- `--update-versions`: When set to "false", any _local_ version of Spinnaker components will be used instead of attempting to update. This does not work for distributed installations of Spinnaker, where no _local_ version exists.
+- `--vault-address`: The address of a running Vault datastore. See [https://www.vaultproject.io/](https://www.vaultproject.io/). This is only required when Spinnaker is being deployed in non-Kubernetes clustered configuration.
+- `--vault-enabled`: Whether or not to use Vault as a secret storage mechanism to deploy Spinnaker.
---
+
## hal config deploy ha
Configure, validate, and view the specified high availability Spinnaker service configuration.
#### Usage
+
```
hal config deploy ha [subcommands]
```
#### Subcommands
- * `clouddriver`: Manage and view Spinnaker configuration for the clouddriver high availability service
- * `echo`: Manage and view Spinnaker configuration for the echo high availability service
+
+- `clouddriver`: Manage and view Spinnaker configuration for the clouddriver high availability service
+- `echo`: Manage and view Spinnaker configuration for the echo high availability service
---
+
## hal config deploy ha clouddriver
Manage and view Spinnaker configuration for the clouddriver high availability service Manage and view Spinnaker configuration for the clouddriver high availability service. When clouddriver high availability is enabled, Halyard will deploy clouddriver as three separate services in order to increase availability: clouddriver-rw, clouddriver-ro, and clouddriver-caching. The clouddriver-rw service handles mutation operations sent via orca. The clouddriver-ro service handles read queries and does not perform write operations to redis. The clouddriver-caching service handles the periodic caching of cloud provider data, and is isolated from the rest of Spinnaker. The three services are configured to use the shared redis provisioned by Halyard, by default. To achieve more scale, a redis master endpoint and a redis slave endpoint can be supplied. The clouddriver-rw and clouddriver-caching services will use the redis master and the clouddriver-ro service will use the redis slave.
#### Usage
+
```
hal config deploy ha clouddriver [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `disable`: Set the clouddriver high availability service as disabled
- * `edit`: Edit the clouddriver high availability service
- * `enable`: Set the clouddriver high availability service as enabled
+
+- `disable`: Set the clouddriver high availability service as disabled
+- `edit`: Edit the clouddriver high availability service
+- `enable`: Set the clouddriver high availability service as enabled
---
+
## hal config deploy ha clouddriver disable
Set the clouddriver high availability service as disabled
#### Usage
+
```
hal config deploy ha clouddriver disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config deploy ha clouddriver edit
Edit the clouddriver high availability service
#### Usage
+
```
hal config deploy ha clouddriver edit [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--redis-master-endpoint`: Set external Redis endpoint for clouddriver-rw and clouddriver-caching. The Redis URI schema is described here: [https://www.iana.org/assignments/uri-schemes/prov/redis](https://www.iana.org/assignments/uri-schemes/prov/redis). clouddriver-rw and clouddriver-caching are configured to use the shared Redis, by default.
- * `--redis-slave-deck-endpoint`: Set external Redis endpoint for clouddriver-ro-deck. The Redis URI schema is described here: [https://www.iana.org/assignments/uri-schemes/prov/redis](https://www.iana.org/assignments/uri-schemes/prov/redis). clouddriver-ro-deck is configured to use the shared Redis, by default.
- * `--redis-slave-endpoint`: Set external Redis endpoint for clouddriver-ro. The Redis URI schema is described here: [https://www.iana.org/assignments/uri-schemes/prov/redis](https://www.iana.org/assignments/uri-schemes/prov/redis). clouddriver-ro is configured to use the shared Redis, by default.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--redis-master-endpoint`: Set external Redis endpoint for clouddriver-rw and clouddriver-caching. The Redis URI schema is described here: [https://www.iana.org/assignments/uri-schemes/prov/redis](https://www.iana.org/assignments/uri-schemes/prov/redis). clouddriver-rw and clouddriver-caching are configured to use the shared Redis, by default.
+- `--redis-slave-deck-endpoint`: Set external Redis endpoint for clouddriver-ro-deck. The Redis URI schema is described here: [https://www.iana.org/assignments/uri-schemes/prov/redis](https://www.iana.org/assignments/uri-schemes/prov/redis). clouddriver-ro-deck is configured to use the shared Redis, by default.
+- `--redis-slave-endpoint`: Set external Redis endpoint for clouddriver-ro. The Redis URI schema is described here: [https://www.iana.org/assignments/uri-schemes/prov/redis](https://www.iana.org/assignments/uri-schemes/prov/redis). clouddriver-ro is configured to use the shared Redis, by default.
---
+
## hal config deploy ha clouddriver enable
Set the clouddriver high availability service as enabled
#### Usage
+
```
hal config deploy ha clouddriver enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config deploy ha echo
Manage and view Spinnaker configuration for the echo high availability service Manage and view Spinnaker configuration for the echo high availability service. When echo high availability is enabled, Halyard will deploy echo as two separate services in order to increase availability: echo-scheduler and echo-worker. The echo-scheduler service only handles Spinnaker cron-jobs and is isolated from the rest of Spinnaker. The echo-worker handles everything else.
#### Usage
+
```
hal config deploy ha echo [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `disable`: Set the echo high availability service as disabled
- * `enable`: Set the echo high availability service as enabled
+
+- `disable`: Set the echo high availability service as disabled
+- `enable`: Set the echo high availability service as enabled
---
+
## hal config deploy ha echo disable
Set the echo high availability service as disabled
#### Usage
+
```
hal config deploy ha echo disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config deploy ha echo enable
Set the echo high availability service as enabled
#### Usage
+
```
hal config deploy ha echo enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config edit
Configure top-level, global configuration parameters. The properties edited here affect all Spinnaker subcomponents.
#### Usage
+
```
hal config edit [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--timezone`: The timezone your Spinnaker instance runs in. This affects what the UI will display as well as how CRON triggers are run.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--timezone`: The timezone your Spinnaker instance runs in. This affects what the UI will display as well as how CRON triggers are run.
---
+
## hal config features
Display the state of Spinnaker's feature flags.
#### Usage
+
```
hal config features [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `edit`: Enable and disable Spinnaker feature flags.
+
+- `edit`: Enable and disable Spinnaker feature flags.
---
+
## hal config features edit
Enable and disable Spinnaker feature flags.
#### Usage
+
```
hal config features edit [parameters]
```
#### Parameters
- * `--artifacts`: Enable artifact support. Read more at [https://spinnaker.io/reference/artifacts/](https://spinnaker.io/reference/artifacts/)
- * `--artifacts-rewrite`: Enable new artifact support. Read more at [https://www.spinnaker.io/reference/artifacts-with-artifactsrewrite/](https://www.spinnaker.io/reference/artifacts-with-artifactsrewrite/)
- * `--chaos`: Enable Chaos Monkey support. For this to work, you'll need a running Chaos Monkey deployment. Currently, Halyard doesn't configure Chaos Monkey for you; read more instructions here [https://github.com/Netflix/chaosmonkey/wiki](https://github.com/Netflix/chaosmonkey/wiki).
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--gremlin`: Enable Gremlin fault-injection support.
- * `--managed-pipeline-templates-v2-ui`: Enable managed pipeline templates v2 UI support.
- * `--mine-canary`: Enable canary support. For this to work, you'll need a canary judge configured. Currently, Halyard does not configure canary judge for you.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--pipeline-templates`: Enable pipeline template support. Read more at [https://github.com/spinnaker/dcd-spec](https://github.com/spinnaker/dcd-spec).
+- `--artifacts`: Enable artifact support. Read more at [https://spinnaker.io/reference/artifacts/](https://spinnaker.io/reference/artifacts/)
+- `--artifacts-rewrite`: Enable new artifact support. Read more at [https://www.spinnaker.io/reference/artifacts-with-artifactsrewrite/](https://www.spinnaker.io/reference/artifacts-with-artifactsrewrite/)
+- `--chaos`: Enable Chaos Monkey support. For this to work, you'll need a running Chaos Monkey deployment. Currently, Halyard doesn't configure Chaos Monkey for you; read more instructions here [https://github.com/Netflix/chaosmonkey/wiki](https://github.com/Netflix/chaosmonkey/wiki).
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--gremlin`: Enable Gremlin fault-injection support.
+- `--managed-pipeline-templates-v2-ui`: Enable managed pipeline templates v2 UI support.
+- `--mine-canary`: Enable canary support. For this to work, you'll need a canary judge configured. Currently, Halyard does not configure canary judge for you.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--pipeline-templates`: Enable pipeline template support. Read more at [https://github.com/spinnaker/dcd-spec](https://github.com/spinnaker/dcd-spec).
---
+
## hal config generate
Generate the full Spinnaker config for your current deployment. This does _not_ apply that configuration to your running Spinnaker installation. That either needs to be done manually, or with `hal deploy apply`.
#### Usage
+
```
hal config generate [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config list
Lists all deployments
#### Usage
+
```
hal config list [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config metric-stores
Configure Spinnaker's metric stores. Metrics stores are used to store metrics for the various Spinnaker micro-services. These metrics are not related in any way to canary deployments. The technologies backing both are similar, but metrics stores are places to push metrics regarding Spinnaker metrics, whereas canary metrics stores are used to pull metrics to analyze deployments. This configuration only affects the publishing of metrics against whichever metric stores you enable (it can be more than one).
#### Usage
+
```
hal config metric-stores [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `datadog`: Configure your datadog metric store.
- * `edit`: Configure global metric stores properties.
- * `newrelic`: Configure your newrelic metric store.
- * `prometheus`: Configure your prometheus metric store.
- * `stackdriver`: Configure your stackdriver metric store.
+
+- `datadog`: Configure your datadog metric store.
+- `edit`: Configure global metric stores properties.
+- `newrelic`: Configure your newrelic metric store.
+- `prometheus`: Configure your prometheus metric store.
+- `stackdriver`: Configure your stackdriver metric store.
---
+
## hal config metric-stores datadog
Configure your datadog metric store.
#### Usage
+
```
hal config metric-stores datadog [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `disable`: Set the datadog method as disabled
- * `edit`: Edit the datadog metric store.
- * `enable`: Set the datadog method as enabled
+
+- `disable`: Set the datadog method as disabled
+- `edit`: Edit the datadog metric store.
+- `enable`: Set the datadog method as enabled
---
+
## hal config metric-stores datadog disable
Set the datadog method as disabled
#### Usage
+
```
hal config metric-stores datadog disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config metric-stores datadog edit
Edit the datadog metric store.
#### Usage
+
```
hal config metric-stores datadog edit [parameters]
```
#### Parameters
- * `--add-tag`: Add this tag to the list of Datadog tags.
- * `--api-key`: Your datadog API key.
- * `--app-key`: Your datadog app key. This is only required if you want Spinnaker to push pre-configured Spinnaker dashboards to your Datadog account.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--remove-tag`: Remove this tag from the list of Datadog tags.
- * `--tags`: (*Default*: `[]`) Your datadog custom tags. Please delimit the KVP with colons i.e. --tags app:test env:dev
+- `--add-tag`: Add this tag to the list of Datadog tags.
+- `--api-key`: Your datadog API key.
+- `--app-key`: Your datadog app key. This is only required if you want Spinnaker to push pre-configured Spinnaker dashboards to your Datadog account.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--remove-tag`: Remove this tag from the list of Datadog tags.
+- `--tags`: (_Default_: `[]`) Your datadog custom tags. Please delimit the KVP with colons i.e. --tags app:test env:dev
---
+
## hal config metric-stores datadog enable
Set the datadog method as enabled
#### Usage
+
```
hal config metric-stores datadog enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config metric-stores edit
Configure global metric stores properties.
#### Usage
+
```
hal config metric-stores edit [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--period`: (*Required*) Set the polling period for the monitoring daemon.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--period`: (_Required_) Set the polling period for the monitoring daemon.
---
+
## hal config metric-stores newrelic
Configure your newrelic metric store.
#### Usage
+
```
hal config metric-stores newrelic [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `disable`: Set the newrelic method as disabled
- * `edit`: Edit the newrelic metric store.
- * `enable`: Set the newrelic method as enabled
+
+- `disable`: Set the newrelic method as disabled
+- `edit`: Edit the newrelic metric store.
+- `enable`: Set the newrelic method as enabled
---
+
## hal config metric-stores newrelic disable
Set the newrelic method as disabled
#### Usage
+
```
hal config metric-stores newrelic disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config metric-stores newrelic edit
Edit the newrelic metric store.
#### Usage
+
```
hal config metric-stores newrelic edit [parameters]
```
#### Parameters
- * `--add-tag`: Add this tag to the list of tags. Use the format key:value i.e. --add-tag app:test
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--host`: The URL to post metric data to. In almost all cases, this is set correctly by default and should not be used.
- * `--insert-key`: Your New Relic Insights insert key
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--remove-tag`: Remove this tag from the list of tags. Use the name of the tag you want to remove i.e. --remove-tag app
- * `--tags`: (*Default*: `[]`) Your custom tags. Please delimit the KVP with colons i.e. --tags app:test env:dev
+- `--add-tag`: Add this tag to the list of tags. Use the format key:value i.e. --add-tag app:test
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--host`: The URL to post metric data to. In almost all cases, this is set correctly by default and should not be used.
+- `--insert-key`: Your New Relic Insights insert key
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--remove-tag`: Remove this tag from the list of tags. Use the name of the tag you want to remove i.e. --remove-tag app
+- `--tags`: (_Default_: `[]`) Your custom tags. Please delimit the KVP with colons i.e. --tags app:test env:dev
---
+
## hal config metric-stores newrelic enable
Set the newrelic method as enabled
#### Usage
+
```
hal config metric-stores newrelic enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config metric-stores prometheus
Configure your prometheus metric store.
#### Usage
+
```
hal config metric-stores prometheus [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `disable`: Set the prometheus method as disabled
- * `edit`: Edit the prometheus metric store.
- * `enable`: Set the prometheus method as enabled
+
+- `disable`: Set the prometheus method as disabled
+- `edit`: Edit the prometheus metric store.
+- `enable`: Set the prometheus method as enabled
---
+
## hal config metric-stores prometheus disable
Set the prometheus method as disabled
#### Usage
+
```
hal config metric-stores prometheus disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config metric-stores prometheus edit
Edit the prometheus metric store.
#### Usage
+
```
hal config metric-stores prometheus edit [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--push-gateway`: The endpoint the monitoring Daemon should push metrics to. If you have configured Prometheus to automatically discover all your Spinnaker services and pull metrics from them this is not required.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--push-gateway`: The endpoint the monitoring Daemon should push metrics to. If you have configured Prometheus to automatically discover all your Spinnaker services and pull metrics from them this is not required.
---
+
## hal config metric-stores prometheus enable
Set the prometheus method as enabled
#### Usage
+
```
hal config metric-stores prometheus enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config metric-stores stackdriver
Configure your stackdriver metric store.
#### Usage
+
```
hal config metric-stores stackdriver [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `disable`: Set the stackdriver method as disabled
- * `edit`: Edit the stackdriver metric store.
- * `enable`: Set the stackdriver method as enabled
+
+- `disable`: Set the stackdriver method as disabled
+- `edit`: Edit the stackdriver metric store.
+- `enable`: Set the stackdriver method as enabled
---
+
## hal config metric-stores stackdriver disable
Set the stackdriver method as disabled
#### Usage
+
```
hal config metric-stores stackdriver disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config metric-stores stackdriver edit
Edit the stackdriver metric store.
#### Usage
+
```
hal config metric-stores stackdriver edit [parameters]
```
#### Parameters
- * `--credentials-path`: A path to a Google JSON service account that has permission to publish metrics.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--project`: The project Spinnaker's metrics should be published to.
- * `--zone`: The zone Spinnaker's metrics should be associated with.
+- `--credentials-path`: A path to a Google JSON service account that has permission to publish metrics.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--project`: The project Spinnaker's metrics should be published to.
+- `--zone`: The zone Spinnaker's metrics should be associated with.
---
+
## hal config metric-stores stackdriver enable
Set the stackdriver method as enabled
#### Usage
+
```
hal config metric-stores stackdriver enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config notification
Display the state of Spinnaker's notification settings.
#### Usage
+
```
hal config notification [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `github-status`: Manage and view Spinnaker configuration for the github-status notification
- * `pubsub`: Configure, validate, and view the specified pubsub.
- * `slack`: Manage and view Spinnaker configuration for the slack notification
- * `twilio`: Manage and view Spinnaker configuration for the twilio notification
+
+- `github-status`: Manage and view Spinnaker configuration for the github-status notification
+- `pubsub`: Configure, validate, and view the specified pubsub.
+- `slack`: Manage and view Spinnaker configuration for the slack notification
+- `twilio`: Manage and view Spinnaker configuration for the twilio notification
---
+
## hal config notification github-status
Manage and view Spinnaker configuration for the github-status notification
#### Usage
+
```
hal config notification github-status [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `disable`: Set the github-status notification as disabled
- * `edit`: Edit the github-status notification type
- * `enable`: Set the github-status notification as enabled
+
+- `disable`: Set the github-status notification as disabled
+- `edit`: Edit the github-status notification type
+- `enable`: Set the github-status notification as enabled
---
+
## hal config notification github-status disable
Set the github-status notification as disabled
#### Usage
+
```
hal config notification github-status disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config notification github-status edit
Edit the github-status notification type
#### Usage
+
```
hal config notification github-status edit [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--token`: (*Sensitive data* - user will be prompted on standard input) Your github account token.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--token`: (_Sensitive data_ - user will be prompted on standard input) Your github account token.
---
+
## hal config notification github-status enable
Set the github-status notification as enabled
#### Usage
+
```
hal config notification github-status enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config notification pubsub
Configure, validate, and view the specified pubsub.
#### Usage
+
```
hal config notification pubsub [subcommands]
```
#### Subcommands
- * `google`: Manage and view Spinnaker configuration for the google pubsub
+
+- `google`: Manage and view Spinnaker configuration for the google pubsub
---
+
## hal config notification pubsub google
Manage and view Spinnaker configuration for the google pubsub
#### Usage
+
```
hal config notification pubsub google [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `add`: Add a publisher of type google
- * `delete`: Delete a specific google publisher by name.
- * `disable`: Set the google pubsub as disabled
- * `edit`: Edit an publisher in the google pubsub.
- * `enable`: Set the google pubsub as enabled
- * `get`: Get the specified publisher details for the google pubsub.
- * `list`: List the publisher names for the google pubsub.
+
+- `add`: Add a publisher of type google
+- `delete`: Delete a specific google publisher by name.
+- `disable`: Set the google pubsub as disabled
+- `edit`: Edit an publisher in the google pubsub.
+- `enable`: Set the google pubsub as enabled
+- `get`: Get the specified publisher details for the google pubsub.
+- `list`: List the publisher names for the google pubsub.
---
+
## hal config notification pubsub google add
Add a publisher of type google
#### Usage
+
```
hal config notification pubsub google add PUBLISHER [parameters]
```
#### Parameters
+
`PUBLISHER`: The name of the publishers to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--json-path`: The path to a JSON service account that Spinnaker will use as credentials. This is only needed if Spinnaker is not deployed on a Google Compute Engine VM, or needs permissions not afforded to the VM it is running on. See [https://cloud.google.com/compute/docs/access/service-accounts](https://cloud.google.com/compute/docs/access/service-accounts) for more information.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--project`: The name of the GCP project your subscription lives in.
- * `--topic-name`: The name of the topic to publish to. This identifier does not include the name of the project, and must already be configured for Spinnaker to work.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--json-path`: The path to a JSON service account that Spinnaker will use as credentials. This is only needed if Spinnaker is not deployed on a Google Compute Engine VM, or needs permissions not afforded to the VM it is running on. See [https://cloud.google.com/compute/docs/access/service-accounts](https://cloud.google.com/compute/docs/access/service-accounts) for more information.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--project`: The name of the GCP project your subscription lives in.
+- `--topic-name`: The name of the topic to publish to. This identifier does not include the name of the project, and must already be configured for Spinnaker to work.
---
+
## hal config notification pubsub google delete
Delete a specific google publisher by name.
#### Usage
+
```
hal config notification pubsub google delete PUBLISHER [parameters]
```
#### Parameters
+
`PUBLISHER`: The name of the publishers to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config notification pubsub google disable
Set the google pubsub as disabled
#### Usage
+
```
hal config notification pubsub google disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config notification pubsub google edit
Edit an publisher in the google pubsub.
#### Usage
+
```
hal config notification pubsub google edit PUBLISHER [parameters]
```
#### Parameters
+
`PUBLISHER`: The name of the publishers to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--json-path`: The path to a JSON service account that Spinnaker will use as credentials. This is only needed if Spinnaker is not deployed on a Google Compute Engine VM, or needs permissions not afforded to the VM it is running on. See [https://cloud.google.com/compute/docs/access/service-accounts](https://cloud.google.com/compute/docs/access/service-accounts) for more information.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--project`: The name of the GCP project your subscription lives in.
- * `--topic-name`: The name of the topic to publish to. This identifier does not include the name of the project, and must already be configured for Spinnaker to work.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--json-path`: The path to a JSON service account that Spinnaker will use as credentials. This is only needed if Spinnaker is not deployed on a Google Compute Engine VM, or needs permissions not afforded to the VM it is running on. See [https://cloud.google.com/compute/docs/access/service-accounts](https://cloud.google.com/compute/docs/access/service-accounts) for more information.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--project`: The name of the GCP project your subscription lives in.
+- `--topic-name`: The name of the topic to publish to. This identifier does not include the name of the project, and must already be configured for Spinnaker to work.
---
+
## hal config notification pubsub google enable
Set the google pubsub as enabled
#### Usage
+
```
hal config notification pubsub google enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config notification pubsub google get
Get the specified publisher details for the google pubsub.
#### Usage
+
```
hal config notification pubsub google get PUBLISHER [parameters]
```
#### Parameters
+
`PUBLISHER`: The name of the publishers to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config notification pubsub google list
List the publisher names for the google pubsub.
#### Usage
+
```
hal config notification pubsub google list [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config notification slack
Manage and view Spinnaker configuration for the slack notification
#### Usage
+
```
hal config notification slack [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `disable`: Set the slack notification as disabled
- * `edit`: Edit the slack notification type
- * `enable`: Set the slack notification as enabled
+
+- `disable`: Set the slack notification as disabled
+- `edit`: Edit the slack notification type
+- `enable`: Set the slack notification as enabled
---
+
## hal config notification slack disable
Set the slack notification as disabled
#### Usage
+
```
hal config notification slack disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config notification slack edit
Edit the slack notification type
#### Usage
+
```
hal config notification slack edit [parameters]
```
#### Parameters
- * `--base-url`: Slack endpoint. Optional, only set if using a compatible API.
- * `--bot-name`: The name of your slack bot.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--force-use-incoming-webhook`: Force usage of incoming webhooks endpoint for slack. Optional, only set if using a compatible API.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--token`: (*Sensitive data* - user will be prompted on standard input) Your slack bot token.
+- `--base-url`: Slack endpoint. Optional, only set if using a compatible API.
+- `--bot-name`: The name of your slack bot.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--force-use-incoming-webhook`: Force usage of incoming webhooks endpoint for slack. Optional, only set if using a compatible API.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--token`: (_Sensitive data_ - user will be prompted on standard input) Your slack bot token.
---
+
## hal config notification slack enable
Set the slack notification as enabled
#### Usage
+
```
hal config notification slack enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config notification twilio
Manage and view Spinnaker configuration for the twilio notification
#### Usage
+
```
hal config notification twilio [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `disable`: Set the twilio notification as disabled
- * `edit`: Edit the twilio notification type
- * `enable`: Set the twilio notification as enabled
+
+- `disable`: Set the twilio notification as disabled
+- `edit`: Edit the twilio notification type
+- `enable`: Set the twilio notification as enabled
---
+
## hal config notification twilio disable
Set the twilio notification as disabled
#### Usage
+
```
hal config notification twilio disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config notification twilio edit
Edit the twilio notification type
#### Usage
+
```
hal config notification twilio edit [parameters]
```
#### Parameters
- * `--account`: Your Twilio account SID.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--from`: The phone number from which the SMS will be sent (i.e. +1234-567-8910).
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--token`: (*Sensitive data* - user will be prompted on standard input) Your Twilio auth token.
+- `--account`: Your Twilio account SID.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--from`: The phone number from which the SMS will be sent (i.e. +1234-567-8910).
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--token`: (_Sensitive data_ - user will be prompted on standard input) Your Twilio auth token.
---
+
## hal config notification twilio enable
Set the twilio notification as enabled
#### Usage
+
```
hal config notification twilio enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider
Configure, validate, and view the specified provider.
#### Usage
+
```
hal config provider [subcommands]
```
#### Subcommands
- * `appengine`: Manage and view Spinnaker configuration for the appengine provider
- * `aws`: Manage and view Spinnaker configuration for the aws provider
- * `azure`: Manage and view Spinnaker configuration for the azure provider
- * `cloudfoundry`: Manage and view Spinnaker configuration for the cloudfoundry provider
- * `dcos`: Manage and view Spinnaker configuration for the dcos provider
- * `docker-registry`: Manage and view Spinnaker configuration for the dockerRegistry provider
- * `ecs`: Manage and view Spinnaker configuration for the ecs provider
- * `google`: Manage and view Spinnaker configuration for the google provider
- * `huaweicloud`: Manage and view Spinnaker configuration for the huaweicloud provider
- * `kubernetes`: Manage and view Spinnaker configuration for the kubernetes provider
- * `oracle`: Manage and view Spinnaker configuration for the oracle provider
- * `tencentcloud`: Manage and view Spinnaker configuration for the tencentcloud provider
+
+- `appengine`: Manage and view Spinnaker configuration for the appengine provider
+- `aws`: Manage and view Spinnaker configuration for the aws provider
+- `azure`: Manage and view Spinnaker configuration for the azure provider
+- `cloudfoundry`: Manage and view Spinnaker configuration for the cloudfoundry provider
+- `dcos`: Manage and view Spinnaker configuration for the dcos provider
+- `docker-registry`: Manage and view Spinnaker configuration for the dockerRegistry provider
+- `ecs`: Manage and view Spinnaker configuration for the ecs provider
+- `google`: Manage and view Spinnaker configuration for the google provider
+- `huaweicloud`: Manage and view Spinnaker configuration for the huaweicloud provider
+- `kubernetes`: Manage and view Spinnaker configuration for the kubernetes provider
+- `oracle`: Manage and view Spinnaker configuration for the oracle provider
+- `tencentcloud`: Manage and view Spinnaker configuration for the tencentcloud provider
---
+
## hal config provider appengine
The App Engine provider is used to deploy resources to any number of App Engine applications. To get started with App Engine, visit [https://cloud.google.com/appengine/docs/](https://cloud.google.com/appengine/docs/). For more information on how to configure individual accounts, please read the documentation under `hal config provider appengine account -h`.
#### Usage
+
```
hal config provider appengine [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `account`: Manage and view Spinnaker configuration for the appengine provider's account
- * `disable`: Set the appengine provider as disabled
- * `edit`: Edit Spinnaker's app engine configuration.
- * `enable`: Set the appengine provider as enabled
+
+- `account`: Manage and view Spinnaker configuration for the appengine provider's account
+- `disable`: Set the appengine provider as disabled
+- `edit`: Edit Spinnaker's app engine configuration.
+- `enable`: Set the appengine provider as enabled
---
+
## hal config provider appengine account
An account in the App Engine provider refers to a single App Engine application. Spinnaker assumes that your App Engine application already exists. You can create an application in your Google Cloud Platform project by running `gcloud app create --region `.
#### Usage
+
```
hal config provider appengine account ACCOUNT [parameters] [subcommands]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `add`: Add an account to the appengine provider.
- * `delete`: Delete a specific appengine account by name.
- * `edit`: Edit an account in the appengine provider.
- * `get`: Get the specified account details for the appengine provider.
- * `list`: List the account names for the appengine provider.
+
+- `add`: Add an account to the appengine provider.
+- `delete`: Delete a specific appengine account by name.
+- `edit`: Edit an account in the appengine provider.
+- `get`: Get the specified account details for the appengine provider.
+- `list`: List the account names for the appengine provider.
---
+
## hal config provider appengine account add
Add an account to the appengine provider.
#### Usage
+
```
hal config provider appengine account add ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--caching-interval-seconds`: The interval in seconds at which Spinnaker will poll for updates in your AppEngine clusters.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--environment`: The environment name for the account. Many accounts can share the same environment (e.g. dev, test, prod)
- * `--gcloud-release-track`: The gcloud release track (ALPHA, BETA, or STABLE) that Spinnaker will use when deploying to App Engine.
- * `--git-https-password`: (*Sensitive data* - user will be prompted on standard input) A password to be used when connecting with a remote git repository server over HTTPS.
- * `--git-https-username`: A username to be used when connecting with a remote git repository server over HTTPS.
- * `--github-oauth-access-token`: (*Sensitive data* - user will be prompted on standard input) An OAuth token provided by Github for connecting to a git repository over HTTPS. See [https://help.github.com/articles/creating-an-access-token-for-command-line-use](https://help.github.com/articles/creating-an-access-token-for-command-line-use) for more information.
- * `--json-path`: The path to a JSON service account that Spinnaker will use as credentials. This is only needed if Spinnaker is not deployed on a Google Compute Engine VM, or needs permissions not afforded to the VM it is running on. See [https://cloud.google.com/compute/docs/access/service-accounts](https://cloud.google.com/compute/docs/access/service-accounts) for more information.
- * `--local-repository-directory`: (*Default*: `/var/tmp/clouddriver`) A local directory to be used to stage source files for App Engine deployments within Spinnaker's Clouddriver microservice.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--omit-services`: A list of regular expressions. Any service matching one of these regexes will be ignored by Spinnaker.
- * `--omit-versions`: A list of regular expressions. Any version matching one of these regexes will be ignored by Spinnaker.
- * `--project`: (*Required*) The Google Cloud Platform project this Spinnaker account will manage.
- * `--read-permissions`: (*Default*: `[]`) A user must have at least one of these roles in order to view this account's cloud resources.
- * `--required-group-membership`: (*Default*: `[]`) A user must be a member of at least one specified group in order to make changes to this account's cloud resources.
- * `--services`: A list of regular expressions. Any service matching one of these regexes will be indexed by Spinnaker.
- * `--ssh-known-hosts-file-path`: The path to a known_hosts file to be used when connecting with a remote git repository over SSH.
- * `--ssh-private-key-file-path`: The path to an SSH private key to be used when connecting with a remote git repository over SSH.
- * `--ssh-private-key-passphrase`: (*Sensitive data* - user will be prompted on standard input) The passphrase to an SSH private key to be used when connecting with a remote git repository over SSH.
- * `--ssh-trust-unknown-hosts`: (*Default*: `false`) Enabling this flag will allow Spinnaker to connect with a remote git repository over SSH without verifying the server's IP address against a known_hosts file.
- * `--versions`: A list of regular expressions. Any version matching one of these regexes will be indexed by Spinnaker.
- * `--write-permissions`: (*Default*: `[]`) A user must have at least one of these roles in order to make changes to this account's cloud resources.
+- `--caching-interval-seconds`: The interval in seconds at which Spinnaker will poll for updates in your AppEngine clusters.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--environment`: The environment name for the account. Many accounts can share the same environment (e.g. dev, test, prod)
+- `--gcloud-release-track`: The gcloud release track (ALPHA, BETA, or STABLE) that Spinnaker will use when deploying to App Engine.
+- `--git-https-password`: (_Sensitive data_ - user will be prompted on standard input) A password to be used when connecting with a remote git repository server over HTTPS.
+- `--git-https-username`: A username to be used when connecting with a remote git repository server over HTTPS.
+- `--github-oauth-access-token`: (_Sensitive data_ - user will be prompted on standard input) An OAuth token provided by Github for connecting to a git repository over HTTPS. See [https://help.github.com/articles/creating-an-access-token-for-command-line-use](https://help.github.com/articles/creating-an-access-token-for-command-line-use) for more information.
+- `--json-path`: The path to a JSON service account that Spinnaker will use as credentials. This is only needed if Spinnaker is not deployed on a Google Compute Engine VM, or needs permissions not afforded to the VM it is running on. See [https://cloud.google.com/compute/docs/access/service-accounts](https://cloud.google.com/compute/docs/access/service-accounts) for more information.
+- `--local-repository-directory`: (_Default_: `/var/tmp/clouddriver`) A local directory to be used to stage source files for App Engine deployments within Spinnaker's Clouddriver microservice.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--omit-services`: A list of regular expressions. Any service matching one of these regexes will be ignored by Spinnaker.
+- `--omit-versions`: A list of regular expressions. Any version matching one of these regexes will be ignored by Spinnaker.
+- `--project`: (_Required_) The Google Cloud Platform project this Spinnaker account will manage.
+- `--read-permissions`: (_Default_: `[]`) A user must have at least one of these roles in order to view this account's cloud resources.
+- `--required-group-membership`: (_Default_: `[]`) A user must be a member of at least one specified group in order to make changes to this account's cloud resources.
+- `--services`: A list of regular expressions. Any service matching one of these regexes will be indexed by Spinnaker.
+- `--ssh-known-hosts-file-path`: The path to a known_hosts file to be used when connecting with a remote git repository over SSH.
+- `--ssh-private-key-file-path`: The path to an SSH private key to be used when connecting with a remote git repository over SSH.
+- `--ssh-private-key-passphrase`: (_Sensitive data_ - user will be prompted on standard input) The passphrase to an SSH private key to be used when connecting with a remote git repository over SSH.
+- `--ssh-trust-unknown-hosts`: (_Default_: `false`) Enabling this flag will allow Spinnaker to connect with a remote git repository over SSH without verifying the server's IP address against a known_hosts file.
+- `--versions`: A list of regular expressions. Any version matching one of these regexes will be indexed by Spinnaker.
+- `--write-permissions`: (_Default_: `[]`) A user must have at least one of these roles in order to make changes to this account's cloud resources.
---
+
## hal config provider appengine account delete
Delete a specific appengine account by name.
#### Usage
+
```
hal config provider appengine account delete ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider appengine account edit
Edit an account in the appengine provider.
#### Usage
+
```
hal config provider appengine account edit ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--add-read-permission`: Add this permission to the list of read permissions.
- * `--add-required-group-membership`: Add this group to the list of required group memberships.
- * `--add-write-permission`: Add this permission to the list of write permissions.
- * `--caching-interval-seconds`: The interval in seconds at which Spinnaker will poll for updates in your AppEngine clusters.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--environment`: The environment name for the account. Many accounts can share the same environment (e.g. dev, test, prod)
- * `--gcloud-release-track`: The gcloud release track (ALPHA, BETA, or STABLE) that Spinnaker will use when deploying to App Engine.
- * `--git-https-password`: (*Sensitive data* - user will be prompted on standard input) A password to be used when connecting with a remote git repository server over HTTPS.
- * `--git-https-username`: A username to be used when connecting with a remote git repository server over HTTPS.
- * `--github-oauth-access-token`: (*Sensitive data* - user will be prompted on standard input) An OAuth token provided by Github for connecting to a git repository over HTTPS. See [https://help.github.com/articles/creating-an-access-token-for-command-line-use](https://help.github.com/articles/creating-an-access-token-for-command-line-use) for more information.
- * `--json-path`: The path to a JSON service account that Spinnaker will use as credentials. This is only needed if Spinnaker is not deployed on a Google Compute Engine VM, or needs permissions not afforded to the VM it is running on. See [https://cloud.google.com/compute/docs/access/service-accounts](https://cloud.google.com/compute/docs/access/service-accounts) for more information.
- * `--local-repository-directory`: A local directory to be used to stage source files for App Engine deployments within Spinnaker's Clouddriver microservice.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--omit-services`: A list of regular expressions. Any service matching one of these regexes will be ignored by Spinnaker.
- * `--omit-versions`: A list of regular expressions. Any version matching one of these regexes will be ignored by Spinnaker.
- * `--project`: The Google Cloud Platform project this Spinnaker account will manage.
- * `--read-permissions`: A user must have at least one of these roles in order to view this account's cloud resources.
- * `--remove-read-permission`: Remove this permission from the list of read permissions.
- * `--remove-required-group-membership`: Remove this group from the list of required group memberships.
- * `--remove-write-permission`: Remove this permission to from list of write permissions.
- * `--required-group-membership`: A user must be a member of at least one specified group in order to make changes to this account's cloud resources.
- * `--services`: A list of regular expressions. Any service matching one of these regexes will be indexed by Spinnaker.
- * `--ssh-known-hosts-file-path`: The path to a known_hosts file to be used when connecting with a remote git repository over SSH.
- * `--ssh-private-key-file-path`: The path to an SSH private key to be used when connecting with a remote git repository over SSH.
- * `--ssh-private-key-passphrase`: (*Sensitive data* - user will be prompted on standard input) The passphrase to an SSH private key to be used when connecting with a remote git repository over SSH.
- * `--ssh-trust-unknown-hosts`: Enabling this flag will allow Spinnaker to connect with a remote git repository over SSH without verifying the server's IP address against a known_hosts file.
- * `--versions`: A list of regular expressions. Any version matching one of these regexes will be indexed by Spinnaker.
- * `--write-permissions`: A user must have at least one of these roles in order to make changes to this account's cloud resources.
+- `--add-read-permission`: Add this permission to the list of read permissions.
+- `--add-required-group-membership`: Add this group to the list of required group memberships.
+- `--add-write-permission`: Add this permission to the list of write permissions.
+- `--caching-interval-seconds`: The interval in seconds at which Spinnaker will poll for updates in your AppEngine clusters.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--environment`: The environment name for the account. Many accounts can share the same environment (e.g. dev, test, prod)
+- `--gcloud-release-track`: The gcloud release track (ALPHA, BETA, or STABLE) that Spinnaker will use when deploying to App Engine.
+- `--git-https-password`: (_Sensitive data_ - user will be prompted on standard input) A password to be used when connecting with a remote git repository server over HTTPS.
+- `--git-https-username`: A username to be used when connecting with a remote git repository server over HTTPS.
+- `--github-oauth-access-token`: (_Sensitive data_ - user will be prompted on standard input) An OAuth token provided by Github for connecting to a git repository over HTTPS. See [https://help.github.com/articles/creating-an-access-token-for-command-line-use](https://help.github.com/articles/creating-an-access-token-for-command-line-use) for more information.
+- `--json-path`: The path to a JSON service account that Spinnaker will use as credentials. This is only needed if Spinnaker is not deployed on a Google Compute Engine VM, or needs permissions not afforded to the VM it is running on. See [https://cloud.google.com/compute/docs/access/service-accounts](https://cloud.google.com/compute/docs/access/service-accounts) for more information.
+- `--local-repository-directory`: A local directory to be used to stage source files for App Engine deployments within Spinnaker's Clouddriver microservice.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--omit-services`: A list of regular expressions. Any service matching one of these regexes will be ignored by Spinnaker.
+- `--omit-versions`: A list of regular expressions. Any version matching one of these regexes will be ignored by Spinnaker.
+- `--project`: The Google Cloud Platform project this Spinnaker account will manage.
+- `--read-permissions`: A user must have at least one of these roles in order to view this account's cloud resources.
+- `--remove-read-permission`: Remove this permission from the list of read permissions.
+- `--remove-required-group-membership`: Remove this group from the list of required group memberships.
+- `--remove-write-permission`: Remove this permission to from list of write permissions.
+- `--required-group-membership`: A user must be a member of at least one specified group in order to make changes to this account's cloud resources.
+- `--services`: A list of regular expressions. Any service matching one of these regexes will be indexed by Spinnaker.
+- `--ssh-known-hosts-file-path`: The path to a known_hosts file to be used when connecting with a remote git repository over SSH.
+- `--ssh-private-key-file-path`: The path to an SSH private key to be used when connecting with a remote git repository over SSH.
+- `--ssh-private-key-passphrase`: (_Sensitive data_ - user will be prompted on standard input) The passphrase to an SSH private key to be used when connecting with a remote git repository over SSH.
+- `--ssh-trust-unknown-hosts`: Enabling this flag will allow Spinnaker to connect with a remote git repository over SSH without verifying the server's IP address against a known_hosts file.
+- `--versions`: A list of regular expressions. Any version matching one of these regexes will be indexed by Spinnaker.
+- `--write-permissions`: A user must have at least one of these roles in order to make changes to this account's cloud resources.
---
+
## hal config provider appengine account get
Get the specified account details for the appengine provider.
#### Usage
+
```
hal config provider appengine account get ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider appengine account list
List the account names for the appengine provider.
#### Usage
+
```
hal config provider appengine account list [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider appengine disable
Set the appengine provider as disabled
#### Usage
+
```
hal config provider appengine disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider appengine edit
Edit Spinnaker's app engine configuration.
#### Usage
+
```
hal config provider appengine edit [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--gcloudPath`: The path to the gcloud executable on the machine running clouddriver.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--gcloudPath`: The path to the gcloud executable on the machine running clouddriver.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider appengine enable
Set the appengine provider as enabled
#### Usage
+
```
hal config provider appengine enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider aws
Manage and view Spinnaker configuration for the aws provider
#### Usage
+
```
hal config provider aws [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `account`: Manage and view Spinnaker configuration for the aws provider's account
- * `bakery`: Manage and view Spinnaker configuration for the aws provider's image bakery configuration.
- * `disable`: Set the aws provider as disabled
- * `edit`: Set provider-wide properties for the AWS provider
- * `enable`: Set the aws provider as enabled
- * `features`: Manage and view Spinnaker configuration for the aws features configuration.
+
+- `account`: Manage and view Spinnaker configuration for the aws provider's account
+- `bakery`: Manage and view Spinnaker configuration for the aws provider's image bakery configuration.
+- `disable`: Set the aws provider as disabled
+- `edit`: Set provider-wide properties for the AWS provider
+- `enable`: Set the aws provider as enabled
+- `features`: Manage and view Spinnaker configuration for the aws features configuration.
---
+
## hal config provider aws account
Manage and view Spinnaker configuration for the aws provider's account
#### Usage
+
```
hal config provider aws account ACCOUNT [parameters] [subcommands]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `add`: Add an account to the aws provider.
- * `delete`: Delete a specific aws account by name.
- * `edit`: Edit an account in the aws provider.
- * `get`: Get the specified account details for the aws provider.
- * `list`: List the account names for the aws provider.
+
+- `add`: Add an account to the aws provider.
+- `delete`: Delete a specific aws account by name.
+- `edit`: Edit an account in the aws provider.
+- `get`: Get the specified account details for the aws provider.
+- `list`: List the account names for the aws provider.
---
+
## hal config provider aws account add
Add an account to the aws provider.
#### Usage
+
```
hal config provider aws account add ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--account-id`: (*Required*) Your AWS account ID to manage. See [http://docs.aws.amazon.com/IAM/latest/UserGuide/console_account-alias.html](http://docs.aws.amazon.com/IAM/latest/UserGuide/console_account-alias.html) for more information.
- * `--assume-role`: (*Required*) If set, Halyard will configure a credentials provider that uses AWS Security Token Service to assume the specified role.
+
+- `--account-id`: (_Required_) Your AWS account ID to manage. See [http://docs.aws.amazon.com/IAM/latest/UserGuide/console_account-alias.html](http://docs.aws.amazon.com/IAM/latest/UserGuide/console_account-alias.html) for more information.
+- `--assume-role`: (_Required_) If set, Halyard will configure a credentials provider that uses AWS Security Token Service to assume the specified role.
Example: "user/spinnaker" or "role/spinnakerManaged"
- * `--default-key-pair`: Provide the name of the AWS key-pair to use. See [http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html) for more information.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--discovery`: The endpoint your Eureka discovery system is reachable at. See [https://github.com/Netflix/eureka](https://github.com/Netflix/eureka) for more information.
-Example: [http://{{region}}.eureka.url.to.use:8080/eureka-server/v2](http://{{region}}.eureka.url.to.use:8080/eureka-server/v2)
+- `--default-key-pair`: Provide the name of the AWS key-pair to use. See [http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html) for more information.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--discovery`: The endpoint your Eureka discovery system is reachable at. See [https://github.com/Netflix/eureka](https://github.com/Netflix/eureka) for more information.
+
+Example: [http://{{region}}.eureka.url.to.use:8080/eureka-server/v2](http://{{region}}.eureka.url.to.use:8080/eureka-server/v2)
Using {{region}} will make Spinnaker use AWS regions in the hostname to access discovery so that you can have discovery for multiple regions.
- * `--edda`: The endpoint Edda is reachable at. Edda is not a hard dependency of Spinnaker, but is helpful for reducing the request volume against AWS. See [https://github.com/Netflix/edda](https://github.com/Netflix/edda) for more information.
- * `--environment`: The environment name for the account. Many accounts can share the same environment (e.g. dev, test, prod)
- * `--launching-lifecycle-hook-default-result`: (*Default*: `ABANDON`) Defines the action the Auto Scaling group should take when the lifecycle hook timeout elapses or if an unexpected failure occurs. This parameter can be either CONTINUE or ABANDON. The default value is ABANDON.
- * `--launching-lifecycle-hook-heartbeat-timeout-seconds`: (*Default*: `3600`) Set the heartbeat timeout for the lifecycle hook. Instances can " +
- "remain in a wait state for a finite period of time. The default is one hour (3600 seconds).
- * `--launching-lifecycle-hook-notification-target-arn`: The ARN of the notification target that Amazon EC2 Auto Scaling uses to notify you when an instance is in the transition state for the lifecycle hook. This target can be either an SQS queue or an SNS topic.
- * `--launching-lifecycle-hook-role-arn`: The ARN of the IAM role that allows the Auto Scaling group to publish to the specified notification target, for example, an Amazon SNS topic or an Amazon SQS queue.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--read-permissions`: (*Default*: `[]`) A user must have at least one of these roles in order to view this account's cloud resources.
- * `--regions`: (*Default*: `[]`) The AWS regions this Spinnaker account will manage.
- * `--required-group-membership`: (*Default*: `[]`) A user must be a member of at least one specified group in order to make changes to this account's cloud resources.
- * `--terminating-lifecycle-hook-default-result`: (*Default*: `ABANDON`) Defines the action the Auto Scaling group should take when the lifecycle hook timeout elapses or if an unexpected failure occurs. This parameter can be either CONTINUE or ABANDON. The default value is ABANDON.
- * `--terminating-lifecycle-hook-heartbeat-timeout-seconds`: (*Default*: `3600`) Set the heartbeat timeout for the lifecycle hook. Instances can " +
- "remain in a wait state for a finite period of time. The default is one hour (3600 seconds).
- * `--terminating-lifecycle-hook-notification-target-arn`: The ARN of the notification target that Amazon EC2 Auto Scaling uses to notify you when an instance is in the transition state for the lifecycle hook. This target can be either an SQS queue or an SNS topic.
+- `--edda`: The endpoint Edda is reachable at. Edda is not a hard dependency of Spinnaker, but is helpful for reducing the request volume against AWS. See [https://github.com/Netflix/edda](https://github.com/Netflix/edda) for more information.
+- `--environment`: The environment name for the account. Many accounts can share the same environment (e.g. dev, test, prod)
+- `--launching-lifecycle-hook-default-result`: (_Default_: `ABANDON`) Defines the action the Auto Scaling group should take when the lifecycle hook timeout elapses or if an unexpected failure occurs. This parameter can be either CONTINUE or ABANDON. The default value is ABANDON.
+- `--launching-lifecycle-hook-heartbeat-timeout-seconds`: (_Default_: `3600`) Set the heartbeat timeout for the lifecycle hook. Instances can " +
+ "remain in a wait state for a finite period of time. The default is one hour (3600 seconds).
+- `--launching-lifecycle-hook-notification-target-arn`: The ARN of the notification target that Amazon EC2 Auto Scaling uses to notify you when an instance is in the transition state for the lifecycle hook. This target can be either an SQS queue or an SNS topic.
- * `--terminating-lifecycle-hook-role-arn`: The ARN of the IAM role that allows the Auto Scaling group to publish to the specified notification target, for example, an Amazon SNS topic or an Amazon SQS queue.
- * `--write-permissions`: (*Default*: `[]`) A user must have at least one of these roles in order to make changes to this account's cloud resources.
+- `--launching-lifecycle-hook-role-arn`: The ARN of the IAM role that allows the Auto Scaling group to publish to the specified notification target, for example, an Amazon SNS topic or an Amazon SQS queue.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--read-permissions`: (_Default_: `[]`) A user must have at least one of these roles in order to view this account's cloud resources.
+- `--regions`: (_Default_: `[]`) The AWS regions this Spinnaker account will manage.
+- `--required-group-membership`: (_Default_: `[]`) A user must be a member of at least one specified group in order to make changes to this account's cloud resources.
+- `--terminating-lifecycle-hook-default-result`: (_Default_: `ABANDON`) Defines the action the Auto Scaling group should take when the lifecycle hook timeout elapses or if an unexpected failure occurs. This parameter can be either CONTINUE or ABANDON. The default value is ABANDON.
+- `--terminating-lifecycle-hook-heartbeat-timeout-seconds`: (_Default_: `3600`) Set the heartbeat timeout for the lifecycle hook. Instances can " +
+ "remain in a wait state for a finite period of time. The default is one hour (3600 seconds).
+- `--terminating-lifecycle-hook-notification-target-arn`: The ARN of the notification target that Amazon EC2 Auto Scaling uses to notify you when an instance is in the transition state for the lifecycle hook. This target can be either an SQS queue or an SNS topic.
+- `--terminating-lifecycle-hook-role-arn`: The ARN of the IAM role that allows the Auto Scaling group to publish to the specified notification target, for example, an Amazon SNS topic or an Amazon SQS queue.
+- `--write-permissions`: (_Default_: `[]`) A user must have at least one of these roles in order to make changes to this account's cloud resources.
---
+
## hal config provider aws account delete
Delete a specific aws account by name.
#### Usage
+
```
hal config provider aws account delete ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider aws account edit
Edit an account in the aws provider.
#### Usage
+
```
hal config provider aws account edit ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--account-id`: Your AWS account ID to manage. See [http://docs.aws.amazon.com/IAM/latest/UserGuide/console_account-alias.html](http://docs.aws.amazon.com/IAM/latest/UserGuide/console_account-alias.html) for more information.
- * `--add-read-permission`: Add this permission to the list of read permissions.
- * `--add-region`: Add this region to the list of managed regions.
- * `--add-required-group-membership`: Add this group to the list of required group memberships.
- * `--add-write-permission`: Add this permission to the list of write permissions.
- * `--assume-role`: If set, Halyard will configure a credentials provider that uses AWS Security Token Service to assume the specified role.
+
+- `--account-id`: Your AWS account ID to manage. See [http://docs.aws.amazon.com/IAM/latest/UserGuide/console_account-alias.html](http://docs.aws.amazon.com/IAM/latest/UserGuide/console_account-alias.html) for more information.
+- `--add-read-permission`: Add this permission to the list of read permissions.
+- `--add-region`: Add this region to the list of managed regions.
+- `--add-required-group-membership`: Add this group to the list of required group memberships.
+- `--add-write-permission`: Add this permission to the list of write permissions.
+- `--assume-role`: If set, Halyard will configure a credentials provider that uses AWS Security Token Service to assume the specified role.
Example: "user/spinnaker" or "role/spinnakerManaged"
- * `--default-key-pair`: Provide the name of the AWS key-pair to use. See [http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html) for more information.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--discovery`: The endpoint your Eureka discovery system is reachable at. See [https://github.com/Netflix/eureka](https://github.com/Netflix/eureka) for more information.
-Example: [http://{{region}}.eureka.url.to.use:8080/eureka-server/v2](http://{{region}}.eureka.url.to.use:8080/eureka-server/v2)
+- `--default-key-pair`: Provide the name of the AWS key-pair to use. See [http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html) for more information.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--discovery`: The endpoint your Eureka discovery system is reachable at. See [https://github.com/Netflix/eureka](https://github.com/Netflix/eureka) for more information.
+
+Example: [http://{{region}}.eureka.url.to.use:8080/eureka-server/v2](http://{{region}}.eureka.url.to.use:8080/eureka-server/v2)
Using {{region}} will make Spinnaker use AWS regions in the hostname to access discovery so that you can have discovery for multiple regions.
- * `--edda`: The endpoint Edda is reachable at. Edda is not a hard dependency of Spinnaker, but is helpful for reducing the request volume against AWS. See [https://github.com/Netflix/edda](https://github.com/Netflix/edda) for more information.
- * `--environment`: The environment name for the account. Many accounts can share the same environment (e.g. dev, test, prod)
- * `--launching-lifecycle-hook-default-result`: (*Default*: `ABANDON`) Defines the action the Auto Scaling group should take when the lifecycle hook timeout elapses or if an unexpected failure occurs. This parameter can be either CONTINUE or ABANDON. The default value is ABANDON.
- * `--launching-lifecycle-hook-heartbeat-timeout-seconds`: (*Default*: `3600`) Set the heartbeat timeout for the lifecycle hook. Instances can " +
- "remain in a wait state for a finite period of time. The default is one hour (3600 seconds).
- * `--launching-lifecycle-hook-notification-target-arn`: The ARN of the notification target that Amazon EC2 Auto Scaling uses to notify you when an instance is in the transition state for the lifecycle hook. This target can be either an SQS queue or an SNS topic.
-
- * `--launching-lifecycle-hook-role-arn`: The ARN of the IAM role that allows the Auto Scaling group to publish to the specified notification target, for example, an Amazon SNS topic or an Amazon SQS queue.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--read-permissions`: A user must have at least one of these roles in order to view this account's cloud resources.
- * `--regions`: The AWS regions this Spinnaker account will manage.
- * `--remove-read-permission`: Remove this permission from the list of read permissions.
- * `--remove-region`: Remove this region from the list of managed regions.
- * `--remove-required-group-membership`: Remove this group from the list of required group memberships.
- * `--remove-write-permission`: Remove this permission to from list of write permissions.
- * `--required-group-membership`: A user must be a member of at least one specified group in order to make changes to this account's cloud resources.
- * `--terminating-lifecycle-hook-default-result`: (*Default*: `ABANDON`) Defines the action the Auto Scaling group should take when the lifecycle hook timeout elapses or if an unexpected failure occurs. This parameter can be either CONTINUE or ABANDON. The default value is ABANDON.
- * `--terminating-lifecycle-hook-heartbeat-timeout-seconds`: (*Default*: `3600`) Set the heartbeat timeout for the lifecycle hook. Instances can " +
- "remain in a wait state for a finite period of time. The default is one hour (3600 seconds).
- * `--terminating-lifecycle-hook-notification-target-arn`: The ARN of the notification target that Amazon EC2 Auto Scaling uses to notify you when an instance is in the transition state for the lifecycle hook. This target can be either an SQS queue or an SNS topic.
-
- * `--terminating-lifecycle-hook-role-arn`: The ARN of the IAM role that allows the Auto Scaling group to publish to the specified notification target, for example, an Amazon SNS topic or an Amazon SQS queue.
- * `--write-permissions`: A user must have at least one of these roles in order to make changes to this account's cloud resources.
+- `--edda`: The endpoint Edda is reachable at. Edda is not a hard dependency of Spinnaker, but is helpful for reducing the request volume against AWS. See [https://github.com/Netflix/edda](https://github.com/Netflix/edda) for more information.
+- `--environment`: The environment name for the account. Many accounts can share the same environment (e.g. dev, test, prod)
+- `--launching-lifecycle-hook-default-result`: (_Default_: `ABANDON`) Defines the action the Auto Scaling group should take when the lifecycle hook timeout elapses or if an unexpected failure occurs. This parameter can be either CONTINUE or ABANDON. The default value is ABANDON.
+- `--launching-lifecycle-hook-heartbeat-timeout-seconds`: (_Default_: `3600`) Set the heartbeat timeout for the lifecycle hook. Instances can " +
+ "remain in a wait state for a finite period of time. The default is one hour (3600 seconds).
+- `--launching-lifecycle-hook-notification-target-arn`: The ARN of the notification target that Amazon EC2 Auto Scaling uses to notify you when an instance is in the transition state for the lifecycle hook. This target can be either an SQS queue or an SNS topic.
+
+- `--launching-lifecycle-hook-role-arn`: The ARN of the IAM role that allows the Auto Scaling group to publish to the specified notification target, for example, an Amazon SNS topic or an Amazon SQS queue.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--read-permissions`: A user must have at least one of these roles in order to view this account's cloud resources.
+- `--regions`: The AWS regions this Spinnaker account will manage.
+- `--remove-read-permission`: Remove this permission from the list of read permissions.
+- `--remove-region`: Remove this region from the list of managed regions.
+- `--remove-required-group-membership`: Remove this group from the list of required group memberships.
+- `--remove-write-permission`: Remove this permission to from list of write permissions.
+- `--required-group-membership`: A user must be a member of at least one specified group in order to make changes to this account's cloud resources.
+- `--terminating-lifecycle-hook-default-result`: (_Default_: `ABANDON`) Defines the action the Auto Scaling group should take when the lifecycle hook timeout elapses or if an unexpected failure occurs. This parameter can be either CONTINUE or ABANDON. The default value is ABANDON.
+- `--terminating-lifecycle-hook-heartbeat-timeout-seconds`: (_Default_: `3600`) Set the heartbeat timeout for the lifecycle hook. Instances can " +
+ "remain in a wait state for a finite period of time. The default is one hour (3600 seconds).
+- `--terminating-lifecycle-hook-notification-target-arn`: The ARN of the notification target that Amazon EC2 Auto Scaling uses to notify you when an instance is in the transition state for the lifecycle hook. This target can be either an SQS queue or an SNS topic.
+
+- `--terminating-lifecycle-hook-role-arn`: The ARN of the IAM role that allows the Auto Scaling group to publish to the specified notification target, for example, an Amazon SNS topic or an Amazon SQS queue.
+- `--write-permissions`: A user must have at least one of these roles in order to make changes to this account's cloud resources.
---
+
## hal config provider aws account get
Get the specified account details for the aws provider.
#### Usage
+
```
hal config provider aws account get ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider aws account list
List the account names for the aws provider.
#### Usage
+
```
hal config provider aws account list [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider aws bakery
Manage and view Spinnaker configuration for the aws provider's image bakery configuration.
#### Usage
+
```
hal config provider aws bakery [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `edit`: Edit the aws provider's bakery default options.
+
+- `edit`: Edit the aws provider's bakery default options.
---
+
## hal config provider aws bakery edit
Edit the aws provider's bakery default options.
#### Usage
+
```
hal config provider aws bakery edit [parameters]
```
#### Parameters
- * `--aws-access-key`: The default access key used to communicate with AWS.
- * `--aws-associate-public-ip-address`: If using a non-default VPC, public IP addresses are not provided by default. If this is enabled, your new instance will get a Public IP.
- * `--aws-secret-key`: (*Sensitive data* - user will be prompted on standard input) The secret key used to communicate with AWS.
- * `--aws-subnet-id`: If using VPC, the default ID of the subnet, such as subnet-12345def, where Packer will launch the EC2 instance. This field is required if you are using a non-default VPC.
- * `--aws-vpc-id`: If launching into a VPC subnet, Packer needs the VPC ID in order to create a temporary security group within the VPC. Requires subnet_id to be set. If this default value is left blank, Packer will try to get the VPC ID from the subnet_id.
- * `--default-virtualization-type`: The default type of virtualization for the AMI you are building. This option must match the supported virtualization type of source_ami. Can be pv or hvm.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--template-file`: This is the name of the packer template that will be used to bake images from this base image. The template file must be found in this list [https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer](https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer), or supplied as described here: [https://spinnaker.io/setup/bakery/](https://spinnaker.io/setup/bakery/)
+- `--aws-access-key`: The default access key used to communicate with AWS.
+- `--aws-associate-public-ip-address`: If using a non-default VPC, public IP addresses are not provided by default. If this is enabled, your new instance will get a Public IP.
+- `--aws-secret-key`: (_Sensitive data_ - user will be prompted on standard input) The secret key used to communicate with AWS.
+- `--aws-subnet-id`: If using VPC, the default ID of the subnet, such as subnet-12345def, where Packer will launch the EC2 instance. This field is required if you are using a non-default VPC.
+- `--aws-vpc-id`: If launching into a VPC subnet, Packer needs the VPC ID in order to create a temporary security group within the VPC. Requires subnet_id to be set. If this default value is left blank, Packer will try to get the VPC ID from the subnet_id.
+- `--default-virtualization-type`: The default type of virtualization for the AMI you are building. This option must match the supported virtualization type of source_ami. Can be pv or hvm.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--template-file`: This is the name of the packer template that will be used to bake images from this base image. The template file must be found in this list [https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer](https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer), or supplied as described here: [https://spinnaker.io/setup/bakery/](https://spinnaker.io/setup/bakery/)
---
+
## hal config provider aws disable
Set the aws provider as disabled
#### Usage
+
```
hal config provider aws disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider aws edit
The AWS provider requires a central "Managing Account" to authenticate on behalf of other AWS accounts, or act as your sole, credential-based account. Since this configuration, as well as some defaults, span all AWS accounts, it is generally required to edit the AWS provider using this command.
#### Usage
+
```
hal config provider aws edit [parameters]
```
#### Parameters
- * `--access-key-id`: Your AWS Access Key ID. If not provided, Halyard/Spinnaker will try to find AWS credentials as described at [http://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/credentials.html#credentials-default](http://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/credentials.html#credentials-default). Note that if you are baking AMI's via Rosco, you may also need to set the access key on the AWS bakery default options.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--secret-access-key`: (*Sensitive data* - user will be prompted on standard input) Your AWS Secret Key.. Note that if you are baking AMI's via Rosco, you may also need to set the secret key on the AWS bakery default options.
+- `--access-key-id`: Your AWS Access Key ID. If not provided, Halyard/Spinnaker will try to find AWS credentials as described at [http://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/credentials.html#credentials-default](http://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/credentials.html#credentials-default). Note that if you are baking AMI's via Rosco, you may also need to set the access key on the AWS bakery default options.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--secret-access-key`: (_Sensitive data_ - user will be prompted on standard input) Your AWS Secret Key.. Note that if you are baking AMI's via Rosco, you may also need to set the secret key on the AWS bakery default options.
---
+
## hal config provider aws enable
Set the aws provider as enabled
#### Usage
+
```
hal config provider aws enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider aws features
Manage and view Spinnaker configuration for the aws features configuration.
#### Usage
+
```
hal config provider aws features [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `edit`: Edit features for AWS provider
+
+- `edit`: Edit features for AWS provider
---
+
## hal config provider aws features edit
Edit features for AWS provider
#### Usage
+
```
hal config provider aws features edit [parameters]
```
#### Parameters
- * `--cloud-formation`: (*Required*) Enable CloudFormation support for AWS.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--cloud-formation`: (_Required_) Enable CloudFormation support for AWS.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider azure
Manage and view Spinnaker configuration for the azure provider
#### Usage
+
```
hal config provider azure [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `account`: Manage and view Spinnaker configuration for the azure provider's account
- * `bakery`: Manage and view Spinnaker configuration for the azure provider's image bakery configuration.
- * `disable`: Set the azure provider as disabled
- * `enable`: Set the azure provider as enabled
+
+- `account`: Manage and view Spinnaker configuration for the azure provider's account
+- `bakery`: Manage and view Spinnaker configuration for the azure provider's image bakery configuration.
+- `disable`: Set the azure provider as disabled
+- `enable`: Set the azure provider as enabled
---
+
## hal config provider azure account
Manage and view Spinnaker configuration for the azure provider's account
#### Usage
+
```
hal config provider azure account ACCOUNT [parameters] [subcommands]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `add`: Add an account to the azure provider.
- * `delete`: Delete a specific azure account by name.
- * `edit`: Edit an account in the azure provider.
- * `get`: Get the specified account details for the azure provider.
- * `list`: List the account names for the azure provider.
+
+- `add`: Add an account to the azure provider.
+- `delete`: Delete a specific azure account by name.
+- `edit`: Edit an account in the azure provider.
+- `get`: Get the specified account details for the azure provider.
+- `list`: List the account names for the azure provider.
---
+
## hal config provider azure account add
Add an account to the azure provider.
#### Usage
+
```
hal config provider azure account add ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--app-key`: (*Required*) (*Sensitive data* - user will be prompted on standard input) The appKey (password) of your service principal.
- * `--client-id`: (*Required*) The clientId (also called appId) of your service principal.
- * `--default-key-vault`: (*Required*) The name of a KeyVault that contains the user name, password, and ssh public key used to create VMs
- * `--default-resource-group`: (*Required*) The default resource group to contain any non-application specific resources.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--environment`: The environment name for the account. Many accounts can share the same environment (e.g. dev, test, prod)
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--object-id`: The objectId of your service principal. This is only required if using Packer to bake Windows images.
- * `--packer-resource-group`: The resource group to use if baking images with Packer.
- * `--packer-storage-account`: The storage account to use if baking images with Packer.
- * `--read-permissions`: (*Default*: `[]`) A user must have at least one of these roles in order to view this account's cloud resources.
- * `--regions`: (*Default*: `[westus, eastus]`) The Azure regions this Spinnaker account will manage.
- * `--required-group-membership`: (*Default*: `[]`) A user must be a member of at least one specified group in order to make changes to this account's cloud resources.
- * `--subscription-id`: (*Required*) The subscriptionId that your service principal is assigned to.
- * `--tenant-id`: (*Required*) The tenantId that your service principal is assigned to.
- * `--useSshPublicKey`: (*Default*: `true`) Whether to use SSH public key to provision the linux vm. The default value is true which means using the ssh public key. Setting it to false means using the password instead.
- * `--write-permissions`: (*Default*: `[]`) A user must have at least one of these roles in order to make changes to this account's cloud resources.
+- `--app-key`: (_Required_) (_Sensitive data_ - user will be prompted on standard input) The appKey (password) of your service principal.
+- `--client-id`: (_Required_) The clientId (also called appId) of your service principal.
+- `--default-key-vault`: (_Required_) The name of a KeyVault that contains the user name, password, and ssh public key used to create VMs
+- `--default-resource-group`: (_Required_) The default resource group to contain any non-application specific resources.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--environment`: The environment name for the account. Many accounts can share the same environment (e.g. dev, test, prod)
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--object-id`: The objectId of your service principal. This is only required if using Packer to bake Windows images.
+- `--packer-resource-group`: The resource group to use if baking images with Packer.
+- `--packer-storage-account`: The storage account to use if baking images with Packer.
+- `--read-permissions`: (_Default_: `[]`) A user must have at least one of these roles in order to view this account's cloud resources.
+- `--regions`: (_Default_: `[westus, eastus]`) The Azure regions this Spinnaker account will manage.
+- `--required-group-membership`: (_Default_: `[]`) A user must be a member of at least one specified group in order to make changes to this account's cloud resources.
+- `--subscription-id`: (_Required_) The subscriptionId that your service principal is assigned to.
+- `--tenant-id`: (_Required_) The tenantId that your service principal is assigned to.
+- `--useSshPublicKey`: (_Default_: `true`) Whether to use SSH public key to provision the linux vm. The default value is true which means using the ssh public key. Setting it to false means using the password instead.
+- `--write-permissions`: (_Default_: `[]`) A user must have at least one of these roles in order to make changes to this account's cloud resources.
---
+
## hal config provider azure account delete
Delete a specific azure account by name.
#### Usage
+
```
hal config provider azure account delete ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider azure account edit
Edit an account in the azure provider.
#### Usage
+
```
hal config provider azure account edit ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--add-read-permission`: Add this permission to the list of read permissions.
- * `--add-required-group-membership`: Add this group to the list of required group memberships.
- * `--add-write-permission`: Add this permission to the list of write permissions.
- * `--app-key`: (*Sensitive data* - user will be prompted on standard input) The appKey (password) of your service principal.
- * `--client-id`: The clientId (also called appId) of your service principal.
- * `--default-key-vault`: The name of a KeyVault that contains the user name, password, and ssh public key used to create VMs
- * `--default-resource-group`: The default resource group to contain any non-application specific resources.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--environment`: The environment name for the account. Many accounts can share the same environment (e.g. dev, test, prod)
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--object-id`: The objectId of your service principal. This is only required if using Packer to bake Windows images.
- * `--packer-resource-group`: The resource group to use if baking images with Packer.
- * `--packer-storage-account`: The storage account to use if baking images with Packer.
- * `--read-permissions`: A user must have at least one of these roles in order to view this account's cloud resources.
- * `--regions`: The Azure regions this Spinnaker account will manage.
- * `--remove-read-permission`: Remove this permission from the list of read permissions.
- * `--remove-required-group-membership`: Remove this group from the list of required group memberships.
- * `--remove-write-permission`: Remove this permission to from list of write permissions.
- * `--required-group-membership`: A user must be a member of at least one specified group in order to make changes to this account's cloud resources.
- * `--subscription-id`: The subscriptionId that your service principal is assigned to.
- * `--tenant-id`: The tenantId that your service principal is assigned to.
- * `--useSshPublicKey`: Whether to use SSH public key to provision the linux vm. The default value is true which means using the ssh public key. Setting it to false means using the password instead.
- * `--write-permissions`: A user must have at least one of these roles in order to make changes to this account's cloud resources.
+- `--add-read-permission`: Add this permission to the list of read permissions.
+- `--add-required-group-membership`: Add this group to the list of required group memberships.
+- `--add-write-permission`: Add this permission to the list of write permissions.
+- `--app-key`: (_Sensitive data_ - user will be prompted on standard input) The appKey (password) of your service principal.
+- `--client-id`: The clientId (also called appId) of your service principal.
+- `--default-key-vault`: The name of a KeyVault that contains the user name, password, and ssh public key used to create VMs
+- `--default-resource-group`: The default resource group to contain any non-application specific resources.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--environment`: The environment name for the account. Many accounts can share the same environment (e.g. dev, test, prod)
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--object-id`: The objectId of your service principal. This is only required if using Packer to bake Windows images.
+- `--packer-resource-group`: The resource group to use if baking images with Packer.
+- `--packer-storage-account`: The storage account to use if baking images with Packer.
+- `--read-permissions`: A user must have at least one of these roles in order to view this account's cloud resources.
+- `--regions`: The Azure regions this Spinnaker account will manage.
+- `--remove-read-permission`: Remove this permission from the list of read permissions.
+- `--remove-required-group-membership`: Remove this group from the list of required group memberships.
+- `--remove-write-permission`: Remove this permission to from list of write permissions.
+- `--required-group-membership`: A user must be a member of at least one specified group in order to make changes to this account's cloud resources.
+- `--subscription-id`: The subscriptionId that your service principal is assigned to.
+- `--tenant-id`: The tenantId that your service principal is assigned to.
+- `--useSshPublicKey`: Whether to use SSH public key to provision the linux vm. The default value is true which means using the ssh public key. Setting it to false means using the password instead.
+- `--write-permissions`: A user must have at least one of these roles in order to make changes to this account's cloud resources.
---
+
## hal config provider azure account get
Get the specified account details for the azure provider.
#### Usage
+
```
hal config provider azure account get ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider azure account list
List the account names for the azure provider.
#### Usage
+
```
hal config provider azure account list [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider azure bakery
Manage and view Spinnaker configuration for the azure provider's image bakery configuration.
#### Usage
+
```
hal config provider azure bakery [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `base-image`: Manage and view Spinnaker configuration for the azure provider's base image.
- * `edit`: Edit the azure provider's bakery default options.
+
+- `base-image`: Manage and view Spinnaker configuration for the azure provider's base image.
+- `edit`: Edit the azure provider's bakery default options.
---
+
## hal config provider azure bakery base-image
Manage and view Spinnaker configuration for the azure provider's base image.
#### Usage
+
```
hal config provider azure bakery base-image [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `add`: Add a base image for the azure provider's bakery.
- * `delete`: Delete a specific azure base image by name.
- * `edit`: Edit a base image for the azure provider's bakery.
- * `get`: Get the specified base image details for the azure provider.
- * `list`: List the base image names for the azure provider.
+
+- `add`: Add a base image for the azure provider's bakery.
+- `delete`: Delete a specific azure base image by name.
+- `edit`: Edit a base image for the azure provider's bakery.
+- `get`: Get the specified base image details for the azure provider.
+- `list`: List the base image names for the azure provider.
---
+
## hal config provider azure bakery base-image add
Add a base image for the azure provider's bakery.
#### Usage
+
```
hal config provider azure bakery base-image add BASE-IMAGE [parameters]
```
#### Parameters
+
`BASE-IMAGE`: The name of the base image to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--detailed-description`: A long description to help human operators identify the image.
- * `--image-version`: The version of your base image. This defaults to 'latest' if not specified.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--offer`: (*Required*) The offer for your base image. See [https://aka.ms/azspinimage](https://aka.ms/azspinimage) to get a list of images.
- * `--package-type`: This is used to help Spinnaker's bakery download the build artifacts you supply it with. For example, specifying 'deb' indicates that your artifacts will need to be fetched from a debian repository.
- * `--publisher`: (*Required*) The Publisher name for your base image. See [https://aka.ms/azspinimage](https://aka.ms/azspinimage) to get a list of images.
- * `--short-description`: A short description to help human operators identify the image.
- * `--sku`: (*Required*) The SKU for your base image. See [https://aka.ms/azspinimage](https://aka.ms/azspinimage) to get a list of images.
- * `--template-file`: This is the name of the packer template that will be used to bake images from this base image. The template file must be found in this list [https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer](https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer), or supplied as described here: [https://spinnaker.io/setup/bakery/](https://spinnaker.io/setup/bakery/)
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--detailed-description`: A long description to help human operators identify the image.
+- `--image-version`: The version of your base image. This defaults to 'latest' if not specified.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--offer`: (_Required_) The offer for your base image. See [https://aka.ms/azspinimage](https://aka.ms/azspinimage) to get a list of images.
+- `--package-type`: This is used to help Spinnaker's bakery download the build artifacts you supply it with. For example, specifying 'deb' indicates that your artifacts will need to be fetched from a debian repository.
+- `--publisher`: (_Required_) The Publisher name for your base image. See [https://aka.ms/azspinimage](https://aka.ms/azspinimage) to get a list of images.
+- `--short-description`: A short description to help human operators identify the image.
+- `--sku`: (_Required_) The SKU for your base image. See [https://aka.ms/azspinimage](https://aka.ms/azspinimage) to get a list of images.
+- `--template-file`: This is the name of the packer template that will be used to bake images from this base image. The template file must be found in this list [https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer](https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer), or supplied as described here: [https://spinnaker.io/setup/bakery/](https://spinnaker.io/setup/bakery/)
---
+
## hal config provider azure bakery base-image delete
Delete a specific azure base image by name.
#### Usage
+
```
hal config provider azure bakery base-image delete BASE-IMAGE [parameters]
```
#### Parameters
+
`BASE-IMAGE`: The name of the base image to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider azure bakery base-image edit
Edit a base image for the azure provider's bakery.
#### Usage
+
```
hal config provider azure bakery base-image edit BASE-IMAGE [parameters]
```
#### Parameters
+
`BASE-IMAGE`: The name of the base image to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--detailed-description`: A long description to help human operators identify the image.
- * `--id`: This is the identifier used by your cloud to find this base image.
- * `--image-version`: The version of your base image. This defaults to 'latest' if not specified.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--offer`: The offer for your base image. See [https://aka.ms/azspinimage](https://aka.ms/azspinimage) to get a list of images.
- * `--package-type`: This is used to help Spinnaker's bakery download the build artifacts you supply it with. For example, specifying 'deb' indicates that your artifacts will need to be fetched from a debian repository.
- * `--publisher`: The Publisher name for your base image. See [https://aka.ms/azspinimage](https://aka.ms/azspinimage) to get a list of images.
- * `--short-description`: A short description to help human operators identify the image.
- * `--sku`: The SKU for your base image. See [https://aka.ms/azspinimage](https://aka.ms/azspinimage) to get a list of images.
- * `--template-file`: This is the name of the packer template that will be used to bake images from this base image. The template file must be found in this list [https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer](https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer), or supplied as described here: [https://spinnaker.io/setup/bakery/](https://spinnaker.io/setup/bakery/)
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--detailed-description`: A long description to help human operators identify the image.
+- `--id`: This is the identifier used by your cloud to find this base image.
+- `--image-version`: The version of your base image. This defaults to 'latest' if not specified.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--offer`: The offer for your base image. See [https://aka.ms/azspinimage](https://aka.ms/azspinimage) to get a list of images.
+- `--package-type`: This is used to help Spinnaker's bakery download the build artifacts you supply it with. For example, specifying 'deb' indicates that your artifacts will need to be fetched from a debian repository.
+- `--publisher`: The Publisher name for your base image. See [https://aka.ms/azspinimage](https://aka.ms/azspinimage) to get a list of images.
+- `--short-description`: A short description to help human operators identify the image.
+- `--sku`: The SKU for your base image. See [https://aka.ms/azspinimage](https://aka.ms/azspinimage) to get a list of images.
+- `--template-file`: This is the name of the packer template that will be used to bake images from this base image. The template file must be found in this list [https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer](https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer), or supplied as described here: [https://spinnaker.io/setup/bakery/](https://spinnaker.io/setup/bakery/)
---
+
## hal config provider azure bakery base-image get
Get the specified base image details for the azure provider.
#### Usage
+
```
hal config provider azure bakery base-image get BASE-IMAGE [parameters]
```
#### Parameters
+
`BASE-IMAGE`: The name of the base image to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider azure bakery base-image list
List the base image names for the azure provider.
#### Usage
+
```
hal config provider azure bakery base-image list [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider azure bakery edit
Edit the azure provider's bakery default options.
#### Usage
+
```
hal config provider azure bakery edit [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider azure disable
Set the azure provider as disabled
#### Usage
+
```
hal config provider azure disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider azure enable
Set the azure provider as enabled
#### Usage
+
```
hal config provider azure enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider cloudfoundry
Manage and view Spinnaker configuration for the cloudfoundry provider
#### Usage
+
```
hal config provider cloudfoundry [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `account`: Manage and view Spinnaker configuration for the cloudfoundry provider's account
- * `disable`: Set the cloudfoundry provider as disabled
- * `enable`: Set the cloudfoundry provider as enabled
+
+- `account`: Manage and view Spinnaker configuration for the cloudfoundry provider's account
+- `disable`: Set the cloudfoundry provider as disabled
+- `enable`: Set the cloudfoundry provider as enabled
---
+
## hal config provider cloudfoundry account
Manage and view Spinnaker configuration for the cloudfoundry provider's account
#### Usage
+
```
hal config provider cloudfoundry account ACCOUNT [parameters] [subcommands]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `add`: Add an account to the cloudfoundry provider.
- * `delete`: Delete a specific cloudfoundry account by name.
- * `edit`: Edit an account in the cloudfoundry provider.
- * `get`: Get the specified account details for the cloudfoundry provider.
- * `list`: List the account names for the cloudfoundry provider.
+
+- `add`: Add an account to the cloudfoundry provider.
+- `delete`: Delete a specific cloudfoundry account by name.
+- `edit`: Edit an account in the cloudfoundry provider.
+- `get`: Get the specified account details for the cloudfoundry provider.
+- `list`: List the account names for the cloudfoundry provider.
---
+
## hal config provider cloudfoundry account add
Add an account to the cloudfoundry provider.
#### Usage
+
```
hal config provider cloudfoundry account add ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--api-host, --api`: (*Required*) Host of the CloudFoundry Foundation API endpoint ie. `api.sys.somesystem.com`
- * `--apps-manager-url, --apps-manager-uri, --appsManagerUri`: HTTP(S) URL of the Apps Manager application for the CloudFoundry Foundation ie. `[https://apps.sys.somesystem.com](https://apps.sys.somesystem.com)`
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--environment`: The environment name for the account. Many accounts can share the same environment (e.g. dev, test, prod)
- * `--metrics-url, --metrics-uri, --metricsUri`: HTTP(S) URL of the metrics application for the CloudFoundry Foundation ie. `[https://metrics.sys.somesystem.com](https://metrics.sys.somesystem.com)`
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--password`: (*Required*) Password for the account to use on for this CloudFoundry Foundation
- * `--read-permissions`: (*Default*: `[]`) A user must have at least one of these roles in order to view this account's cloud resources.
- * `--required-group-membership`: (*Default*: `[]`) A user must be a member of at least one specified group in order to make changes to this account's cloud resources.
- * `--skip-ssl-validation`: (*Default*: `false`) Skip SSL server certificate validation of the API endpoint
- * `--user`: (*Required*) User name for the account to use on for this CloudFoundry Foundation
- * `--write-permissions`: (*Default*: `[]`) A user must have at least one of these roles in order to make changes to this account's cloud resources.
+- `--api-host, --api`: (_Required_) Host of the CloudFoundry Foundation API endpoint ie. `api.sys.somesystem.com`
+- `--apps-manager-url, --apps-manager-uri, --appsManagerUri`: HTTP(S) URL of the Apps Manager application for the CloudFoundry Foundation ie. `[https://apps.sys.somesystem.com](https://apps.sys.somesystem.com)`
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--environment`: The environment name for the account. Many accounts can share the same environment (e.g. dev, test, prod)
+- `--metrics-url, --metrics-uri, --metricsUri`: HTTP(S) URL of the metrics application for the CloudFoundry Foundation ie. `[https://metrics.sys.somesystem.com](https://metrics.sys.somesystem.com)`
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--password`: (_Required_) Password for the account to use on for this CloudFoundry Foundation
+- `--read-permissions`: (_Default_: `[]`) A user must have at least one of these roles in order to view this account's cloud resources.
+- `--required-group-membership`: (_Default_: `[]`) A user must be a member of at least one specified group in order to make changes to this account's cloud resources.
+- `--skip-ssl-validation`: (_Default_: `false`) Skip SSL server certificate validation of the API endpoint
+- `--user`: (_Required_) User name for the account to use on for this CloudFoundry Foundation
+- `--write-permissions`: (_Default_: `[]`) A user must have at least one of these roles in order to make changes to this account's cloud resources.
---
+
## hal config provider cloudfoundry account delete
Delete a specific cloudfoundry account by name.
#### Usage
+
```
hal config provider cloudfoundry account delete ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider cloudfoundry account edit
Edit an account in the cloudfoundry provider.
#### Usage
+
```
hal config provider cloudfoundry account edit ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--add-read-permission`: Add this permission to the list of read permissions.
- * `--add-required-group-membership`: Add this group to the list of required group memberships.
- * `--add-write-permission`: Add this permission to the list of write permissions.
- * `--api-host, --api`: Host of the CloudFoundry Foundation API endpoint ie. `api.sys.somesystem.com`
- * `--apps-manager-url, --apps-manager-uri, --appsManagerUri`: HTTP(S) URL of the Apps Manager application for the CloudFoundry Foundation ie. `[https://apps.sys.somesystem.com](https://apps.sys.somesystem.com)`
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--environment`: The environment name for the account. Many accounts can share the same environment (e.g. dev, test, prod)
- * `--metrics-url, --metrics-uri, --metricsUri`: HTTP(S) URL of the metrics application for the CloudFoundry Foundation ie. `[https://metrics.sys.somesystem.com](https://metrics.sys.somesystem.com)`
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--password`: Password for the account to use on for this CloudFoundry Foundation
- * `--read-permissions`: A user must have at least one of these roles in order to view this account's cloud resources.
- * `--remove-read-permission`: Remove this permission from the list of read permissions.
- * `--remove-required-group-membership`: Remove this group from the list of required group memberships.
- * `--remove-write-permission`: Remove this permission to from list of write permissions.
- * `--required-group-membership`: A user must be a member of at least one specified group in order to make changes to this account's cloud resources.
- * `--skip-ssl-validation`: (*Default*: `false`) Skip SSL server certificate validation of the API endpoint
- * `--user`: User name for the account to use on for this CloudFoundry Foundation
- * `--write-permissions`: A user must have at least one of these roles in order to make changes to this account's cloud resources.
+- `--add-read-permission`: Add this permission to the list of read permissions.
+- `--add-required-group-membership`: Add this group to the list of required group memberships.
+- `--add-write-permission`: Add this permission to the list of write permissions.
+- `--api-host, --api`: Host of the CloudFoundry Foundation API endpoint ie. `api.sys.somesystem.com`
+- `--apps-manager-url, --apps-manager-uri, --appsManagerUri`: HTTP(S) URL of the Apps Manager application for the CloudFoundry Foundation ie. `[https://apps.sys.somesystem.com](https://apps.sys.somesystem.com)`
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--environment`: The environment name for the account. Many accounts can share the same environment (e.g. dev, test, prod)
+- `--metrics-url, --metrics-uri, --metricsUri`: HTTP(S) URL of the metrics application for the CloudFoundry Foundation ie. `[https://metrics.sys.somesystem.com](https://metrics.sys.somesystem.com)`
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--password`: Password for the account to use on for this CloudFoundry Foundation
+- `--read-permissions`: A user must have at least one of these roles in order to view this account's cloud resources.
+- `--remove-read-permission`: Remove this permission from the list of read permissions.
+- `--remove-required-group-membership`: Remove this group from the list of required group memberships.
+- `--remove-write-permission`: Remove this permission to from list of write permissions.
+- `--required-group-membership`: A user must be a member of at least one specified group in order to make changes to this account's cloud resources.
+- `--skip-ssl-validation`: (_Default_: `false`) Skip SSL server certificate validation of the API endpoint
+- `--user`: User name for the account to use on for this CloudFoundry Foundation
+- `--write-permissions`: A user must have at least one of these roles in order to make changes to this account's cloud resources.
---
+
## hal config provider cloudfoundry account get
Get the specified account details for the cloudfoundry provider.
#### Usage
+
```
hal config provider cloudfoundry account get ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider cloudfoundry account list
List the account names for the cloudfoundry provider.
#### Usage
+
```
hal config provider cloudfoundry account list [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider cloudfoundry disable
Set the cloudfoundry provider as disabled
#### Usage
+
```
hal config provider cloudfoundry disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider cloudfoundry enable
Set the cloudfoundry provider as enabled
#### Usage
+
```
hal config provider cloudfoundry enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider dcos
Manage and view Spinnaker configuration for the dcos provider
#### Usage
+
```
hal config provider dcos [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `account`: Manage and view Spinnaker configuration for the dcos provider's account
- * `cluster`: Manage and view Spinnaker configuration for the dcos provider's cluster
- * `disable`: Set the dcos provider as disabled
- * `enable`: Set the dcos provider as enabled
+
+- `account`: Manage and view Spinnaker configuration for the dcos provider's account
+- `cluster`: Manage and view Spinnaker configuration for the dcos provider's cluster
+- `disable`: Set the dcos provider as disabled
+- `enable`: Set the dcos provider as enabled
---
+
## hal config provider dcos account
Manage and view Spinnaker configuration for the dcos provider's account
#### Usage
+
```
hal config provider dcos account ACCOUNT [parameters] [subcommands]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `add`: Add an account to the dcos provider.
- * `delete`: Delete a specific dcos account by name.
- * `edit`: Edit an account in the dcos provider.
- * `get`: Get the specified account details for the dcos provider.
- * `list`: List the account names for the dcos provider.
+
+- `add`: Add an account to the dcos provider.
+- `delete`: Delete a specific dcos account by name.
+- `edit`: Edit an account in the dcos provider.
+- `get`: Get the specified account details for the dcos provider.
+- `list`: List the account names for the dcos provider.
---
+
## hal config provider dcos account add
Add an account to the dcos provider.
#### Usage
+
```
hal config provider dcos account add ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--cluster`: (*Required*) Reference to the name of the cluster from the set of clusters defined for this provider
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--docker-registries`: (*Default*: `[]`) (*Required*) Provide the list of docker registries to use with this DC/OS account
- * `--environment`: The environment name for the account. Many accounts can share the same environment (e.g. dev, test, prod)
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--password`: Password for a user account
- * `--read-permissions`: (*Default*: `[]`) A user must have at least one of these roles in order to view this account's cloud resources.
- * `--required-group-membership`: (*Default*: `[]`) A user must be a member of at least one specified group in order to make changes to this account's cloud resources.
- * `--service-key-file`: Path to a file containing the secret key for service account authentication
- * `--uid`: (*Required*) User or service account identifier
- * `--write-permissions`: (*Default*: `[]`) A user must have at least one of these roles in order to make changes to this account's cloud resources.
+- `--cluster`: (_Required_) Reference to the name of the cluster from the set of clusters defined for this provider
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--docker-registries`: (_Default_: `[]`) (_Required_) Provide the list of docker registries to use with this DC/OS account
+- `--environment`: The environment name for the account. Many accounts can share the same environment (e.g. dev, test, prod)
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--password`: Password for a user account
+- `--read-permissions`: (_Default_: `[]`) A user must have at least one of these roles in order to view this account's cloud resources.
+- `--required-group-membership`: (_Default_: `[]`) A user must be a member of at least one specified group in order to make changes to this account's cloud resources.
+- `--service-key-file`: Path to a file containing the secret key for service account authentication
+- `--uid`: (_Required_) User or service account identifier
+- `--write-permissions`: (_Default_: `[]`) A user must have at least one of these roles in order to make changes to this account's cloud resources.
---
+
## hal config provider dcos account delete
Delete a specific dcos account by name.
#### Usage
+
```
hal config provider dcos account delete ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider dcos account edit
Edit an account in the dcos provider.
#### Usage
+
```
hal config provider dcos account edit ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--add-docker-registry`: Add this docker registry to the list of docker registries to use as a source of images.
- * `--add-read-permission`: Add this permission to the list of read permissions.
- * `--add-required-group-membership`: Add this group to the list of required group memberships.
- * `--add-write-permission`: Add this permission to the list of write permissions.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--docker-registries`: (*Default*: `[]`) Provide the list of docker registries to use with this DC/OS account
- * `--environment`: The environment name for the account. Many accounts can share the same environment (e.g. dev, test, prod)
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--read-permissions`: A user must have at least one of these roles in order to view this account's cloud resources.
- * `--remove-credential`: (*Default*: `[]`) Provide the cluster name and uid of credentials to remove: --remove-credential my-cluster my-user
- * `--remove-docker-registry`: Remove this docker registry from the list of docker registries to use as a source of images.
- * `--remove-read-permission`: Remove this permission from the list of read permissions.
- * `--remove-required-group-membership`: Remove this group from the list of required group memberships.
- * `--remove-write-permission`: Remove this permission to from list of write permissions.
- * `--required-group-membership`: A user must be a member of at least one specified group in order to make changes to this account's cloud resources.
- * `--update-service-credential`: (*Default*: `[]`) A DC/OS cluster service account credential in 3 parts: cluster-name uid serviceKey
- * `--update-user-credential`: (*Default*: `[]`) A DC/OS cluster user credential in 3 parts: cluster-name uid password
- * `--write-permissions`: A user must have at least one of these roles in order to make changes to this account's cloud resources.
+- `--add-docker-registry`: Add this docker registry to the list of docker registries to use as a source of images.
+- `--add-read-permission`: Add this permission to the list of read permissions.
+- `--add-required-group-membership`: Add this group to the list of required group memberships.
+- `--add-write-permission`: Add this permission to the list of write permissions.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--docker-registries`: (_Default_: `[]`) Provide the list of docker registries to use with this DC/OS account
+- `--environment`: The environment name for the account. Many accounts can share the same environment (e.g. dev, test, prod)
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--read-permissions`: A user must have at least one of these roles in order to view this account's cloud resources.
+- `--remove-credential`: (_Default_: `[]`) Provide the cluster name and uid of credentials to remove: --remove-credential my-cluster my-user
+- `--remove-docker-registry`: Remove this docker registry from the list of docker registries to use as a source of images.
+- `--remove-read-permission`: Remove this permission from the list of read permissions.
+- `--remove-required-group-membership`: Remove this group from the list of required group memberships.
+- `--remove-write-permission`: Remove this permission to from list of write permissions.
+- `--required-group-membership`: A user must be a member of at least one specified group in order to make changes to this account's cloud resources.
+- `--update-service-credential`: (_Default_: `[]`) A DC/OS cluster service account credential in 3 parts: cluster-name uid serviceKey
+- `--update-user-credential`: (_Default_: `[]`) A DC/OS cluster user credential in 3 parts: cluster-name uid password
+- `--write-permissions`: A user must have at least one of these roles in order to make changes to this account's cloud resources.
---
+
## hal config provider dcos account get
Get the specified account details for the dcos provider.
#### Usage
+
```
hal config provider dcos account get ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider dcos account list
List the account names for the dcos provider.
#### Usage
+
```
hal config provider dcos account list [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider dcos cluster
Manage and view Spinnaker configuration for the dcos provider's cluster
#### Usage
+
```
hal config provider dcos cluster CLUSTER [parameters] [subcommands]
```
#### Parameters
+
`CLUSTER`: The name of the cluster to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `add`: Manage and view Spinnaker configuration for the dcos provider's cluster
- * `delete`: Delete a specific dcos cluster by name.
- * `edit`: Manage and view Spinnaker configuration for the dcos provider's cluster
- * `get`: Get the specified cluster details for the dcos provider.
- * `list`: List the cluster names for the dcos provider.
+
+- `add`: Manage and view Spinnaker configuration for the dcos provider's cluster
+- `delete`: Delete a specific dcos cluster by name.
+- `edit`: Manage and view Spinnaker configuration for the dcos provider's cluster
+- `get`: Get the specified cluster details for the dcos provider.
+- `list`: List the cluster names for the dcos provider.
---
+
## hal config provider dcos cluster add
Manage and view Spinnaker configuration for the dcos provider's cluster
#### Usage
+
```
hal config provider dcos cluster add CLUSTER [parameters]
```
#### Parameters
+
`CLUSTER`: The name of the cluster to operate on.
- * `--ca-cert-file`: Root certificate file to trust for connections to the cluster
- * `--dcos-url`: (*Required*) URL of the endpoint for the DC/OS cluster's admin router.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--lb-account-secret`: Name of the secret to use for allowing marathon-lb to authenticate with the cluster. Only necessary for clusters with strict or permissive security.
- * `--lb-image`: Marathon-lb image to use when creating a load balancer with Spinnaker
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--skip-tls-verify`: Set this flag to disable verification of certificates from the cluster (insecure)
+- `--ca-cert-file`: Root certificate file to trust for connections to the cluster
+- `--dcos-url`: (_Required_) URL of the endpoint for the DC/OS cluster's admin router.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--lb-account-secret`: Name of the secret to use for allowing marathon-lb to authenticate with the cluster. Only necessary for clusters with strict or permissive security.
+- `--lb-image`: Marathon-lb image to use when creating a load balancer with Spinnaker
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--skip-tls-verify`: Set this flag to disable verification of certificates from the cluster (insecure)
---
+
## hal config provider dcos cluster delete
Delete a specific dcos cluster by name.
#### Usage
+
```
hal config provider dcos cluster delete CLUSTER [parameters]
```
#### Parameters
+
`CLUSTER`: The name of the cluster to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider dcos cluster edit
Manage and view Spinnaker configuration for the dcos provider's cluster
#### Usage
+
```
hal config provider dcos cluster edit CLUSTER [parameters]
```
#### Parameters
+
`CLUSTER`: The name of the cluster to operate on.
- * `--ca-cert-file`: Root certificate file to trust for connections to the cluster
- * `--dcos-url`: URL of the endpoint for the DC/OS cluster's admin router.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--lb-account-secret`: Name of the secret to use for allowing marathon-lb to authenticate with the cluster. Only necessary for clusters with strict or permissive security.
- * `--lb-image`: Marathon-lb image to use when creating a load balancer with Spinnaker
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--remove-ca-cert-file`: (*Default*: `false`) Remove the CA certificate file for this cluster
- * `--remove-lb`: (*Default*: `false`) Remove the load balancer attributes for this cluster
- * `--set-skip-tls-verify`: Set this flag to disable verification of certificates from the cluster (insecure)
+- `--ca-cert-file`: Root certificate file to trust for connections to the cluster
+- `--dcos-url`: URL of the endpoint for the DC/OS cluster's admin router.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--lb-account-secret`: Name of the secret to use for allowing marathon-lb to authenticate with the cluster. Only necessary for clusters with strict or permissive security.
+- `--lb-image`: Marathon-lb image to use when creating a load balancer with Spinnaker
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--remove-ca-cert-file`: (_Default_: `false`) Remove the CA certificate file for this cluster
+- `--remove-lb`: (_Default_: `false`) Remove the load balancer attributes for this cluster
+- `--set-skip-tls-verify`: Set this flag to disable verification of certificates from the cluster (insecure)
---
+
## hal config provider dcos cluster get
Get the specified cluster details for the dcos provider.
#### Usage
+
```
hal config provider dcos cluster get CLUSTER [parameters]
```
#### Parameters
+
`CLUSTER`: The name of the cluster to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider dcos cluster list
List the cluster names for the dcos provider.
#### Usage
+
```
hal config provider dcos cluster list CLUSTER [parameters]
```
#### Parameters
+
`CLUSTER`: The name of the cluster to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider dcos disable
Set the dcos provider as disabled
#### Usage
+
```
hal config provider dcos disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider dcos enable
Set the dcos provider as enabled
#### Usage
+
```
hal config provider dcos enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider docker-registry
Manage and view Spinnaker configuration for the dockerRegistry provider
#### Usage
+
```
hal config provider docker-registry [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `account`: Manage and view Spinnaker configuration for the dockerRegistry provider's account
- * `disable`: Set the dockerRegistry provider as disabled
- * `enable`: Set the dockerRegistry provider as enabled
+
+- `account`: Manage and view Spinnaker configuration for the dockerRegistry provider's account
+- `disable`: Set the dockerRegistry provider as disabled
+- `enable`: Set the dockerRegistry provider as enabled
---
+
## hal config provider docker-registry account
Manage and view Spinnaker configuration for the dockerRegistry provider's account
#### Usage
+
```
hal config provider docker-registry account ACCOUNT [parameters] [subcommands]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `add`: Add an account to the dockerRegistry provider.
- * `delete`: Delete a specific dockerRegistry account by name.
- * `edit`: Edit an account in the dockerRegistry provider.
- * `get`: Get the specified account details for the dockerRegistry provider.
- * `list`: List the account names for the dockerRegistry provider.
+
+- `add`: Add an account to the dockerRegistry provider.
+- `delete`: Delete a specific dockerRegistry account by name.
+- `edit`: Edit an account in the dockerRegistry provider.
+- `get`: Get the specified account details for the dockerRegistry provider.
+- `list`: List the account names for the dockerRegistry provider.
---
+
## hal config provider docker-registry account add
Add an account to the dockerRegistry provider.
#### Usage
+
```
hal config provider docker-registry account add ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--address`: (*Default*: `gcr.io`) (*Required*) The registry address you want to pull and deploy images from. For example:
-
- index.docker.io - DockerHub
- quay.io - Quay
- gcr.io - Google Container Registry (GCR)
- [us|eu|asia].gcr.io - Regional GCR
- localhost - Locally deployed registry
- * `--cache-interval-seconds`: (*Default*: `30`) How many seconds elapse between polling your docker registry. Certain registries are sensitive to over-polling, and larger intervals (e.g. 10 minutes = 600 seconds) are desirable if you're seeing rate limiting.
- * `--cache-threads`: (*Default*: `1`) How many threads to cache all provided repos on. Really only useful if you have a ton of repos.
- * `--client-timeout-millis`: (*Default*: `60000`) Timeout time in milliseconds for this repository.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--email`: (*Default*: `fake.email@spinnaker.io`) Your docker registry email (often this only needs to be well-formed, rather than be a real address)
- * `--environment`: The environment name for the account. Many accounts can share the same environment (e.g. dev, test, prod)
- * `--insecure-registry`: (*Default*: `false`) Treat the docker registry as insecure (don't validate the ssl cert).
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--paginate-size`: (*Default*: `100`) Paginate size for the docker repository _catalog endpoint.
- * `--password`: (*Sensitive data* - user will be prompted on standard input) Your docker registry password
- * `--password-command`: Command to retrieve docker token/password, commands must be available in environment
- * `--password-file`: The path to a file containing your docker password in plaintext (not a docker/config.json file)
- * `--read-permissions`: (*Default*: `[]`) A user must have at least one of these roles in order to view this account's cloud resources.
- * `--repositories`: (*Default*: `[]`) An optional list of repositories to cache images from. If not provided, Spinnaker will attempt to read accessible repositories from the registries _catalog endpoint
- * `--required-group-membership`: (*Default*: `[]`) A user must be a member of at least one specified group in order to make changes to this account's cloud resources.
- * `--sort-tags-by-date`: (*Default*: `false`) Sort tags by creation date. Not recommended for use with large registries; sorting performance scales poorly due to limitations of the Docker V2 API.
- * `--track-digests`: (*Default*: `false`) Track digest changes. This is not recommended as it consumes a high QPM, and most registries are flaky.
- * `--username`: Your docker registry username
- * `--write-permissions`: (*Default*: `[]`) A user must have at least one of these roles in order to make changes to this account's cloud resources.
+- `--address`: (_Default_: `gcr.io`) (_Required_) The registry address you want to pull and deploy images from. For example:
+
+index.docker.io - DockerHub
+quay.io - Quay
+gcr.io - Google Container Registry (GCR)
+[us|eu|asia].gcr.io - Regional GCR
+localhost - Locally deployed registry
+
+- `--cache-interval-seconds`: (_Default_: `30`) How many seconds elapse between polling your docker registry. Certain registries are sensitive to over-polling, and larger intervals (e.g. 10 minutes = 600 seconds) are desirable if you're seeing rate limiting.
+- `--cache-threads`: (_Default_: `1`) How many threads to cache all provided repos on. Really only useful if you have a ton of repos.
+- `--client-timeout-millis`: (_Default_: `60000`) Timeout time in milliseconds for this repository.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--email`: (_Default_: `fake.email@spinnaker.io`) Your docker registry email (often this only needs to be well-formed, rather than be a real address)
+- `--environment`: The environment name for the account. Many accounts can share the same environment (e.g. dev, test, prod)
+- `--insecure-registry`: (_Default_: `false`) Treat the docker registry as insecure (don't validate the ssl cert).
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--paginate-size`: (_Default_: `100`) Paginate size for the docker repository \_catalog endpoint.
+- `--password`: (_Sensitive data_ - user will be prompted on standard input) Your docker registry password
+- `--password-command`: Command to retrieve docker token/password, commands must be available in environment
+- `--password-file`: The path to a file containing your docker password in plaintext (not a docker/config.json file)
+- `--read-permissions`: (_Default_: `[]`) A user must have at least one of these roles in order to view this account's cloud resources.
+- `--repositories`: (_Default_: `[]`) An optional list of repositories to cache images from. If not provided, Spinnaker will attempt to read accessible repositories from the registries \_catalog endpoint
+- `--required-group-membership`: (_Default_: `[]`) A user must be a member of at least one specified group in order to make changes to this account's cloud resources.
+- `--sort-tags-by-date`: (_Default_: `false`) Sort tags by creation date. Not recommended for use with large registries; sorting performance scales poorly due to limitations of the Docker V2 API.
+- `--track-digests`: (_Default_: `false`) Track digest changes. This is not recommended as it consumes a high QPM, and most registries are flaky.
+- `--username`: Your docker registry username
+- `--write-permissions`: (_Default_: `[]`) A user must have at least one of these roles in order to make changes to this account's cloud resources.
---
+
## hal config provider docker-registry account delete
Delete a specific dockerRegistry account by name.
#### Usage
+
```
hal config provider docker-registry account delete ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider docker-registry account edit
Edit an account in the dockerRegistry provider.
#### Usage
+
```
hal config provider docker-registry account edit ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--add-read-permission`: Add this permission to the list of read permissions.
- * `--add-repository`: Add this repository to the list of repositories to cache images from.
- * `--add-required-group-membership`: Add this group to the list of required group memberships.
- * `--add-write-permission`: Add this permission to the list of write permissions.
- * `--address`: The registry address you want to pull and deploy images from. For example:
-
- index.docker.io - DockerHub
- quay.io - Quay
- gcr.io - Google Container Registry (GCR)
- [us|eu|asia].gcr.io - Regional GCR
- localhost - Locally deployed registry
- * `--cache-interval-seconds`: How many seconds elapse between polling your docker registry. Certain registries are sensitive to over-polling, and larger intervals (e.g. 10 minutes = 600 seconds) are desirable if you're seeing rate limiting.
- * `--cache-threads`: How many threads to cache all provided repos on. Really only useful if you have a ton of repos.
- * `--client-timeout-millis`: Timeout time in milliseconds for this repository.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--email`: Your docker registry email (often this only needs to be well-formed, rather than be a real address)
- * `--environment`: The environment name for the account. Many accounts can share the same environment (e.g. dev, test, prod)
- * `--insecure-registry`: Treat the docker registry as insecure (don't validate the ssl cert).
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--paginate-size`: Paginate size for the docker repository _catalog endpoint.
- * `--password`: (*Sensitive data* - user will be prompted on standard input) Your docker registry password
- * `--password-command`: Command to retrieve docker token/password, commands must be available in environment
- * `--password-file`: The path to a file containing your docker password in plaintext (not a docker/config.json file)
- * `--read-permissions`: A user must have at least one of these roles in order to view this account's cloud resources.
- * `--remove-read-permission`: Remove this permission from the list of read permissions.
- * `--remove-repository`: Remove this repository to the list of repositories to cache images from.
- * `--remove-required-group-membership`: Remove this group from the list of required group memberships.
- * `--remove-write-permission`: Remove this permission to from list of write permissions.
- * `--repositories`: (*Default*: `[]`) An optional list of repositories to cache images from. If not provided, Spinnaker will attempt to read accessible repositories from the registries _catalog endpoint
- * `--required-group-membership`: A user must be a member of at least one specified group in order to make changes to this account's cloud resources.
- * `--sort-tags-by-date`: Sort tags by creation date. Not recommended for use with large registries; sorting performance scales poorly due to limitations of the Docker V2 API.
- * `--track-digests`: Track digest changes. This is not recommended as it consumes a high QPM, and most registries are flaky.
- * `--username`: Your docker registry username
- * `--write-permissions`: A user must have at least one of these roles in order to make changes to this account's cloud resources.
+- `--add-read-permission`: Add this permission to the list of read permissions.
+- `--add-repository`: Add this repository to the list of repositories to cache images from.
+- `--add-required-group-membership`: Add this group to the list of required group memberships.
+- `--add-write-permission`: Add this permission to the list of write permissions.
+- `--address`: The registry address you want to pull and deploy images from. For example:
+
+index.docker.io - DockerHub
+quay.io - Quay
+gcr.io - Google Container Registry (GCR)
+[us|eu|asia].gcr.io - Regional GCR
+localhost - Locally deployed registry
+
+- `--cache-interval-seconds`: How many seconds elapse between polling your docker registry. Certain registries are sensitive to over-polling, and larger intervals (e.g. 10 minutes = 600 seconds) are desirable if you're seeing rate limiting.
+- `--cache-threads`: How many threads to cache all provided repos on. Really only useful if you have a ton of repos.
+- `--client-timeout-millis`: Timeout time in milliseconds for this repository.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--email`: Your docker registry email (often this only needs to be well-formed, rather than be a real address)
+- `--environment`: The environment name for the account. Many accounts can share the same environment (e.g. dev, test, prod)
+- `--insecure-registry`: Treat the docker registry as insecure (don't validate the ssl cert).
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--paginate-size`: Paginate size for the docker repository \_catalog endpoint.
+- `--password`: (_Sensitive data_ - user will be prompted on standard input) Your docker registry password
+- `--password-command`: Command to retrieve docker token/password, commands must be available in environment
+- `--password-file`: The path to a file containing your docker password in plaintext (not a docker/config.json file)
+- `--read-permissions`: A user must have at least one of these roles in order to view this account's cloud resources.
+- `--remove-read-permission`: Remove this permission from the list of read permissions.
+- `--remove-repository`: Remove this repository to the list of repositories to cache images from.
+- `--remove-required-group-membership`: Remove this group from the list of required group memberships.
+- `--remove-write-permission`: Remove this permission to from list of write permissions.
+- `--repositories`: (_Default_: `[]`) An optional list of repositories to cache images from. If not provided, Spinnaker will attempt to read accessible repositories from the registries \_catalog endpoint
+- `--required-group-membership`: A user must be a member of at least one specified group in order to make changes to this account's cloud resources.
+- `--sort-tags-by-date`: Sort tags by creation date. Not recommended for use with large registries; sorting performance scales poorly due to limitations of the Docker V2 API.
+- `--track-digests`: Track digest changes. This is not recommended as it consumes a high QPM, and most registries are flaky.
+- `--username`: Your docker registry username
+- `--write-permissions`: A user must have at least one of these roles in order to make changes to this account's cloud resources.
---
+
## hal config provider docker-registry account get
Get the specified account details for the dockerRegistry provider.
#### Usage
+
```
hal config provider docker-registry account get ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider docker-registry account list
List the account names for the dockerRegistry provider.
#### Usage
+
```
hal config provider docker-registry account list [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider docker-registry disable
Set the dockerRegistry provider as disabled
#### Usage
+
```
hal config provider docker-registry disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider docker-registry enable
Set the dockerRegistry provider as enabled
#### Usage
+
```
hal config provider docker-registry enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider ecs
Manage and view Spinnaker configuration for the ecs provider
#### Usage
+
```
hal config provider ecs [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `account`: Manage and view Spinnaker configuration for the ecs provider's account
- * `disable`: Set the ecs provider as disabled
- * `enable`: Set the ecs provider as enabled
+
+- `account`: Manage and view Spinnaker configuration for the ecs provider's account
+- `disable`: Set the ecs provider as disabled
+- `enable`: Set the ecs provider as enabled
---
+
## hal config provider ecs account
Manage and view Spinnaker configuration for the ecs provider's account
#### Usage
+
```
hal config provider ecs account ACCOUNT [parameters] [subcommands]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `add`: Add an account to the ecs provider.
- * `delete`: Delete a specific ecs account by name.
- * `edit`: Edit an account in the ecs provider.
- * `get`: Get the specified account details for the ecs provider.
- * `list`: List the account names for the ecs provider.
+
+- `add`: Add an account to the ecs provider.
+- `delete`: Delete a specific ecs account by name.
+- `edit`: Edit an account in the ecs provider.
+- `get`: Get the specified account details for the ecs provider.
+- `list`: List the account names for the ecs provider.
---
+
## hal config provider ecs account add
Add an account to the ecs provider.
#### Usage
+
```
hal config provider ecs account add ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--aws-account`: (*Required*) Provide the name of the AWS account associated with this ECS account.See [https://github.com/spinnaker/clouddriver/blob/master/clouddriver-ecs/README.md](https://github.com/spinnaker/clouddriver/blob/master/clouddriver-ecs/README.md) for more information.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--environment`: The environment name for the account. Many accounts can share the same environment (e.g. dev, test, prod)
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--read-permissions`: (*Default*: `[]`) A user must have at least one of these roles in order to view this account's cloud resources.
- * `--required-group-membership`: (*Default*: `[]`) A user must be a member of at least one specified group in order to make changes to this account's cloud resources.
- * `--write-permissions`: (*Default*: `[]`) A user must have at least one of these roles in order to make changes to this account's cloud resources.
+- `--aws-account`: (_Required_) Provide the name of the AWS account associated with this ECS account.See [https://github.com/spinnaker/clouddriver/blob/master/clouddriver-ecs/README.md](https://github.com/spinnaker/clouddriver/blob/master/clouddriver-ecs/README.md) for more information.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--environment`: The environment name for the account. Many accounts can share the same environment (e.g. dev, test, prod)
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--read-permissions`: (_Default_: `[]`) A user must have at least one of these roles in order to view this account's cloud resources.
+- `--required-group-membership`: (_Default_: `[]`) A user must be a member of at least one specified group in order to make changes to this account's cloud resources.
+- `--write-permissions`: (_Default_: `[]`) A user must have at least one of these roles in order to make changes to this account's cloud resources.
---
+
## hal config provider ecs account delete
Delete a specific ecs account by name.
#### Usage
+
```
hal config provider ecs account delete ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider ecs account edit
Edit an account in the ecs provider.
#### Usage
+
```
hal config provider ecs account edit ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--add-read-permission`: Add this permission to the list of read permissions.
- * `--add-required-group-membership`: Add this group to the list of required group memberships.
- * `--add-write-permission`: Add this permission to the list of write permissions.
- * `--aws-account`: Provide the name of the AWS account associated with this ECS account.See [https://github.com/spinnaker/clouddriver/blob/master/clouddriver-ecs/README.md](https://github.com/spinnaker/clouddriver/blob/master/clouddriver-ecs/README.md) for more information.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--environment`: The environment name for the account. Many accounts can share the same environment (e.g. dev, test, prod)
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--read-permissions`: A user must have at least one of these roles in order to view this account's cloud resources.
- * `--remove-read-permission`: Remove this permission from the list of read permissions.
- * `--remove-required-group-membership`: Remove this group from the list of required group memberships.
- * `--remove-write-permission`: Remove this permission to from list of write permissions.
- * `--required-group-membership`: A user must be a member of at least one specified group in order to make changes to this account's cloud resources.
- * `--write-permissions`: A user must have at least one of these roles in order to make changes to this account's cloud resources.
+- `--add-read-permission`: Add this permission to the list of read permissions.
+- `--add-required-group-membership`: Add this group to the list of required group memberships.
+- `--add-write-permission`: Add this permission to the list of write permissions.
+- `--aws-account`: Provide the name of the AWS account associated with this ECS account.See [https://github.com/spinnaker/clouddriver/blob/master/clouddriver-ecs/README.md](https://github.com/spinnaker/clouddriver/blob/master/clouddriver-ecs/README.md) for more information.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--environment`: The environment name for the account. Many accounts can share the same environment (e.g. dev, test, prod)
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--read-permissions`: A user must have at least one of these roles in order to view this account's cloud resources.
+- `--remove-read-permission`: Remove this permission from the list of read permissions.
+- `--remove-required-group-membership`: Remove this group from the list of required group memberships.
+- `--remove-write-permission`: Remove this permission to from list of write permissions.
+- `--required-group-membership`: A user must be a member of at least one specified group in order to make changes to this account's cloud resources.
+- `--write-permissions`: A user must have at least one of these roles in order to make changes to this account's cloud resources.
---
+
## hal config provider ecs account get
Get the specified account details for the ecs provider.
#### Usage
+
```
hal config provider ecs account get ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider ecs account list
List the account names for the ecs provider.
#### Usage
+
```
hal config provider ecs account list [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider ecs disable
Set the ecs provider as disabled
#### Usage
+
```
hal config provider ecs disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider ecs enable
Set the ecs provider as enabled
#### Usage
+
```
hal config provider ecs enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider google
Manage and view Spinnaker configuration for the google provider
#### Usage
+
```
hal config provider google [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `account`: Manage and view Spinnaker configuration for the google provider's account
- * `bakery`: Manage and view Spinnaker configuration for the google provider's image bakery configuration.
- * `disable`: Set the google provider as disabled
- * `edit`: Set provider-wide properties for the Google provider
- * `enable`: Set the google provider as enabled
+
+- `account`: Manage and view Spinnaker configuration for the google provider's account
+- `bakery`: Manage and view Spinnaker configuration for the google provider's image bakery configuration.
+- `disable`: Set the google provider as disabled
+- `edit`: Set provider-wide properties for the Google provider
+- `enable`: Set the google provider as enabled
---
+
## hal config provider google account
Manage and view Spinnaker configuration for the google provider's account
#### Usage
+
```
hal config provider google account ACCOUNT [parameters] [subcommands]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `add`: Add an account to the google provider.
- * `delete`: Delete a specific google account by name.
- * `edit`: Edit an account in the google provider.
- * `get`: Get the specified account details for the google provider.
- * `list`: List the account names for the google provider.
+
+- `add`: Add an account to the google provider.
+- `delete`: Delete a specific google account by name.
+- `edit`: Edit an account in the google provider.
+- `get`: Get the specified account details for the google provider.
+- `list`: List the account names for the google provider.
---
+
## hal config provider google account add
Add an account to the google provider.
#### Usage
+
```
hal config provider google account add ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--alpha-listed`: (*Default*: `false`) Enable this flag if your project has access to alpha features and you want Spinnaker to take advantage of them.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--environment`: The environment name for the account. Many accounts can share the same environment (e.g. dev, test, prod)
- * `--image-projects`: (*Default*: `[]`) A list of Google Cloud Platform projects Spinnaker will be able to cache and deploy images from. When this is omitted, it defaults to the current project. Each project must have granted the IAM role `compute.imageUser` to the service account associated with the json key used by this account, as well as to the 'Google APIs service account' automatically created for the project being managed (should look similar to `12345678912@cloudservices.gserviceaccount.com`). See [https://cloud.google.com/compute/docs/images/sharing-images-across-projects](https://cloud.google.com/compute/docs/images/sharing-images-across-projects) for more information about sharing images across GCP projects.
- * `--json-path`: The path to a JSON service account that Spinnaker will use as credentials. This is only needed if Spinnaker is not deployed on a Google Compute Engine VM, or needs permissions not afforded to the VM it is running on. See [https://cloud.google.com/compute/docs/access/service-accounts](https://cloud.google.com/compute/docs/access/service-accounts) for more information.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--project`: (*Required*) The Google Cloud Platform project this Spinnaker account will manage.
- * `--read-permissions`: (*Default*: `[]`) A user must have at least one of these roles in order to view this account's cloud resources.
- * `--regions`: A list of regions for caching and mutating calls. This overwrites any default-regions set on the provider.
- * `--required-group-membership`: (*Default*: `[]`) A user must be a member of at least one specified group in order to make changes to this account's cloud resources.
- * `--user-data`: The path to user data template file. Spinnaker has the ability to inject userdata into generated instance templates. The mechanism is via a template file that is token replaced to provide some specifics about the deployment. See [https://github.com/spinnaker/clouddriver/blob/master/clouddriver-aws/UserData.md](https://github.com/spinnaker/clouddriver/blob/master/clouddriver-aws/UserData.md) for more information.
- * `--write-permissions`: (*Default*: `[]`) A user must have at least one of these roles in order to make changes to this account's cloud resources.
+- `--alpha-listed`: (_Default_: `false`) Enable this flag if your project has access to alpha features and you want Spinnaker to take advantage of them.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--environment`: The environment name for the account. Many accounts can share the same environment (e.g. dev, test, prod)
+- `--image-projects`: (_Default_: `[]`) A list of Google Cloud Platform projects Spinnaker will be able to cache and deploy images from. When this is omitted, it defaults to the current project. Each project must have granted the IAM role `compute.imageUser` to the service account associated with the json key used by this account, as well as to the 'Google APIs service account' automatically created for the project being managed (should look similar to `12345678912@cloudservices.gserviceaccount.com`). See [https://cloud.google.com/compute/docs/images/sharing-images-across-projects](https://cloud.google.com/compute/docs/images/sharing-images-across-projects) for more information about sharing images across GCP projects.
+- `--json-path`: The path to a JSON service account that Spinnaker will use as credentials. This is only needed if Spinnaker is not deployed on a Google Compute Engine VM, or needs permissions not afforded to the VM it is running on. See [https://cloud.google.com/compute/docs/access/service-accounts](https://cloud.google.com/compute/docs/access/service-accounts) for more information.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--project`: (_Required_) The Google Cloud Platform project this Spinnaker account will manage.
+- `--read-permissions`: (_Default_: `[]`) A user must have at least one of these roles in order to view this account's cloud resources.
+- `--regions`: A list of regions for caching and mutating calls. This overwrites any default-regions set on the provider.
+- `--required-group-membership`: (_Default_: `[]`) A user must be a member of at least one specified group in order to make changes to this account's cloud resources.
+- `--user-data`: The path to user data template file. Spinnaker has the ability to inject userdata into generated instance templates. The mechanism is via a template file that is token replaced to provide some specifics about the deployment. See [https://github.com/spinnaker/clouddriver/blob/master/clouddriver-aws/UserData.md](https://github.com/spinnaker/clouddriver/blob/master/clouddriver-aws/UserData.md) for more information.
+- `--write-permissions`: (_Default_: `[]`) A user must have at least one of these roles in order to make changes to this account's cloud resources.
---
+
## hal config provider google account delete
Delete a specific google account by name.
#### Usage
+
```
hal config provider google account delete ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider google account edit
Edit an account in the google provider.
#### Usage
+
```
hal config provider google account edit ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--add-image-project`: Add this image project to the list of image projects to cache and deploy images from.
- * `--add-read-permission`: Add this permission to the list of read permissions.
- * `--add-region`: Add this region to the list of regions for caching and mutating calls.
- * `--add-required-group-membership`: Add this group to the list of required group memberships.
- * `--add-write-permission`: Add this permission to the list of write permissions.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--environment`: The environment name for the account. Many accounts can share the same environment (e.g. dev, test, prod)
- * `--image-projects`: A list of Google Cloud Platform projects Spinnaker will be able to cache and deploy images from. When this is omitted, it defaults to the current project. Each project must have granted the IAM role `compute.imageUser` to the service account associated with the json key used by this account, as well as to the 'Google APIs service account' automatically created for the project being managed (should look similar to `12345678912@cloudservices.gserviceaccount.com`). See [https://cloud.google.com/compute/docs/images/sharing-images-across-projects](https://cloud.google.com/compute/docs/images/sharing-images-across-projects) for more information about sharing images across GCP projects.
- * `--json-path`: The path to a JSON service account that Spinnaker will use as credentials. This is only needed if Spinnaker is not deployed on a Google Compute Engine VM, or needs permissions not afforded to the VM it is running on. See [https://cloud.google.com/compute/docs/access/service-accounts](https://cloud.google.com/compute/docs/access/service-accounts) for more information.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--project`: The Google Cloud Platform project this Spinnaker account will manage.
- * `--read-permissions`: A user must have at least one of these roles in order to view this account's cloud resources.
- * `--regions`: A list of regions for caching and mutating calls. This overwrites any default-regions set on the provider.
- * `--remove-image-project`: Remove this image project from the list of image projects to cache and deploy images from.
- * `--remove-read-permission`: Remove this permission from the list of read permissions.
- * `--remove-region`: Remove this region from the list of regions for caching and mutating calls.
- * `--remove-required-group-membership`: Remove this group from the list of required group memberships.
- * `--remove-write-permission`: Remove this permission to from list of write permissions.
- * `--required-group-membership`: A user must be a member of at least one specified group in order to make changes to this account's cloud resources.
- * `--set-alpha-listed`: Enable this flag if your project has access to alpha features and you want Spinnaker to take advantage of them.
- * `--user-data`: The path to user data template file. Spinnaker has the ability to inject userdata into generated instance templates. The mechanism is via a template file that is token replaced to provide some specifics about the deployment. See [https://github.com/spinnaker/clouddriver/blob/master/clouddriver-aws/UserData.md](https://github.com/spinnaker/clouddriver/blob/master/clouddriver-aws/UserData.md) for more information.
- * `--write-permissions`: A user must have at least one of these roles in order to make changes to this account's cloud resources.
+- `--add-image-project`: Add this image project to the list of image projects to cache and deploy images from.
+- `--add-read-permission`: Add this permission to the list of read permissions.
+- `--add-region`: Add this region to the list of regions for caching and mutating calls.
+- `--add-required-group-membership`: Add this group to the list of required group memberships.
+- `--add-write-permission`: Add this permission to the list of write permissions.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--environment`: The environment name for the account. Many accounts can share the same environment (e.g. dev, test, prod)
+- `--image-projects`: A list of Google Cloud Platform projects Spinnaker will be able to cache and deploy images from. When this is omitted, it defaults to the current project. Each project must have granted the IAM role `compute.imageUser` to the service account associated with the json key used by this account, as well as to the 'Google APIs service account' automatically created for the project being managed (should look similar to `12345678912@cloudservices.gserviceaccount.com`). See [https://cloud.google.com/compute/docs/images/sharing-images-across-projects](https://cloud.google.com/compute/docs/images/sharing-images-across-projects) for more information about sharing images across GCP projects.
+- `--json-path`: The path to a JSON service account that Spinnaker will use as credentials. This is only needed if Spinnaker is not deployed on a Google Compute Engine VM, or needs permissions not afforded to the VM it is running on. See [https://cloud.google.com/compute/docs/access/service-accounts](https://cloud.google.com/compute/docs/access/service-accounts) for more information.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--project`: The Google Cloud Platform project this Spinnaker account will manage.
+- `--read-permissions`: A user must have at least one of these roles in order to view this account's cloud resources.
+- `--regions`: A list of regions for caching and mutating calls. This overwrites any default-regions set on the provider.
+- `--remove-image-project`: Remove this image project from the list of image projects to cache and deploy images from.
+- `--remove-read-permission`: Remove this permission from the list of read permissions.
+- `--remove-region`: Remove this region from the list of regions for caching and mutating calls.
+- `--remove-required-group-membership`: Remove this group from the list of required group memberships.
+- `--remove-write-permission`: Remove this permission to from list of write permissions.
+- `--required-group-membership`: A user must be a member of at least one specified group in order to make changes to this account's cloud resources.
+- `--set-alpha-listed`: Enable this flag if your project has access to alpha features and you want Spinnaker to take advantage of them.
+- `--user-data`: The path to user data template file. Spinnaker has the ability to inject userdata into generated instance templates. The mechanism is via a template file that is token replaced to provide some specifics about the deployment. See [https://github.com/spinnaker/clouddriver/blob/master/clouddriver-aws/UserData.md](https://github.com/spinnaker/clouddriver/blob/master/clouddriver-aws/UserData.md) for more information.
+- `--write-permissions`: A user must have at least one of these roles in order to make changes to this account's cloud resources.
---
+
## hal config provider google account get
Get the specified account details for the google provider.
#### Usage
+
```
hal config provider google account get ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider google account list
List the account names for the google provider.
#### Usage
+
```
hal config provider google account list [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider google bakery
Manage and view Spinnaker configuration for the google provider's image bakery configuration.
#### Usage
+
```
hal config provider google bakery [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `base-image`: Manage and view Spinnaker configuration for the google provider's base image.
- * `edit`: Edit the google provider's bakery default options.
+
+- `base-image`: Manage and view Spinnaker configuration for the google provider's base image.
+- `edit`: Edit the google provider's bakery default options.
---
+
## hal config provider google bakery base-image
Manage and view Spinnaker configuration for the google provider's base image.
#### Usage
+
```
hal config provider google bakery base-image [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `add`: Add a base image for the google provider's bakery.
- * `delete`: Delete a specific google base image by name.
- * `edit`: Edit a base image for the google provider's bakery.
- * `get`: Get the specified base image details for the google provider.
- * `list`: List the base image names for the google provider.
+
+- `add`: Add a base image for the google provider's bakery.
+- `delete`: Delete a specific google base image by name.
+- `edit`: Edit a base image for the google provider's bakery.
+- `get`: Get the specified base image details for the google provider.
+- `list`: List the base image names for the google provider.
---
+
## hal config provider google bakery base-image add
Add a base image for the google provider's bakery.
#### Usage
+
```
hal config provider google bakery base-image add BASE-IMAGE [parameters]
```
#### Parameters
+
`BASE-IMAGE`: The name of the base image to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--detailed-description`: A long description to help human operators identify the image.
- * `--is-image-family`: (*Default*: `false`) todo(duftler) I couldn't find a description on the packer website of what this is.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--package-type`: This is used to help Spinnaker's bakery download the build artifacts you supply it with. For example, specifying 'deb' indicates that your artifacts will need to be fetched from a debian repository.
- * `--short-description`: A short description to help human operators identify the image.
- * `--source-image`: The source image. If both source image and source image family are set, source image will take precedence.
- * `--source-image-family`: The source image family to create the image from. The newest, non-deprecated image is used.
- * `--template-file`: This is the name of the packer template that will be used to bake images from this base image. The template file must be found in this list [https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer](https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer), or supplied as described here: [https://spinnaker.io/setup/bakery/](https://spinnaker.io/setup/bakery/)
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--detailed-description`: A long description to help human operators identify the image.
+- `--is-image-family`: (_Default_: `false`) todo(duftler) I couldn't find a description on the packer website of what this is.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--package-type`: This is used to help Spinnaker's bakery download the build artifacts you supply it with. For example, specifying 'deb' indicates that your artifacts will need to be fetched from a debian repository.
+- `--short-description`: A short description to help human operators identify the image.
+- `--source-image`: The source image. If both source image and source image family are set, source image will take precedence.
+- `--source-image-family`: The source image family to create the image from. The newest, non-deprecated image is used.
+- `--template-file`: This is the name of the packer template that will be used to bake images from this base image. The template file must be found in this list [https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer](https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer), or supplied as described here: [https://spinnaker.io/setup/bakery/](https://spinnaker.io/setup/bakery/)
---
+
## hal config provider google bakery base-image delete
Delete a specific google base image by name.
#### Usage
+
```
hal config provider google bakery base-image delete BASE-IMAGE [parameters]
```
#### Parameters
+
`BASE-IMAGE`: The name of the base image to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider google bakery base-image edit
Edit a base image for the google provider's bakery.
#### Usage
+
```
hal config provider google bakery base-image edit BASE-IMAGE [parameters]
```
#### Parameters
+
`BASE-IMAGE`: The name of the base image to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--detailed-description`: A long description to help human operators identify the image.
- * `--id`: This is the identifier used by your cloud to find this base image.
- * `--is-image-family`: todo(duftler) I couldn't find a description on the packer website of what this is.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--package-type`: This is used to help Spinnaker's bakery download the build artifacts you supply it with. For example, specifying 'deb' indicates that your artifacts will need to be fetched from a debian repository.
- * `--short-description`: A short description to help human operators identify the image.
- * `--source-image`: The source image. If both source image and source image family are set, source image will take precedence.
- * `--source-image-family`: The source image family to create the image from. The newest, non-deprecated image is used.
- * `--template-file`: This is the name of the packer template that will be used to bake images from this base image. The template file must be found in this list [https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer](https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer), or supplied as described here: [https://spinnaker.io/setup/bakery/](https://spinnaker.io/setup/bakery/)
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--detailed-description`: A long description to help human operators identify the image.
+- `--id`: This is the identifier used by your cloud to find this base image.
+- `--is-image-family`: todo(duftler) I couldn't find a description on the packer website of what this is.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--package-type`: This is used to help Spinnaker's bakery download the build artifacts you supply it with. For example, specifying 'deb' indicates that your artifacts will need to be fetched from a debian repository.
+- `--short-description`: A short description to help human operators identify the image.
+- `--source-image`: The source image. If both source image and source image family are set, source image will take precedence.
+- `--source-image-family`: The source image family to create the image from. The newest, non-deprecated image is used.
+- `--template-file`: This is the name of the packer template that will be used to bake images from this base image. The template file must be found in this list [https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer](https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer), or supplied as described here: [https://spinnaker.io/setup/bakery/](https://spinnaker.io/setup/bakery/)
---
+
## hal config provider google bakery base-image get
Get the specified base image details for the google provider.
#### Usage
+
```
hal config provider google bakery base-image get BASE-IMAGE [parameters]
```
#### Parameters
+
`BASE-IMAGE`: The name of the base image to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider google bakery base-image list
List the base image names for the google provider.
#### Usage
+
```
hal config provider google bakery base-image list [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider google bakery edit
Edit the google provider's bakery default options.
#### Usage
+
```
hal config provider google bakery edit [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--network`: Set the default network your images will be baked in.
- * `--network-project-id`: Set the default project id for the network and subnet to use for the VM baking your image.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--template-file`: This is the name of the packer template that will be used to bake images from this base image. The template file must be found in this list [https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer](https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer), or supplied as described here: [https://spinnaker.io/setup/bakery/](https://spinnaker.io/setup/bakery/)
- * `--use-internal-ip`: Use the internal rather than external IP of the VM baking your image.
- * `--zone`: Set the default zone your images will be baked in.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--network`: Set the default network your images will be baked in.
+- `--network-project-id`: Set the default project id for the network and subnet to use for the VM baking your image.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--template-file`: This is the name of the packer template that will be used to bake images from this base image. The template file must be found in this list [https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer](https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer), or supplied as described here: [https://spinnaker.io/setup/bakery/](https://spinnaker.io/setup/bakery/)
+- `--use-internal-ip`: Use the internal rather than external IP of the VM baking your image.
+- `--zone`: Set the default zone your images will be baked in.
---
+
## hal config provider google disable
Set the google provider as disabled
#### Usage
+
```
hal config provider google disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider google edit
You can edit the list of default regions used in caching and mutating calls here. This list will become the default for all accounts, unlessspecifically overridden on a per-account basis.
#### Usage
+
```
hal config provider google edit [parameters]
```
#### Parameters
- * `--add-default-region`: Add this region to the list of regions for caching and mutating calls.
- * `--default-regions`: A list of regions for caching and mutating calls, applied to all accounts unless overridden.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--remove-default-region`: Remove this region from the list of regions for caching and mutating calls.
+- `--add-default-region`: Add this region to the list of regions for caching and mutating calls.
+- `--default-regions`: A list of regions for caching and mutating calls, applied to all accounts unless overridden.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--remove-default-region`: Remove this region from the list of regions for caching and mutating calls.
---
+
## hal config provider google enable
Set the google provider as enabled
#### Usage
+
```
hal config provider google enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider huaweicloud
Manage and view Spinnaker configuration for the huaweicloud provider
#### Usage
+
```
hal config provider huaweicloud [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `account`: Manage and view Spinnaker configuration for the huaweicloud provider's account
- * `bakery`: Manage and view Spinnaker configuration for the huaweicloud provider's image bakery configuration.
- * `disable`: Set the huaweicloud provider as disabled
- * `enable`: Set the huaweicloud provider as enabled
+
+- `account`: Manage and view Spinnaker configuration for the huaweicloud provider's account
+- `bakery`: Manage and view Spinnaker configuration for the huaweicloud provider's image bakery configuration.
+- `disable`: Set the huaweicloud provider as disabled
+- `enable`: Set the huaweicloud provider as enabled
---
+
## hal config provider huaweicloud account
Manage and view Spinnaker configuration for the huaweicloud provider's account
#### Usage
+
```
hal config provider huaweicloud account ACCOUNT [parameters] [subcommands]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `add`: Add an account to the huaweicloud provider.
- * `delete`: Delete a specific huaweicloud account by name.
- * `edit`: Edit an account in the huaweicloud provider.
- * `get`: Get the specified account details for the huaweicloud provider.
- * `list`: List the account names for the huaweicloud provider.
+
+- `add`: Add an account to the huaweicloud provider.
+- `delete`: Delete a specific huaweicloud account by name.
+- `edit`: Edit an account in the huaweicloud provider.
+- `get`: Get the specified account details for the huaweicloud provider.
+- `list`: List the account names for the huaweicloud provider.
---
+
## hal config provider huaweicloud account add
Add an account to the huaweicloud provider.
#### Usage
+
```
hal config provider huaweicloud account add ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--account-type`: The type of account.
- * `--auth-url`: (*Required*) The auth url of cloud.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--domain-name`: (*Required*) The domain name of the cloud.
- * `--environment`: The environment name for the account. Many accounts can share the same environment (e.g. dev, test, prod)
- * `--insecure`: (*Default*: `false`) Disable certificate validation on SSL connections. Needed if certificates are self signed. Default false.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--password`: (*Required*) (*Sensitive data* - user will be prompted on standard input) (Sensitive data - user will be prompted on standard input) The password used to access cloud.
- * `--project-name`: (*Required*) The name of the project within the cloud.
- * `--read-permissions`: (*Default*: `[]`) A user must have at least one of these roles in order to view this account's cloud resources.
- * `--regions`: (*Default*: `[]`) (*Required*) The region(s) of the cloud.
- * `--required-group-membership`: (*Default*: `[]`) A user must be a member of at least one specified group in order to make changes to this account's cloud resources.
- * `--username`: (*Required*) The username used to access cloud.
- * `--write-permissions`: (*Default*: `[]`) A user must have at least one of these roles in order to make changes to this account's cloud resources.
+- `--account-type`: The type of account.
+- `--auth-url`: (_Required_) The auth url of cloud.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--domain-name`: (_Required_) The domain name of the cloud.
+- `--environment`: The environment name for the account. Many accounts can share the same environment (e.g. dev, test, prod)
+- `--insecure`: (_Default_: `false`) Disable certificate validation on SSL connections. Needed if certificates are self signed. Default false.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--password`: (_Required_) (_Sensitive data_ - user will be prompted on standard input) (Sensitive data - user will be prompted on standard input) The password used to access cloud.
+- `--project-name`: (_Required_) The name of the project within the cloud.
+- `--read-permissions`: (_Default_: `[]`) A user must have at least one of these roles in order to view this account's cloud resources.
+- `--regions`: (_Default_: `[]`) (_Required_) The region(s) of the cloud.
+- `--required-group-membership`: (_Default_: `[]`) A user must be a member of at least one specified group in order to make changes to this account's cloud resources.
+- `--username`: (_Required_) The username used to access cloud.
+- `--write-permissions`: (_Default_: `[]`) A user must have at least one of these roles in order to make changes to this account's cloud resources.
---
+
## hal config provider huaweicloud account delete
Delete a specific huaweicloud account by name.
#### Usage
+
```
hal config provider huaweicloud account delete ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider huaweicloud account edit
Edit an account in the huaweicloud provider.
#### Usage
+
```
hal config provider huaweicloud account edit ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--account-type`: The type of account.
- * `--add-read-permission`: Add this permission to the list of read permissions.
- * `--add-region`: Add this region to the list of managed regions.
- * `--add-required-group-membership`: Add this group to the list of required group memberships.
- * `--add-write-permission`: Add this permission to the list of write permissions.
- * `--auth-url`: The auth url of cloud.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--domain-name`: The domain name of the cloud.
- * `--environment`: The environment name for the account. Many accounts can share the same environment (e.g. dev, test, prod)
- * `--insecure`: Disable certificate validation on SSL connections. Needed if certificates are self signed. Default false.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--password`: (*Sensitive data* - user will be prompted on standard input) (Sensitive data - user will be prompted on standard input) The password used to access cloud.
- * `--project-name`: The name of the project within the cloud.
- * `--read-permissions`: A user must have at least one of these roles in order to view this account's cloud resources.
- * `--regions`: (*Default*: `[]`) The region(s) of the cloud.
- * `--remove-read-permission`: Remove this permission from the list of read permissions.
- * `--remove-region`: Remove this region from the list of managed regions.
- * `--remove-required-group-membership`: Remove this group from the list of required group memberships.
- * `--remove-write-permission`: Remove this permission to from list of write permissions.
- * `--required-group-membership`: A user must be a member of at least one specified group in order to make changes to this account's cloud resources.
- * `--username`: The username used to access cloud.
- * `--write-permissions`: A user must have at least one of these roles in order to make changes to this account's cloud resources.
+- `--account-type`: The type of account.
+- `--add-read-permission`: Add this permission to the list of read permissions.
+- `--add-region`: Add this region to the list of managed regions.
+- `--add-required-group-membership`: Add this group to the list of required group memberships.
+- `--add-write-permission`: Add this permission to the list of write permissions.
+- `--auth-url`: The auth url of cloud.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--domain-name`: The domain name of the cloud.
+- `--environment`: The environment name for the account. Many accounts can share the same environment (e.g. dev, test, prod)
+- `--insecure`: Disable certificate validation on SSL connections. Needed if certificates are self signed. Default false.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--password`: (_Sensitive data_ - user will be prompted on standard input) (Sensitive data - user will be prompted on standard input) The password used to access cloud.
+- `--project-name`: The name of the project within the cloud.
+- `--read-permissions`: A user must have at least one of these roles in order to view this account's cloud resources.
+- `--regions`: (_Default_: `[]`) The region(s) of the cloud.
+- `--remove-read-permission`: Remove this permission from the list of read permissions.
+- `--remove-region`: Remove this region from the list of managed regions.
+- `--remove-required-group-membership`: Remove this group from the list of required group memberships.
+- `--remove-write-permission`: Remove this permission to from list of write permissions.
+- `--required-group-membership`: A user must be a member of at least one specified group in order to make changes to this account's cloud resources.
+- `--username`: The username used to access cloud.
+- `--write-permissions`: A user must have at least one of these roles in order to make changes to this account's cloud resources.
---
+
## hal config provider huaweicloud account get
Get the specified account details for the huaweicloud provider.
#### Usage
+
```
hal config provider huaweicloud account get ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider huaweicloud account list
List the account names for the huaweicloud provider.
#### Usage
+
```
hal config provider huaweicloud account list [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider huaweicloud bakery
Manage and view Spinnaker configuration for the huaweicloud provider's image bakery configuration.
#### Usage
+
```
hal config provider huaweicloud bakery [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `base-image`: Manage and view Spinnaker configuration for the huaweicloud provider's base image.
- * `edit`: Edit the huaweicloud provider's bakery default options.
+
+- `base-image`: Manage and view Spinnaker configuration for the huaweicloud provider's base image.
+- `edit`: Edit the huaweicloud provider's bakery default options.
---
+
## hal config provider huaweicloud bakery base-image
Manage and view Spinnaker configuration for the huaweicloud provider's base image.
#### Usage
+
```
hal config provider huaweicloud bakery base-image [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `add`: Add a base image for the huaweicloud provider's bakery.
- * `delete`: Delete a specific huaweicloud base image by name.
- * `edit`: Edit a base image for the huaweicloud provider's bakery.
- * `get`: Get the specified base image details for the huaweicloud provider.
- * `list`: List the base image names for the huaweicloud provider.
+
+- `add`: Add a base image for the huaweicloud provider's bakery.
+- `delete`: Delete a specific huaweicloud base image by name.
+- `edit`: Edit a base image for the huaweicloud provider's bakery.
+- `get`: Get the specified base image details for the huaweicloud provider.
+- `list`: List the base image names for the huaweicloud provider.
---
+
## hal config provider huaweicloud bakery base-image add
Add a base image for the huaweicloud provider's bakery.
#### Usage
+
```
hal config provider huaweicloud bakery base-image add BASE-IMAGE [parameters]
```
#### Parameters
+
`BASE-IMAGE`: The name of the base image to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--detailed-description`: A long description to help human operators identify the image.
- * `--eip-type`: (*Required*) The eip type for the baking configuration. See the api doc to get its value
- * `--instance-type`: (*Required*) The instance type for the baking configuration.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--package-type`: This is used to help Spinnaker's bakery download the build artifacts you supply it with. For example, specifying 'deb' indicates that your artifacts will need to be fetched from a debian repository.
- * `--region`: (*Required*) The region for the baking configuration.
- * `--short-description`: A short description to help human operators identify the image.
- * `--source-image-id`: (*Required*) The source image ID for the baking configuration.
- * `--ssh-user-name`: (*Required*) The ssh username for the baking configuration.
- * `--template-file`: This is the name of the packer template that will be used to bake images from this base image. The template file must be found in this list [https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer](https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer), or supplied as described here: [https://spinnaker.io/setup/bakery/](https://spinnaker.io/setup/bakery/)
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--detailed-description`: A long description to help human operators identify the image.
+- `--eip-type`: (_Required_) The eip type for the baking configuration. See the api doc to get its value
+- `--instance-type`: (_Required_) The instance type for the baking configuration.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--package-type`: This is used to help Spinnaker's bakery download the build artifacts you supply it with. For example, specifying 'deb' indicates that your artifacts will need to be fetched from a debian repository.
+- `--region`: (_Required_) The region for the baking configuration.
+- `--short-description`: A short description to help human operators identify the image.
+- `--source-image-id`: (_Required_) The source image ID for the baking configuration.
+- `--ssh-user-name`: (_Required_) The ssh username for the baking configuration.
+- `--template-file`: This is the name of the packer template that will be used to bake images from this base image. The template file must be found in this list [https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer](https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer), or supplied as described here: [https://spinnaker.io/setup/bakery/](https://spinnaker.io/setup/bakery/)
---
+
## hal config provider huaweicloud bakery base-image delete
Delete a specific huaweicloud base image by name.
#### Usage
+
```
hal config provider huaweicloud bakery base-image delete BASE-IMAGE [parameters]
```
#### Parameters
+
`BASE-IMAGE`: The name of the base image to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider huaweicloud bakery base-image edit
Edit a base image for the huaweicloud provider's bakery.
#### Usage
+
```
hal config provider huaweicloud bakery base-image edit BASE-IMAGE [parameters]
```
#### Parameters
+
`BASE-IMAGE`: The name of the base image to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--detailed-description`: A long description to help human operators identify the image.
- * `--eip-type`: The eip type for the baking configuration. See the api doc to get its value
- * `--id`: This is the identifier used by your cloud to find this base image.
- * `--instance-type`: The instance type for the baking configuration.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--package-type`: This is used to help Spinnaker's bakery download the build artifacts you supply it with. For example, specifying 'deb' indicates that your artifacts will need to be fetched from a debian repository.
- * `--region`: The region for the baking configuration.
- * `--short-description`: A short description to help human operators identify the image.
- * `--source-image-id`: The source image ID for the baking configuration.
- * `--ssh-user-name`: The ssh username for the baking configuration.
- * `--template-file`: This is the name of the packer template that will be used to bake images from this base image. The template file must be found in this list [https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer](https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer), or supplied as described here: [https://spinnaker.io/setup/bakery/](https://spinnaker.io/setup/bakery/)
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--detailed-description`: A long description to help human operators identify the image.
+- `--eip-type`: The eip type for the baking configuration. See the api doc to get its value
+- `--id`: This is the identifier used by your cloud to find this base image.
+- `--instance-type`: The instance type for the baking configuration.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--package-type`: This is used to help Spinnaker's bakery download the build artifacts you supply it with. For example, specifying 'deb' indicates that your artifacts will need to be fetched from a debian repository.
+- `--region`: The region for the baking configuration.
+- `--short-description`: A short description to help human operators identify the image.
+- `--source-image-id`: The source image ID for the baking configuration.
+- `--ssh-user-name`: The ssh username for the baking configuration.
+- `--template-file`: This is the name of the packer template that will be used to bake images from this base image. The template file must be found in this list [https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer](https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer), or supplied as described here: [https://spinnaker.io/setup/bakery/](https://spinnaker.io/setup/bakery/)
---
+
## hal config provider huaweicloud bakery base-image get
Get the specified base image details for the huaweicloud provider.
#### Usage
+
```
hal config provider huaweicloud bakery base-image get BASE-IMAGE [parameters]
```
#### Parameters
+
`BASE-IMAGE`: The name of the base image to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider huaweicloud bakery base-image list
List the base image names for the huaweicloud provider.
#### Usage
+
```
hal config provider huaweicloud bakery base-image list [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider huaweicloud bakery edit
Edit the huaweicloud provider's bakery default options.
#### Usage
+
```
hal config provider huaweicloud bakery edit [parameters]
```
#### Parameters
- * `--auth-url`: (*Required*) Set the default auth URL your images will be baked in.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--domain-name`: (*Required*) Set the default domainName your images will be baked in.
- * `--eip-bandwidth-size`: (*Required*) Set the bandwidth size of eip your images will be baked in.
- * `--insecure`: (*Required*) The security setting (true/false) for connecting to the HuaweiCloud account.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--password`: (*Required*) (*Sensitive data* - user will be prompted on standard input) Set the default password your images will be baked with.
- * `--project-name`: (*Required*) Set the default project name your images will be baked in.
- * `--security-group`: (*Required*) Set the default security group your images will be baked in.
- * `--subnet-id`: (*Required*) Set the subnet your images will be baked in.
- * `--template-file`: This is the name of the packer template that will be used to bake images from this base image. The template file must be found in this list [https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer](https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer), or supplied as described here: [https://spinnaker.io/setup/bakery/](https://spinnaker.io/setup/bakery/)
- * `--username`: (*Required*) Set the default username your images will be baked with.
- * `--vpc-id`: (*Required*) Set the vpc your images will be baked in.
+- `--auth-url`: (_Required_) Set the default auth URL your images will be baked in.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--domain-name`: (_Required_) Set the default domainName your images will be baked in.
+- `--eip-bandwidth-size`: (_Required_) Set the bandwidth size of eip your images will be baked in.
+- `--insecure`: (_Required_) The security setting (true/false) for connecting to the HuaweiCloud account.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--password`: (_Required_) (_Sensitive data_ - user will be prompted on standard input) Set the default password your images will be baked with.
+- `--project-name`: (_Required_) Set the default project name your images will be baked in.
+- `--security-group`: (_Required_) Set the default security group your images will be baked in.
+- `--subnet-id`: (_Required_) Set the subnet your images will be baked in.
+- `--template-file`: This is the name of the packer template that will be used to bake images from this base image. The template file must be found in this list [https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer](https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer), or supplied as described here: [https://spinnaker.io/setup/bakery/](https://spinnaker.io/setup/bakery/)
+- `--username`: (_Required_) Set the default username your images will be baked with.
+- `--vpc-id`: (_Required_) Set the vpc your images will be baked in.
---
+
## hal config provider huaweicloud disable
Set the huaweicloud provider as disabled
#### Usage
+
```
hal config provider huaweicloud disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider huaweicloud enable
Set the huaweicloud provider as enabled
#### Usage
+
```
hal config provider huaweicloud enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider kubernetes
-The Kubernetes provider is used to deploy Kubernetes resources to any number of Kubernetes clusters. Spinnaker assumes you have a Kubernetes cluster already running. If you don't, you must configure one: [https://kubernetes.io/docs/getting-started-guides/](https://kubernetes.io/docs/getting-started-guides/).
+The Kubernetes provider is used to deploy Kubernetes resources to any number of Kubernetes clusters. Spinnaker assumes you have a Kubernetes cluster already running. If you don't, you must configure one: [https://kubernetes.io/docs/getting-started-guides/](https://kubernetes.io/docs/getting-started-guides/).
Before proceeding, please visit [https://kubernetes.io/docs/concepts/cluster-administration/authenticate-across-clusters-kubeconfig/](https://kubernetes.io/docs/concepts/cluster-administration/authenticate-across-clusters-kubeconfig/) to make sure you're familiar with the authentication terminology. For more information on how to configure individual accounts, or how to deploy to multiple clusters, please read the documentation under `hal config provider kubernetes account -h`.
#### Usage
+
```
hal config provider kubernetes [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `account`: Manage and view Spinnaker configuration for the kubernetes provider's account
- * `disable`: Set the kubernetes provider as disabled
- * `edit`: Set provider-wide properties for the Kubernetes provider
- * `enable`: Set the kubernetes provider as enabled
+
+- `account`: Manage and view Spinnaker configuration for the kubernetes provider's account
+- `disable`: Set the kubernetes provider as disabled
+- `edit`: Set provider-wide properties for the Kubernetes provider
+- `enable`: Set the kubernetes provider as enabled
---
+
## hal config provider kubernetes account
An account in the Kubernetes provider refers to a single Kubernetes context. In Kubernetes, a context is the combination of a Kubernetes cluster and some credentials. If no context is specified, the default context in in your kubeconfig is assumed.
@@ -9527,2949 +10906,3396 @@ An account in the Kubernetes provider refers to a single Kubernetes context. In
You must also provide a set of Docker Registries for each account. Spinnaker will automatically upload that Registry's credentials to the specified Kubernetes cluster allowing you to deploy those images without further configuration.
#### Usage
+
```
hal config provider kubernetes account ACCOUNT [parameters] [subcommands]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `add`: Add an account to the kubernetes provider.
- * `delete`: Delete a specific kubernetes account by name.
- * `edit`: Edit an account in the kubernetes provider.
- * `get`: Get the specified account details for the kubernetes provider.
- * `list`: List the account names for the kubernetes provider.
+
+- `add`: Add an account to the kubernetes provider.
+- `delete`: Delete a specific kubernetes account by name.
+- `edit`: Edit an account in the kubernetes provider.
+- `get`: Get the specified account details for the kubernetes provider.
+- `list`: List the account names for the kubernetes provider.
---
+
## hal config provider kubernetes account add
Add an account to the kubernetes provider.
#### Usage
+
```
hal config provider kubernetes account add ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--cache-threads`: (*Default*: `1`) Number of caching agents for this kubernetes account. Each agent handles a subset of the namespaces available to this account. By default, only 1 agent caches all kinds for all namespaces in the account.
- * `--check-permissions-on-startup`: When false, clouddriver will skip the permission checks for all kubernetes kinds at startup. This can save a great deal of time
-during clouddriver startup when you have many kubernetes accounts configured. This disables the log messages at startup about missing permissions.
- * `--configure-image-pull-secrets`: (*Default*: `true`) (Only applicable to the v1 provider). When true, Spinnaker will create & manage your image pull secrets for you; when false, you will have to create and attach them to your pod specs by hand.
- * `--context`: The kubernetes context to be managed by Spinnaker. See [http://kubernetes.io/docs/user-guide/kubeconfig-file/#context](http://kubernetes.io/docs/user-guide/kubeconfig-file/#context) for more information.
-When no context is configured for an account the 'current-context' in your kubeconfig is assumed.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--docker-registries`: (*Default*: `[]`) A list of the Spinnaker docker registry account names this Spinnaker account can use as image sources. These docker registry accounts must be registered in your halconfig before you can add them here.
- * `--environment`: The environment name for the account. Many accounts can share the same environment (e.g. dev, test, prod)
- * `--kinds`: (*Default*: `[]`) (V2 Only) A list of resource kinds this Spinnaker account can deploy to and will cache.
-When no kinds are configured, this defaults to 'all kinds described here [https://spinnaker.io/reference/providers/kubernetes-v2/](https://spinnaker.io/reference/providers/kubernetes-v2/)'.
- * `--kubeconfig-file`: The path to your kubeconfig file. By default, it will be under the Spinnaker user's home directory in the typical .kube/config location.
- * `--live-manifest-calls`: When true, clouddriver will query manifest status during pipeline executions using live data rather than the cache.
-This eliminates all time spent in the "force cache refresh" task in pipelines, greatly reducing execution time.
- * `--namespaces`: (*Default*: `[]`) A list of namespaces this Spinnaker account can deploy to and will cache.
-When no namespaces are configured, this defaults to 'all namespaces'.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--omit-kinds`: (*Default*: `[]`) (V2 Only) A list of resource kinds this Spinnaker account cannot deploy to or cache.
-This can only be set when --kinds is empty or not set.
- * `--omit-namespaces`: (*Default*: `[]`) A list of namespaces this Spinnaker account cannot deploy to or cache.
-This can only be set when --namespaces is empty or not set.
- * `--only-spinnaker-managed`: (*Default*: `false`) (V2 Only) When true, Spinnaker will only cache/display applications that have been
-created by Spinnaker; as opposed to attempting to configure applications for resources already present in Kubernetes.
- * `--provider-version`: (*Default*: `v2`) There are currently two versions of the Kubernetes Provider: V1 and V2. This allows you to pick the version of the provider (not the resources it manages) to run within Spinnaker.V1 is scheduled for removal in Spinnaker 1.21; we recommend using V2 only.
- * `--read-permissions`: (*Default*: `[]`) A user must have at least one of these roles in order to view this account's cloud resources.
- * `--required-group-membership`: (*Default*: `[]`) A user must be a member of at least one specified group in order to make changes to this account's cloud resources.
- * `--service-account`: When true, Spinnaker attempt to authenticate against Kubernetes using a Kubernetes service account. This only works when Halyard & Spinnaker are deployed in Kubernetes. Read more about service accounts here: [https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/](https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/).
- * `--write-permissions`: (*Default*: `[]`) A user must have at least one of these roles in order to make changes to this account's cloud resources.
+- `--cache-threads`: (_Default_: `1`) Number of caching agents for this kubernetes account. Each agent handles a subset of the namespaces available to this account. By default, only 1 agent caches all kinds for all namespaces in the account.
+- `--check-permissions-on-startup`: When false, clouddriver will skip the permission checks for all kubernetes kinds at startup. This can save a great deal of time
+ during clouddriver startup when you have many kubernetes accounts configured. This disables the log messages at startup about missing permissions.
+- `--configure-image-pull-secrets`: (_Default_: `true`) (Only applicable to the v1 provider). When true, Spinnaker will create & manage your image pull secrets for you; when false, you will have to create and attach them to your pod specs by hand.
+- `--context`: The kubernetes context to be managed by Spinnaker. See [http://kubernetes.io/docs/user-guide/kubeconfig-file/#context](http://kubernetes.io/docs/user-guide/kubeconfig-file/#context) for more information.
+ When no context is configured for an account the 'current-context' in your kubeconfig is assumed.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--docker-registries`: (_Default_: `[]`) A list of the Spinnaker docker registry account names this Spinnaker account can use as image sources. These docker registry accounts must be registered in your halconfig before you can add them here.
+- `--environment`: The environment name for the account. Many accounts can share the same environment (e.g. dev, test, prod)
+- `--kinds`: (_Default_: `[]`) (V2 Only) A list of resource kinds this Spinnaker account can deploy to and will cache.
+ When no kinds are configured, this defaults to 'all kinds described here [https://spinnaker.io/reference/providers/kubernetes-v2/](https://spinnaker.io/reference/providers/kubernetes-v2/)'.
+- `--kubeconfig-file`: The path to your kubeconfig file. By default, it will be under the Spinnaker user's home directory in the typical .kube/config location.
+- `--live-manifest-calls`: When true, clouddriver will query manifest status during pipeline executions using live data rather than the cache.
+ This eliminates all time spent in the "force cache refresh" task in pipelines, greatly reducing execution time.
+- `--namespaces`: (_Default_: `[]`) A list of namespaces this Spinnaker account can deploy to and will cache.
+ When no namespaces are configured, this defaults to 'all namespaces'.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--omit-kinds`: (_Default_: `[]`) (V2 Only) A list of resource kinds this Spinnaker account cannot deploy to or cache.
+ This can only be set when --kinds is empty or not set.
+- `--omit-namespaces`: (_Default_: `[]`) A list of namespaces this Spinnaker account cannot deploy to or cache.
+ This can only be set when --namespaces is empty or not set.
+- `--only-spinnaker-managed`: (_Default_: `false`) (V2 Only) When true, Spinnaker will only cache/display applications that have been
+ created by Spinnaker; as opposed to attempting to configure applications for resources already present in Kubernetes.
+- `--provider-version`: (_Default_: `v2`) There are currently two versions of the Kubernetes Provider: V1 and V2. This allows you to pick the version of the provider (not the resources it manages) to run within Spinnaker.V1 is scheduled for removal in Spinnaker 1.21; we recommend using V2 only.
+- `--read-permissions`: (_Default_: `[]`) A user must have at least one of these roles in order to view this account's cloud resources.
+- `--required-group-membership`: (_Default_: `[]`) A user must be a member of at least one specified group in order to make changes to this account's cloud resources.
+- `--service-account`: When true, Spinnaker attempt to authenticate against Kubernetes using a Kubernetes service account. This only works when Halyard & Spinnaker are deployed in Kubernetes. Read more about service accounts here: [https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/](https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/).
+- `--write-permissions`: (_Default_: `[]`) A user must have at least one of these roles in order to make changes to this account's cloud resources.
---
+
## hal config provider kubernetes account delete
Delete a specific kubernetes account by name.
#### Usage
+
```
hal config provider kubernetes account delete ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider kubernetes account edit
Edit an account in the kubernetes provider.
#### Usage
+
```
hal config provider kubernetes account edit ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--add-custom-resource`: (V2 Only) Add Kubernetes custom resource to the list of custom resources to managed by clouddriver and made available for use in patch and delete manifest stages. Fields besides the Kubernetes Kind (resource name) can be set using the flags "--spinnaker-kind" and "--versioned"
- * `--add-docker-registry`: Add this docker registry to the list of docker registries to use as a source of images.
- * `--add-kind`: Add this kind to the list of kinds to manage.
- * `--add-namespace`: Add this namespace to the list of namespaces to manage.
- * `--add-omit-kind`: Add this kind to the list of kinds to omit.
- * `--add-omit-namespace`: Add this namespace to the list of namespaces to omit.
- * `--add-read-permission`: Add this permission to the list of read permissions.
- * `--add-required-group-membership`: Add this group to the list of required group memberships.
- * `--add-write-permission`: Add this permission to the list of write permissions.
- * `--all-kinds`: (*Default*: `false`) Set the list of kinds to cache and deploy to every kind available to your supplied credentials.
- * `--all-namespaces`: (*Default*: `false`) Set the list of namespaces to cache and deploy to every namespace available to your supplied credentials.
- * `--cache-threads`: Number of caching agents for this kubernetes account. Each agent handles a subset of the namespaces available to this account. By default, only 1 agent caches all kinds for all namespaces in the account.
- * `--check-permissions-on-startup`: When false, clouddriver will skip the permission checks for all kubernetes kinds at startup. This can save a great deal of time
-during clouddriver startup when you have many kubernetes accounts configured. This disables the log messages at startup about missing permissions.
- * `--clear-context`: (*Default*: `false`) Removes the currently configured context, defaulting to 'current-context' in your kubeconfig.See [http://kubernetes.io/docs/user-guide/kubeconfig-file/#context](http://kubernetes.io/docs/user-guide/kubeconfig-file/#context) for more information.
- * `--configure-image-pull-secrets`: (Only applicable to the v1 provider). When true, Spinnaker will create & manage your image pull secrets for you; when false, you will have to create and attach them to your pod specs by hand.
- * `--context`: The kubernetes context to be managed by Spinnaker. See [http://kubernetes.io/docs/user-guide/kubeconfig-file/#context](http://kubernetes.io/docs/user-guide/kubeconfig-file/#context) for more information.
-When no context is configured for an account the 'current-context' in your kubeconfig is assumed.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--docker-registries`: (*Default*: `[]`) A list of the Spinnaker docker registry account names this Spinnaker account can use as image sources. These docker registry accounts must be registered in your halconfig before you can add them here.
- * `--environment`: The environment name for the account. Many accounts can share the same environment (e.g. dev, test, prod)
- * `--kinds`: (*Default*: `[]`) (V2 Only) A list of resource kinds this Spinnaker account can deploy to and will cache.
-When no kinds are configured, this defaults to 'all kinds described here [https://spinnaker.io/reference/providers/kubernetes-v2/](https://spinnaker.io/reference/providers/kubernetes-v2/)'.
- * `--kubeconfig-file`: The path to your kubeconfig file. By default, it will be under the Spinnaker user's home directory in the typical .kube/config location.
- * `--live-manifest-calls`: When true, clouddriver will query manifest status during pipeline executions using live data rather than the cache.
-This eliminates all time spent in the "force cache refresh" task in pipelines, greatly reducing execution time.
- * `--namespaces`: (*Default*: `[]`) A list of namespaces this Spinnaker account can deploy to and will cache.
-When no namespaces are configured, this defaults to 'all namespaces'.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--omit-kinds`: (*Default*: `[]`) (V2 Only) A list of resource kinds this Spinnaker account cannot deploy to or cache.
-This can only be set when --kinds is empty or not set.
- * `--omit-namespaces`: (*Default*: `[]`) A list of namespaces this Spinnaker account cannot deploy to or cache.
-This can only be set when --namespaces is empty or not set.
- * `--only-spinnaker-managed`: (V2 Only) When true, Spinnaker will only cache/display applications that have been
-created by Spinnaker; as opposed to attempting to configure applications for resources already present in Kubernetes.
- * `--provider-version`: There are currently two versions of the Kubernetes Provider: V1 and V2. This allows you to pick the version of the provider (not the resources it manages) to run within Spinnaker.V1 is scheduled for removal in Spinnaker 1.21; we recommend using V2 only.
- * `--read-permissions`: A user must have at least one of these roles in order to view this account's cloud resources.
- * `--remove-custom-resource`: Remove this Kubernetes custom resource by name from the list of custom resources to manage.
- * `--remove-docker-registry`: Remove this docker registry from the list of docker registries to use as a source of images.
- * `--remove-kind`: Remove this kind to the list of kinds to manage.
- * `--remove-namespace`: Remove this namespace to the list of namespaces to manage.
- * `--remove-omit-kind`: Remove this kind to the list of kinds to omit.
- * `--remove-omit-namespace`: Remove this namespace to the list of namespaces to omit.
- * `--remove-read-permission`: Remove this permission from the list of read permissions.
- * `--remove-required-group-membership`: Remove this group from the list of required group memberships.
- * `--remove-write-permission`: Remove this permission to from list of write permissions.
- * `--required-group-membership`: A user must be a member of at least one specified group in order to make changes to this account's cloud resources.
- * `--service-account`: When true, Spinnaker attempt to authenticate against Kubernetes using a Kubernetes service account. This only works when Halyard & Spinnaker are deployed in Kubernetes. Read more about service accounts here: [https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/](https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/).
- * `--spinnaker-kind`: Set the Spinnaker kind for custom resource being added.
- * `--versioned`: Configure whether the custom resource being added is versioned by Spinnaker.
- * `--write-permissions`: A user must have at least one of these roles in order to make changes to this account's cloud resources.
+- `--add-custom-resource`: (V2 Only) Add Kubernetes custom resource to the list of custom resources to managed by clouddriver and made available for use in patch and delete manifest stages. Fields besides the Kubernetes Kind (resource name) can be set using the flags "--spinnaker-kind" and "--versioned"
+- `--add-docker-registry`: Add this docker registry to the list of docker registries to use as a source of images.
+- `--add-kind`: Add this kind to the list of kinds to manage.
+- `--add-namespace`: Add this namespace to the list of namespaces to manage.
+- `--add-omit-kind`: Add this kind to the list of kinds to omit.
+- `--add-omit-namespace`: Add this namespace to the list of namespaces to omit.
+- `--add-read-permission`: Add this permission to the list of read permissions.
+- `--add-required-group-membership`: Add this group to the list of required group memberships.
+- `--add-write-permission`: Add this permission to the list of write permissions.
+- `--all-kinds`: (_Default_: `false`) Set the list of kinds to cache and deploy to every kind available to your supplied credentials.
+- `--all-namespaces`: (_Default_: `false`) Set the list of namespaces to cache and deploy to every namespace available to your supplied credentials.
+- `--cache-threads`: Number of caching agents for this kubernetes account. Each agent handles a subset of the namespaces available to this account. By default, only 1 agent caches all kinds for all namespaces in the account.
+- `--check-permissions-on-startup`: When false, clouddriver will skip the permission checks for all kubernetes kinds at startup. This can save a great deal of time
+ during clouddriver startup when you have many kubernetes accounts configured. This disables the log messages at startup about missing permissions.
+- `--clear-context`: (_Default_: `false`) Removes the currently configured context, defaulting to 'current-context' in your kubeconfig.See [http://kubernetes.io/docs/user-guide/kubeconfig-file/#context](http://kubernetes.io/docs/user-guide/kubeconfig-file/#context) for more information.
+- `--configure-image-pull-secrets`: (Only applicable to the v1 provider). When true, Spinnaker will create & manage your image pull secrets for you; when false, you will have to create and attach them to your pod specs by hand.
+- `--context`: The kubernetes context to be managed by Spinnaker. See [http://kubernetes.io/docs/user-guide/kubeconfig-file/#context](http://kubernetes.io/docs/user-guide/kubeconfig-file/#context) for more information.
+ When no context is configured for an account the 'current-context' in your kubeconfig is assumed.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--docker-registries`: (_Default_: `[]`) A list of the Spinnaker docker registry account names this Spinnaker account can use as image sources. These docker registry accounts must be registered in your halconfig before you can add them here.
+- `--environment`: The environment name for the account. Many accounts can share the same environment (e.g. dev, test, prod)
+- `--kinds`: (_Default_: `[]`) (V2 Only) A list of resource kinds this Spinnaker account can deploy to and will cache.
+ When no kinds are configured, this defaults to 'all kinds described here [https://spinnaker.io/reference/providers/kubernetes-v2/](https://spinnaker.io/reference/providers/kubernetes-v2/)'.
+- `--kubeconfig-file`: The path to your kubeconfig file. By default, it will be under the Spinnaker user's home directory in the typical .kube/config location.
+- `--live-manifest-calls`: When true, clouddriver will query manifest status during pipeline executions using live data rather than the cache.
+ This eliminates all time spent in the "force cache refresh" task in pipelines, greatly reducing execution time.
+- `--namespaces`: (_Default_: `[]`) A list of namespaces this Spinnaker account can deploy to and will cache.
+ When no namespaces are configured, this defaults to 'all namespaces'.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--omit-kinds`: (_Default_: `[]`) (V2 Only) A list of resource kinds this Spinnaker account cannot deploy to or cache.
+ This can only be set when --kinds is empty or not set.
+- `--omit-namespaces`: (_Default_: `[]`) A list of namespaces this Spinnaker account cannot deploy to or cache.
+ This can only be set when --namespaces is empty or not set.
+- `--only-spinnaker-managed`: (V2 Only) When true, Spinnaker will only cache/display applications that have been
+ created by Spinnaker; as opposed to attempting to configure applications for resources already present in Kubernetes.
+- `--provider-version`: There are currently two versions of the Kubernetes Provider: V1 and V2. This allows you to pick the version of the provider (not the resources it manages) to run within Spinnaker.V1 is scheduled for removal in Spinnaker 1.21; we recommend using V2 only.
+- `--read-permissions`: A user must have at least one of these roles in order to view this account's cloud resources.
+- `--remove-custom-resource`: Remove this Kubernetes custom resource by name from the list of custom resources to manage.
+- `--remove-docker-registry`: Remove this docker registry from the list of docker registries to use as a source of images.
+- `--remove-kind`: Remove this kind to the list of kinds to manage.
+- `--remove-namespace`: Remove this namespace to the list of namespaces to manage.
+- `--remove-omit-kind`: Remove this kind to the list of kinds to omit.
+- `--remove-omit-namespace`: Remove this namespace to the list of namespaces to omit.
+- `--remove-read-permission`: Remove this permission from the list of read permissions.
+- `--remove-required-group-membership`: Remove this group from the list of required group memberships.
+- `--remove-write-permission`: Remove this permission to from list of write permissions.
+- `--required-group-membership`: A user must be a member of at least one specified group in order to make changes to this account's cloud resources.
+- `--service-account`: When true, Spinnaker attempt to authenticate against Kubernetes using a Kubernetes service account. This only works when Halyard & Spinnaker are deployed in Kubernetes. Read more about service accounts here: [https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/](https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/).
+- `--spinnaker-kind`: Set the Spinnaker kind for custom resource being added.
+- `--versioned`: Configure whether the custom resource being added is versioned by Spinnaker.
+- `--write-permissions`: A user must have at least one of these roles in order to make changes to this account's cloud resources.
---
+
## hal config provider kubernetes account get
Get the specified account details for the kubernetes provider.
#### Usage
+
```
hal config provider kubernetes account get ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider kubernetes account list
List the account names for the kubernetes provider.
#### Usage
+
```
hal config provider kubernetes account list [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider kubernetes disable
Set the kubernetes provider as disabled
#### Usage
+
```
hal config provider kubernetes disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider kubernetes edit
Due to how the Kubernetes provider shards its cache resources, there is opportunity to tune how its caching should be handled. This command exists to allow you tune this caching behavior.
#### Usage
+
```
hal config provider kubernetes edit [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider kubernetes enable
Set the kubernetes provider as enabled
#### Usage
+
```
hal config provider kubernetes enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider oracle
Manage and view Spinnaker configuration for the oracle provider
#### Usage
+
```
hal config provider oracle [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `account`: Manage and view Spinnaker configuration for the oracle provider's account
- * `bakery`: Manage and view Spinnaker configuration for the oracle provider's image bakery configuration.
- * `disable`: Set the oracle provider as disabled
- * `enable`: Set the oracle provider as enabled
+
+- `account`: Manage and view Spinnaker configuration for the oracle provider's account
+- `bakery`: Manage and view Spinnaker configuration for the oracle provider's image bakery configuration.
+- `disable`: Set the oracle provider as disabled
+- `enable`: Set the oracle provider as enabled
---
+
## hal config provider oracle account
Manage and view Spinnaker configuration for the oracle provider's account
#### Usage
+
```
hal config provider oracle account ACCOUNT [parameters] [subcommands]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `add`: Add an account to the oracle provider.
- * `delete`: Delete a specific oracle account by name.
- * `edit`: Edit an account in the oracle provider.
- * `get`: Get the specified account details for the oracle provider.
- * `list`: List the account names for the oracle provider.
+
+- `add`: Add an account to the oracle provider.
+- `delete`: Delete a specific oracle account by name.
+- `edit`: Edit an account in the oracle provider.
+- `get`: Get the specified account details for the oracle provider.
+- `list`: List the account names for the oracle provider.
---
+
## hal config provider oracle account add
Add an account to the oracle provider.
#### Usage
+
```
hal config provider oracle account add ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--compartment-id`: (*Required*) Provide the OCID of the Oracle Compartment to use.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--environment`: The environment name for the account. Many accounts can share the same environment (e.g. dev, test, prod)
- * `--fingerprint`: (*Required*) Fingerprint of the public key
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--private-key-passphrase`: (*Sensitive data* - user will be prompted on standard input) Passphrase used for the private key, if it is encrypted
- * `--read-permissions`: (*Default*: `[]`) A user must have at least one of these roles in order to view this account's cloud resources.
- * `--region`: (*Required*) An Oracle region (e.g., us-phoenix-1)
- * `--required-group-membership`: (*Default*: `[]`) A user must be a member of at least one specified group in order to make changes to this account's cloud resources.
- * `--ssh-private-key-file-path`: (*Required*) Path to the private key in PEM format
- * `--tenancyId`: (*Required*) Provide the OCID of the Oracle Tenancy to use.
- * `--user-id`: (*Required*) Provide the OCID of the Oracle User you're authenticating as
- * `--write-permissions`: (*Default*: `[]`) A user must have at least one of these roles in order to make changes to this account's cloud resources.
+- `--compartment-id`: (_Required_) Provide the OCID of the Oracle Compartment to use.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--environment`: The environment name for the account. Many accounts can share the same environment (e.g. dev, test, prod)
+- `--fingerprint`: (_Required_) Fingerprint of the public key
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--private-key-passphrase`: (_Sensitive data_ - user will be prompted on standard input) Passphrase used for the private key, if it is encrypted
+- `--read-permissions`: (_Default_: `[]`) A user must have at least one of these roles in order to view this account's cloud resources.
+- `--region`: (_Required_) An Oracle region (e.g., us-phoenix-1)
+- `--required-group-membership`: (_Default_: `[]`) A user must be a member of at least one specified group in order to make changes to this account's cloud resources.
+- `--ssh-private-key-file-path`: (_Required_) Path to the private key in PEM format
+- `--tenancyId`: (_Required_) Provide the OCID of the Oracle Tenancy to use.
+- `--user-id`: (_Required_) Provide the OCID of the Oracle User you're authenticating as
+- `--write-permissions`: (_Default_: `[]`) A user must have at least one of these roles in order to make changes to this account's cloud resources.
---
+
## hal config provider oracle account delete
Delete a specific oracle account by name.
#### Usage
+
```
hal config provider oracle account delete ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider oracle account edit
Edit an account in the oracle provider.
#### Usage
+
```
hal config provider oracle account edit ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--add-read-permission`: Add this permission to the list of read permissions.
- * `--add-required-group-membership`: Add this group to the list of required group memberships.
- * `--add-write-permission`: Add this permission to the list of write permissions.
- * `--compartment-id`: Provide the OCID of the Oracle Compartment to use.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--environment`: The environment name for the account. Many accounts can share the same environment (e.g. dev, test, prod)
- * `--fingerprint`: Fingerprint of the public key
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--private-key-passphrase`: (*Sensitive data* - user will be prompted on standard input) Passphrase used for the private key, if it is encrypted
- * `--read-permissions`: A user must have at least one of these roles in order to view this account's cloud resources.
- * `--region`: An Oracle region (e.g., us-phoenix-1)
- * `--remove-read-permission`: Remove this permission from the list of read permissions.
- * `--remove-required-group-membership`: Remove this group from the list of required group memberships.
- * `--remove-write-permission`: Remove this permission to from list of write permissions.
- * `--required-group-membership`: A user must be a member of at least one specified group in order to make changes to this account's cloud resources.
- * `--ssh-private-key-file-path`: Path to the private key in PEM format
- * `--tenancyId`: Provide the OCID of the Oracle Tenancy to use.
- * `--user-id`: Provide the OCID of the Oracle User you're authenticating as
- * `--write-permissions`: A user must have at least one of these roles in order to make changes to this account's cloud resources.
+- `--add-read-permission`: Add this permission to the list of read permissions.
+- `--add-required-group-membership`: Add this group to the list of required group memberships.
+- `--add-write-permission`: Add this permission to the list of write permissions.
+- `--compartment-id`: Provide the OCID of the Oracle Compartment to use.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--environment`: The environment name for the account. Many accounts can share the same environment (e.g. dev, test, prod)
+- `--fingerprint`: Fingerprint of the public key
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--private-key-passphrase`: (_Sensitive data_ - user will be prompted on standard input) Passphrase used for the private key, if it is encrypted
+- `--read-permissions`: A user must have at least one of these roles in order to view this account's cloud resources.
+- `--region`: An Oracle region (e.g., us-phoenix-1)
+- `--remove-read-permission`: Remove this permission from the list of read permissions.
+- `--remove-required-group-membership`: Remove this group from the list of required group memberships.
+- `--remove-write-permission`: Remove this permission to from list of write permissions.
+- `--required-group-membership`: A user must be a member of at least one specified group in order to make changes to this account's cloud resources.
+- `--ssh-private-key-file-path`: Path to the private key in PEM format
+- `--tenancyId`: Provide the OCID of the Oracle Tenancy to use.
+- `--user-id`: Provide the OCID of the Oracle User you're authenticating as
+- `--write-permissions`: A user must have at least one of these roles in order to make changes to this account's cloud resources.
---
+
## hal config provider oracle account get
Get the specified account details for the oracle provider.
#### Usage
+
```
hal config provider oracle account get ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider oracle account list
List the account names for the oracle provider.
#### Usage
+
```
hal config provider oracle account list [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider oracle bakery
Manage and view Spinnaker configuration for the oracle provider's image bakery configuration.
#### Usage
+
```
hal config provider oracle bakery [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `base-image`: Manage and view Spinnaker configuration for the oracle provider's base image.
- * `edit`: Edit the oracle provider's bakery default options.
+
+- `base-image`: Manage and view Spinnaker configuration for the oracle provider's base image.
+- `edit`: Edit the oracle provider's bakery default options.
---
+
## hal config provider oracle bakery base-image
Manage and view Spinnaker configuration for the oracle provider's base image.
#### Usage
+
```
hal config provider oracle bakery base-image [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `add`: Add a base image for the oracle provider's bakery.
- * `delete`: Delete a specific oracle base image by name.
- * `edit`: Edit a base image for the oracle provider's bakery.
- * `get`: Get the specified base image details for the oracle provider.
- * `list`: List the base image names for the oracle provider.
+
+- `add`: Add a base image for the oracle provider's bakery.
+- `delete`: Delete a specific oracle base image by name.
+- `edit`: Edit a base image for the oracle provider's bakery.
+- `get`: Get the specified base image details for the oracle provider.
+- `list`: List the base image names for the oracle provider.
---
+
## hal config provider oracle bakery base-image add
Add a base image for the oracle provider's bakery.
#### Usage
+
```
hal config provider oracle bakery base-image add BASE-IMAGE [parameters]
```
#### Parameters
+
`BASE-IMAGE`: The name of the base image to operate on.
- * `--base-image-id`: (*Required*) The OCID of the base image ID for the baking configuration.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--detailed-description`: A long description to help human operators identify the image.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--package-type`: This is used to help Spinnaker's bakery download the build artifacts you supply it with. For example, specifying 'deb' indicates that your artifacts will need to be fetched from a debian repository.
- * `--short-description`: A short description to help human operators identify the image.
- * `--ssh-user-name`: (*Required*) The ssh username for the baking configuration.
- * `--template-file`: This is the name of the packer template that will be used to bake images from this base image. The template file must be found in this list [https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer](https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer), or supplied as described here: [https://spinnaker.io/setup/bakery/](https://spinnaker.io/setup/bakery/)
+- `--base-image-id`: (_Required_) The OCID of the base image ID for the baking configuration.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--detailed-description`: A long description to help human operators identify the image.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--package-type`: This is used to help Spinnaker's bakery download the build artifacts you supply it with. For example, specifying 'deb' indicates that your artifacts will need to be fetched from a debian repository.
+- `--short-description`: A short description to help human operators identify the image.
+- `--ssh-user-name`: (_Required_) The ssh username for the baking configuration.
+- `--template-file`: This is the name of the packer template that will be used to bake images from this base image. The template file must be found in this list [https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer](https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer), or supplied as described here: [https://spinnaker.io/setup/bakery/](https://spinnaker.io/setup/bakery/)
---
+
## hal config provider oracle bakery base-image delete
Delete a specific oracle base image by name.
#### Usage
+
```
hal config provider oracle bakery base-image delete BASE-IMAGE [parameters]
```
#### Parameters
+
`BASE-IMAGE`: The name of the base image to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider oracle bakery base-image edit
Edit a base image for the oracle provider's bakery.
#### Usage
+
```
hal config provider oracle bakery base-image edit BASE-IMAGE [parameters]
```
#### Parameters
+
`BASE-IMAGE`: The name of the base image to operate on.
- * `--base-image-id`: The OCID of the base image ID for the baking configuration.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--detailed-description`: A long description to help human operators identify the image.
- * `--id`: This is the identifier used by your cloud to find this base image.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--package-type`: This is used to help Spinnaker's bakery download the build artifacts you supply it with. For example, specifying 'deb' indicates that your artifacts will need to be fetched from a debian repository.
- * `--short-description`: A short description to help human operators identify the image.
- * `--ssh-user-name`: The ssh username for the baking configuration.
- * `--template-file`: This is the name of the packer template that will be used to bake images from this base image. The template file must be found in this list [https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer](https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer), or supplied as described here: [https://spinnaker.io/setup/bakery/](https://spinnaker.io/setup/bakery/)
+- `--base-image-id`: The OCID of the base image ID for the baking configuration.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--detailed-description`: A long description to help human operators identify the image.
+- `--id`: This is the identifier used by your cloud to find this base image.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--package-type`: This is used to help Spinnaker's bakery download the build artifacts you supply it with. For example, specifying 'deb' indicates that your artifacts will need to be fetched from a debian repository.
+- `--short-description`: A short description to help human operators identify the image.
+- `--ssh-user-name`: The ssh username for the baking configuration.
+- `--template-file`: This is the name of the packer template that will be used to bake images from this base image. The template file must be found in this list [https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer](https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer), or supplied as described here: [https://spinnaker.io/setup/bakery/](https://spinnaker.io/setup/bakery/)
---
+
## hal config provider oracle bakery base-image get
Get the specified base image details for the oracle provider.
#### Usage
+
```
hal config provider oracle bakery base-image get BASE-IMAGE [parameters]
```
#### Parameters
+
`BASE-IMAGE`: The name of the base image to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider oracle bakery base-image list
List the base image names for the oracle provider.
#### Usage
+
```
hal config provider oracle bakery base-image list [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider oracle bakery edit
Edit the oracle provider's bakery default options.
#### Usage
+
```
hal config provider oracle bakery edit [parameters]
```
#### Parameters
- * `--availability-domain`: (*Required*) The name of the Availability Domain within which a new instance is launched and provisioned.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--instance-shape`: (*Required*) The shape for allocated to a newly created instance.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--subnet-id`: (*Required*) The name of the subnet within which a new instance is launched and provisioned.
- * `--template-file`: This is the name of the packer template that will be used to bake images from this base image. The template file must be found in this list [https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer](https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer), or supplied as described here: [https://spinnaker.io/setup/bakery/](https://spinnaker.io/setup/bakery/)
+- `--availability-domain`: (_Required_) The name of the Availability Domain within which a new instance is launched and provisioned.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--instance-shape`: (_Required_) The shape for allocated to a newly created instance.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--subnet-id`: (_Required_) The name of the subnet within which a new instance is launched and provisioned.
+- `--template-file`: This is the name of the packer template that will be used to bake images from this base image. The template file must be found in this list [https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer](https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer), or supplied as described here: [https://spinnaker.io/setup/bakery/](https://spinnaker.io/setup/bakery/)
---
+
## hal config provider oracle disable
Set the oracle provider as disabled
#### Usage
+
```
hal config provider oracle disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider oracle enable
Set the oracle provider as enabled
#### Usage
+
```
hal config provider oracle enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider tencentcloud
Manage and view Spinnaker configuration for the tencentcloud provider
#### Usage
+
```
hal config provider tencentcloud [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `account`: Manage and view Spinnaker configuration for the tencentcloud provider's account
- * `bakery`: Manage and view Spinnaker configuration for the tencentcloud provider's image bakery configuration.
- * `disable`: Set the tencentcloud provider as disabled
- * `enable`: Set the tencentcloud provider as enabled
+
+- `account`: Manage and view Spinnaker configuration for the tencentcloud provider's account
+- `bakery`: Manage and view Spinnaker configuration for the tencentcloud provider's image bakery configuration.
+- `disable`: Set the tencentcloud provider as disabled
+- `enable`: Set the tencentcloud provider as enabled
---
+
## hal config provider tencentcloud account
Manage and view Spinnaker configuration for the tencentcloud provider's account
#### Usage
+
```
hal config provider tencentcloud account ACCOUNT [parameters] [subcommands]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `add`: Add an account to the tencentcloud provider.
- * `delete`: Delete a specific tencentcloud account by name.
- * `edit`: Edit an account in the tencentcloud provider.
- * `get`: Get the specified account details for the tencentcloud provider.
- * `list`: List the account names for the tencentcloud provider.
+
+- `add`: Add an account to the tencentcloud provider.
+- `delete`: Delete a specific tencentcloud account by name.
+- `edit`: Edit an account in the tencentcloud provider.
+- `get`: Get the specified account details for the tencentcloud provider.
+- `list`: List the account names for the tencentcloud provider.
---
+
## hal config provider tencentcloud account add
Add an account to the tencentcloud provider.
#### Usage
+
```
hal config provider tencentcloud account add ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--environment`: The environment name for the account. Many accounts can share the same environment (e.g. dev, test, prod)
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--read-permissions`: (*Default*: `[]`) A user must have at least one of these roles in order to view this account's cloud resources.
- * `--regions`: The Tencent CLoud regions this Spinnaker account will manage.
- * `--required-group-membership`: (*Default*: `[]`) A user must be a member of at least one specified group in order to make changes to this account's cloud resources.
- * `--secret-id`: (*Required*) The secret id used to access Tencent Cloud.
- * `--secret-key`: (*Required*) (*Sensitive data* - user will be prompted on standard input) (Sensitive data - user will be prompted on standard input) The secret key used to access Tencent Cloud.
- * `--write-permissions`: (*Default*: `[]`) A user must have at least one of these roles in order to make changes to this account's cloud resources.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--environment`: The environment name for the account. Many accounts can share the same environment (e.g. dev, test, prod)
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--read-permissions`: (_Default_: `[]`) A user must have at least one of these roles in order to view this account's cloud resources.
+- `--regions`: The Tencent CLoud regions this Spinnaker account will manage.
+- `--required-group-membership`: (_Default_: `[]`) A user must be a member of at least one specified group in order to make changes to this account's cloud resources.
+- `--secret-id`: (_Required_) The secret id used to access Tencent Cloud.
+- `--secret-key`: (_Required_) (_Sensitive data_ - user will be prompted on standard input) (Sensitive data - user will be prompted on standard input) The secret key used to access Tencent Cloud.
+- `--write-permissions`: (_Default_: `[]`) A user must have at least one of these roles in order to make changes to this account's cloud resources.
---
+
## hal config provider tencentcloud account delete
Delete a specific tencentcloud account by name.
#### Usage
+
```
hal config provider tencentcloud account delete ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider tencentcloud account edit
Edit an account in the tencentcloud provider.
#### Usage
+
```
hal config provider tencentcloud account edit ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--add-read-permission`: Add this permission to the list of read permissions.
- * `--add-region`: Add this region to the list of managed regions.
- * `--add-required-group-membership`: Add this group to the list of required group memberships.
- * `--add-write-permission`: Add this permission to the list of write permissions.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--environment`: The environment name for the account. Many accounts can share the same environment (e.g. dev, test, prod)
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--read-permissions`: A user must have at least one of these roles in order to view this account's cloud resources.
- * `--regions`: The Tencent CLoud regions this Spinnaker account will manage.
- * `--remove-read-permission`: Remove this permission from the list of read permissions.
- * `--remove-region`: Remove this region from the list of managed regions.
- * `--remove-required-group-membership`: Remove this group from the list of required group memberships.
- * `--remove-write-permission`: Remove this permission to from list of write permissions.
- * `--required-group-membership`: A user must be a member of at least one specified group in order to make changes to this account's cloud resources.
- * `--secret-id`: The secret id used to access Tencent Cloud.
- * `--secret-key`: (*Sensitive data* - user will be prompted on standard input) (Sensitive data - user will be prompted on standard input) The secret key used to access Tencent Cloud.
- * `--write-permissions`: A user must have at least one of these roles in order to make changes to this account's cloud resources.
+- `--add-read-permission`: Add this permission to the list of read permissions.
+- `--add-region`: Add this region to the list of managed regions.
+- `--add-required-group-membership`: Add this group to the list of required group memberships.
+- `--add-write-permission`: Add this permission to the list of write permissions.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--environment`: The environment name for the account. Many accounts can share the same environment (e.g. dev, test, prod)
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--read-permissions`: A user must have at least one of these roles in order to view this account's cloud resources.
+- `--regions`: The Tencent CLoud regions this Spinnaker account will manage.
+- `--remove-read-permission`: Remove this permission from the list of read permissions.
+- `--remove-region`: Remove this region from the list of managed regions.
+- `--remove-required-group-membership`: Remove this group from the list of required group memberships.
+- `--remove-write-permission`: Remove this permission to from list of write permissions.
+- `--required-group-membership`: A user must be a member of at least one specified group in order to make changes to this account's cloud resources.
+- `--secret-id`: The secret id used to access Tencent Cloud.
+- `--secret-key`: (_Sensitive data_ - user will be prompted on standard input) (Sensitive data - user will be prompted on standard input) The secret key used to access Tencent Cloud.
+- `--write-permissions`: A user must have at least one of these roles in order to make changes to this account's cloud resources.
---
+
## hal config provider tencentcloud account get
Get the specified account details for the tencentcloud provider.
#### Usage
+
```
hal config provider tencentcloud account get ACCOUNT [parameters]
```
#### Parameters
+
`ACCOUNT`: The name of the account to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider tencentcloud account list
List the account names for the tencentcloud provider.
#### Usage
+
```
hal config provider tencentcloud account list [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider tencentcloud bakery
Manage and view Spinnaker configuration for the tencentcloud provider's image bakery configuration.
#### Usage
+
```
hal config provider tencentcloud bakery [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `base-image`: Manage and view Spinnaker configuration for the tencentcloud provider's base image.
- * `edit`: Edit the tencentcloud provider's bakery default options.
+
+- `base-image`: Manage and view Spinnaker configuration for the tencentcloud provider's base image.
+- `edit`: Edit the tencentcloud provider's bakery default options.
---
+
## hal config provider tencentcloud bakery base-image
Manage and view Spinnaker configuration for the tencentcloud provider's base image.
#### Usage
+
```
hal config provider tencentcloud bakery base-image [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `add`: Add a base image for the tencentcloud provider's bakery.
- * `delete`: Delete a specific tencentcloud base image by name.
- * `edit`: Edit a base image for the tencentcloud provider's bakery.
- * `get`: Get the specified base image details for the tencentcloud provider.
- * `list`: List the base image names for the tencentcloud provider.
+
+- `add`: Add a base image for the tencentcloud provider's bakery.
+- `delete`: Delete a specific tencentcloud base image by name.
+- `edit`: Edit a base image for the tencentcloud provider's bakery.
+- `get`: Get the specified base image details for the tencentcloud provider.
+- `list`: List the base image names for the tencentcloud provider.
---
+
## hal config provider tencentcloud bakery base-image add
Add a base image for the tencentcloud provider's bakery.
#### Usage
+
```
hal config provider tencentcloud bakery base-image add BASE-IMAGE [parameters]
```
#### Parameters
+
`BASE-IMAGE`: The name of the base image to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--detailed-description`: A long description to help human operators identify the image.
- * `--instance-type`: (*Required*) The instance type for the baking configuration.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--package-type`: This is used to help Spinnaker's bakery download the build artifacts you supply it with. For example, specifying 'deb' indicates that your artifacts will need to be fetched from a debian repository.
- * `--region`: (*Required*) The region for the baking configuration.
- * `--short-description`: A short description to help human operators identify the image.
- * `--source-image-id`: (*Required*) The source image ID for the baking configuration.
- * `--ssh-user-name`: (*Required*) The ssh username for the baking configuration.
- * `--template-file`: This is the name of the packer template that will be used to bake images from this base image. The template file must be found in this list [https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer](https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer), or supplied as described here: [https://spinnaker.io/setup/bakery/](https://spinnaker.io/setup/bakery/)
- * `--zone`: (*Required*) The zone for the baking configuration.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--detailed-description`: A long description to help human operators identify the image.
+- `--instance-type`: (_Required_) The instance type for the baking configuration.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--package-type`: This is used to help Spinnaker's bakery download the build artifacts you supply it with. For example, specifying 'deb' indicates that your artifacts will need to be fetched from a debian repository.
+- `--region`: (_Required_) The region for the baking configuration.
+- `--short-description`: A short description to help human operators identify the image.
+- `--source-image-id`: (_Required_) The source image ID for the baking configuration.
+- `--ssh-user-name`: (_Required_) The ssh username for the baking configuration.
+- `--template-file`: This is the name of the packer template that will be used to bake images from this base image. The template file must be found in this list [https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer](https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer), or supplied as described here: [https://spinnaker.io/setup/bakery/](https://spinnaker.io/setup/bakery/)
+- `--zone`: (_Required_) The zone for the baking configuration.
---
+
## hal config provider tencentcloud bakery base-image delete
Delete a specific tencentcloud base image by name.
#### Usage
+
```
hal config provider tencentcloud bakery base-image delete BASE-IMAGE [parameters]
```
#### Parameters
+
`BASE-IMAGE`: The name of the base image to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider tencentcloud bakery base-image edit
Edit a base image for the tencentcloud provider's bakery.
#### Usage
+
```
hal config provider tencentcloud bakery base-image edit BASE-IMAGE [parameters]
```
#### Parameters
+
`BASE-IMAGE`: The name of the base image to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--detailed-description`: A long description to help human operators identify the image.
- * `--id`: This is the identifier used by your cloud to find this base image.
- * `--instance-type`: (*Required*) The instance type for the baking configuration.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--package-type`: This is used to help Spinnaker's bakery download the build artifacts you supply it with. For example, specifying 'deb' indicates that your artifacts will need to be fetched from a debian repository.
- * `--region`: (*Required*) The region for the baking configuration.
- * `--short-description`: A short description to help human operators identify the image.
- * `--source-image-id`: (*Required*) The source image ID for the baking configuration.
- * `--ssh-user-name`: (*Required*) The ssh username for the baking configuration.
- * `--template-file`: This is the name of the packer template that will be used to bake images from this base image. The template file must be found in this list [https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer](https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer), or supplied as described here: [https://spinnaker.io/setup/bakery/](https://spinnaker.io/setup/bakery/)
- * `--zone`: (*Required*) The zone for the baking configuration.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--detailed-description`: A long description to help human operators identify the image.
+- `--id`: This is the identifier used by your cloud to find this base image.
+- `--instance-type`: (_Required_) The instance type for the baking configuration.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--package-type`: This is used to help Spinnaker's bakery download the build artifacts you supply it with. For example, specifying 'deb' indicates that your artifacts will need to be fetched from a debian repository.
+- `--region`: (_Required_) The region for the baking configuration.
+- `--short-description`: A short description to help human operators identify the image.
+- `--source-image-id`: (_Required_) The source image ID for the baking configuration.
+- `--ssh-user-name`: (_Required_) The ssh username for the baking configuration.
+- `--template-file`: This is the name of the packer template that will be used to bake images from this base image. The template file must be found in this list [https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer](https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer), or supplied as described here: [https://spinnaker.io/setup/bakery/](https://spinnaker.io/setup/bakery/)
+- `--zone`: (_Required_) The zone for the baking configuration.
---
+
## hal config provider tencentcloud bakery base-image get
Get the specified base image details for the tencentcloud provider.
#### Usage
+
```
hal config provider tencentcloud bakery base-image get BASE-IMAGE [parameters]
```
#### Parameters
+
`BASE-IMAGE`: The name of the base image to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider tencentcloud bakery base-image list
List the base image names for the tencentcloud provider.
#### Usage
+
```
hal config provider tencentcloud bakery base-image list [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider tencentcloud bakery edit
Edit the tencentcloud provider's bakery default options.
#### Usage
+
```
hal config provider tencentcloud bakery edit [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--secret-id`: (*Required*) The default access key used to communicate with AWS.
- * `--secret-key`: (*Required*) (*Sensitive data* - user will be prompted on standard input) The secret key used to communicate with AWS.
- * `--template-file`: This is the name of the packer template that will be used to bake images from this base image. The template file must be found in this list [https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer](https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer), or supplied as described here: [https://spinnaker.io/setup/bakery/](https://spinnaker.io/setup/bakery/)
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--secret-id`: (_Required_) The default access key used to communicate with AWS.
+- `--secret-key`: (_Required_) (_Sensitive data_ - user will be prompted on standard input) The secret key used to communicate with AWS.
+- `--template-file`: This is the name of the packer template that will be used to bake images from this base image. The template file must be found in this list [https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer](https://github.com/spinnaker/rosco/tree/master/rosco-web/config/packer), or supplied as described here: [https://spinnaker.io/setup/bakery/](https://spinnaker.io/setup/bakery/)
---
+
## hal config provider tencentcloud disable
Set the tencentcloud provider as disabled
#### Usage
+
```
hal config provider tencentcloud disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config provider tencentcloud enable
Set the tencentcloud provider as enabled
#### Usage
+
```
hal config provider tencentcloud enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config pubsub
Configure, validate, and view the specified pubsub.
#### Usage
+
```
hal config pubsub [subcommands]
```
#### Subcommands
- * `google`: Manage and view Spinnaker configuration for the google pubsub
+
+- `google`: Manage and view Spinnaker configuration for the google pubsub
---
+
## hal config pubsub google
Manage and view Spinnaker configuration for the google pubsub
#### Usage
+
```
hal config pubsub google [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `disable`: Set the google pubsub as disabled
- * `enable`: Set the google pubsub as enabled
- * `subscription`: Manage and view Spinnaker configuration for the google pubsub's subscription
+
+- `disable`: Set the google pubsub as disabled
+- `enable`: Set the google pubsub as enabled
+- `subscription`: Manage and view Spinnaker configuration for the google pubsub's subscription
---
+
## hal config pubsub google disable
Set the google pubsub as disabled
#### Usage
+
```
hal config pubsub google disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config pubsub google enable
Set the google pubsub as enabled
#### Usage
+
```
hal config pubsub google enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config pubsub google subscription
Manage and view Spinnaker configuration for the google pubsub's subscription
#### Usage
+
```
hal config pubsub google subscription SUBSCRIPTION [parameters] [subcommands]
```
#### Parameters
+
`SUBSCRIPTION`: The name of the subscription to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `add`: Add an subscription to the google pubsub.
- * `delete`: Delete a specific google subscription by name.
- * `edit`: Edit an subscription in the google pubsub.
- * `get`: Get the specified subscription details for the google pubsub.
- * `list`: List the subscription names for the google pubsub.
+
+- `add`: Add an subscription to the google pubsub.
+- `delete`: Delete a specific google subscription by name.
+- `edit`: Edit an subscription in the google pubsub.
+- `get`: Get the specified subscription details for the google pubsub.
+- `list`: List the subscription names for the google pubsub.
---
+
## hal config pubsub google subscription add
Add an subscription to the google pubsub.
#### Usage
+
```
hal config pubsub google subscription add SUBSCRIPTION [parameters]
```
#### Parameters
+
`SUBSCRIPTION`: The name of the subscription to operate on.
- * `--ack-deadline-seconds`: (*Default*: `10`) Time in seconds before an outstanding message is considered unacknowledged and is re-sent.
-Configurable in your Google Cloud Pubsub subscription. See the docs here: [https://cloud.google.com/pubsub/docs/subscriber](https://cloud.google.com/pubsub/docs/subscriber)
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--json-path`: The path to a JSON service account that Spinnaker will use as credentials. This is only needed if Spinnaker is not deployed on a Google Compute Engine VM, or needs permissions not afforded to the VM it is running on. See [https://cloud.google.com/compute/docs/access/service-accounts](https://cloud.google.com/compute/docs/access/service-accounts) for more information.
- * `--message-format`: (*Default*: `CUSTOM`) One of 'GCB', 'GCS', 'GCR', or 'CUSTOM'. This can be used to help Spinnaker translate the contents of the
-Pub/Sub message into Spinnaker artifacts.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--project`: The name of the GCP project your subscription lives in.
- * `--subscription-name`: The name of the subscription to listen to. This identifier does not include the name of the project, and must already be configured for Spinnaker to work.
- * `--template-path`: A path to a jinja template that specifies how artifacts from this pubsub system are interpreted and transformed into Spinnaker artifacts. See spinnaker.io/reference/artifacts for more information.
+- `--ack-deadline-seconds`: (_Default_: `10`) Time in seconds before an outstanding message is considered unacknowledged and is re-sent.
+ Configurable in your Google Cloud Pubsub subscription. See the docs here: [https://cloud.google.com/pubsub/docs/subscriber](https://cloud.google.com/pubsub/docs/subscriber)
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--json-path`: The path to a JSON service account that Spinnaker will use as credentials. This is only needed if Spinnaker is not deployed on a Google Compute Engine VM, or needs permissions not afforded to the VM it is running on. See [https://cloud.google.com/compute/docs/access/service-accounts](https://cloud.google.com/compute/docs/access/service-accounts) for more information.
+- `--message-format`: (_Default_: `CUSTOM`) One of 'GCB', 'GCS', 'GCR', or 'CUSTOM'. This can be used to help Spinnaker translate the contents of the
+ Pub/Sub message into Spinnaker artifacts.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--project`: The name of the GCP project your subscription lives in.
+- `--subscription-name`: The name of the subscription to listen to. This identifier does not include the name of the project, and must already be configured for Spinnaker to work.
+- `--template-path`: A path to a jinja template that specifies how artifacts from this pubsub system are interpreted and transformed into Spinnaker artifacts. See spinnaker.io/reference/artifacts for more information.
---
+
## hal config pubsub google subscription delete
Delete a specific google subscription by name.
#### Usage
+
```
hal config pubsub google subscription delete SUBSCRIPTION [parameters]
```
#### Parameters
+
`SUBSCRIPTION`: The name of the subscription to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config pubsub google subscription edit
Edit an subscription in the google pubsub.
#### Usage
+
```
hal config pubsub google subscription edit SUBSCRIPTION [parameters]
```
#### Parameters
+
`SUBSCRIPTION`: The name of the subscription to operate on.
- * `--ack-deadline-seconds`: Time in seconds before an outstanding message is considered unacknowledged and is re-sent.
-Configurable in your Google Cloud Pubsub subscription. See the docs here: [https://cloud.google.com/pubsub/docs/subscriber](https://cloud.google.com/pubsub/docs/subscriber)
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--json-path`: The path to a JSON service account that Spinnaker will use as credentials. This is only needed if Spinnaker is not deployed on a Google Compute Engine VM, or needs permissions not afforded to the VM it is running on. See [https://cloud.google.com/compute/docs/access/service-accounts](https://cloud.google.com/compute/docs/access/service-accounts) for more information.
- * `--message-format`: One of 'GCB', 'GCS', 'GCR', or 'CUSTOM'. This can be used to help Spinnaker translate the contents of the
-Pub/Sub message into Spinnaker artifacts.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--project`: The name of the GCP project your subscription lives in.
- * `--subscription-name`: The name of the subscription to listen to. This identifier does not include the name of the project, and must already be configured for Spinnaker to work.
- * `--template-path`: A path to a jinja template that specifies how artifacts from this pubsub system are interpreted and transformed into Spinnaker artifacts. See spinnaker.io/reference/artifacts for more information.
+- `--ack-deadline-seconds`: Time in seconds before an outstanding message is considered unacknowledged and is re-sent.
+ Configurable in your Google Cloud Pubsub subscription. See the docs here: [https://cloud.google.com/pubsub/docs/subscriber](https://cloud.google.com/pubsub/docs/subscriber)
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--json-path`: The path to a JSON service account that Spinnaker will use as credentials. This is only needed if Spinnaker is not deployed on a Google Compute Engine VM, or needs permissions not afforded to the VM it is running on. See [https://cloud.google.com/compute/docs/access/service-accounts](https://cloud.google.com/compute/docs/access/service-accounts) for more information.
+- `--message-format`: One of 'GCB', 'GCS', 'GCR', or 'CUSTOM'. This can be used to help Spinnaker translate the contents of the
+ Pub/Sub message into Spinnaker artifacts.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--project`: The name of the GCP project your subscription lives in.
+- `--subscription-name`: The name of the subscription to listen to. This identifier does not include the name of the project, and must already be configured for Spinnaker to work.
+- `--template-path`: A path to a jinja template that specifies how artifacts from this pubsub system are interpreted and transformed into Spinnaker artifacts. See spinnaker.io/reference/artifacts for more information.
---
+
## hal config pubsub google subscription get
Get the specified subscription details for the google pubsub.
#### Usage
+
```
hal config pubsub google subscription get SUBSCRIPTION [parameters]
```
#### Parameters
+
`SUBSCRIPTION`: The name of the subscription to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config pubsub google subscription list
List the subscription names for the google pubsub.
#### Usage
+
```
hal config pubsub google subscription list [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config repository
Configure, validate, and view the specified repository.
#### Usage
+
```
hal config repository [subcommands]
```
#### Subcommands
- * `artifactory`: Manage and view Spinnaker configuration for the artifactory repository
+
+- `artifactory`: Manage and view Spinnaker configuration for the artifactory repository
---
+
## hal config repository artifactory
Manage and view Spinnaker configuration for the artifactory repository
#### Usage
+
```
hal config repository artifactory [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `disable`: Set the artifactory repository as disabled
- * `enable`: Set the artifactory repository as enabled
- * `search`: Manage and view Spinnaker configuration for the artifactory repository services's search
+
+- `disable`: Set the artifactory repository as disabled
+- `enable`: Set the artifactory repository as enabled
+- `search`: Manage and view Spinnaker configuration for the artifactory repository services's search
---
+
## hal config repository artifactory disable
Set the artifactory repository as disabled
#### Usage
+
```
hal config repository artifactory disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config repository artifactory enable
Set the artifactory repository as enabled
#### Usage
+
```
hal config repository artifactory enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config repository artifactory search
Manage and view Spinnaker configuration for the artifactory repository services's search
#### Usage
+
```
hal config repository artifactory search SEARCH [parameters] [subcommands]
```
#### Parameters
+
`SEARCH`: The name of the search to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `add`: Add a search for the artifactory repository service.
- * `delete`: Delete a specific artifactory search by name.
- * `edit`: Edit a search for the artifactory repository service.
- * `get`: Get the specified search details for artifactory.
- * `list`: List the search names for artifactory.
+
+- `add`: Add a search for the artifactory repository service.
+- `delete`: Delete a specific artifactory search by name.
+- `edit`: Edit a search for the artifactory repository service.
+- `get`: Get the specified search details for artifactory.
+- `list`: List the search names for artifactory.
---
+
## hal config repository artifactory search add
Add a search for the artifactory repository service.
#### Usage
+
```
hal config repository artifactory search add SEARCH [parameters]
```
#### Parameters
+
`SEARCH`: The name of the search to operate on.
- * `--base-url`: (*Required*) The base url your artifactory search is reachable at.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--groupId`: The group id in your artifactory to be searched.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--password`: (*Required*) (*Sensitive data* - user will be prompted on standard input) The password of the artifactory user to authenticate as.
- * `--read-permissions`: (*Default*: `[]`) A user must have at least one of these roles in order to view this build search or use it as a trigger source.
- * `--repo`: (*Required*) The repo in your artifactory to be searched.
- * `--repo-type`: (*Default*: `MAVEN`) The package type of repo in your artifactory to be searched.
- * `--username`: (*Required*) The username of the artifactory user to authenticate as.
- * `--write-permissions`: (*Default*: `[]`) A user must have at least one of these roles in order to be able to run jobs on this build search.
+- `--base-url`: (_Required_) The base url your artifactory search is reachable at.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--groupId`: The group id in your artifactory to be searched.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--password`: (_Required_) (_Sensitive data_ - user will be prompted on standard input) The password of the artifactory user to authenticate as.
+- `--read-permissions`: (_Default_: `[]`) A user must have at least one of these roles in order to view this build search or use it as a trigger source.
+- `--repo`: (_Required_) The repo in your artifactory to be searched.
+- `--repo-type`: (_Default_: `MAVEN`) The package type of repo in your artifactory to be searched.
+- `--username`: (_Required_) The username of the artifactory user to authenticate as.
+- `--write-permissions`: (_Default_: `[]`) A user must have at least one of these roles in order to be able to run jobs on this build search.
---
+
## hal config repository artifactory search delete
Delete a specific artifactory search by name.
#### Usage
+
```
hal config repository artifactory search delete SEARCH [parameters]
```
#### Parameters
+
`SEARCH`: The name of the search to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config repository artifactory search edit
Edit a search for the artifactory repository service.
#### Usage
+
```
hal config repository artifactory search edit SEARCH [parameters]
```
#### Parameters
+
`SEARCH`: The name of the search to operate on.
- * `--add-read-permission`: Add this permission to the list of read permissions.
- * `--add-write-permission`: Add this permission to the list of write permissions.
- * `--base-url`: The base url your artifactory search is reachable at.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--groupId`: The group id in your artifactory to be searched.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--password`: The password of the artifactory user to authenticate as.
- * `--read-permissions`: A user must have at least one of these roles in order to view this build search or use it as a trigger source.
- * `--remove-read-permission`: Remove this permission from the list of read permissions.
- * `--remove-write-permission`: Remove this permission from the list of write permissions.
- * `--repo`: The repo in your artifactory to be searched.
- * `--repo-type`: The package type of repo in your artifactory to be searched.
- * `--username`: The username of the artifactory user to authenticate as.
- * `--write-permissions`: A user must have at least one of these roles in order to be able to run jobs on this build search.
+- `--add-read-permission`: Add this permission to the list of read permissions.
+- `--add-write-permission`: Add this permission to the list of write permissions.
+- `--base-url`: The base url your artifactory search is reachable at.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--groupId`: The group id in your artifactory to be searched.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--password`: The password of the artifactory user to authenticate as.
+- `--read-permissions`: A user must have at least one of these roles in order to view this build search or use it as a trigger source.
+- `--remove-read-permission`: Remove this permission from the list of read permissions.
+- `--remove-write-permission`: Remove this permission from the list of write permissions.
+- `--repo`: The repo in your artifactory to be searched.
+- `--repo-type`: The package type of repo in your artifactory to be searched.
+- `--username`: The username of the artifactory user to authenticate as.
+- `--write-permissions`: A user must have at least one of these roles in order to be able to run jobs on this build search.
---
+
## hal config repository artifactory search get
Get the specified search details for artifactory.
#### Usage
+
```
hal config repository artifactory search get SEARCH [parameters]
```
#### Parameters
+
`SEARCH`: The name of the search to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config repository artifactory search list
List the search names for artifactory.
#### Usage
+
```
hal config repository artifactory search list [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config security
Configure Spinnaker's security. This includes external SSL, authentication mechanisms, and authorization policies.
#### Usage
+
```
hal config security [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `api`: Configure and view the API server's addressable URL and CORS policies.
- * `authn`: Configure your authentication settings for Spinnaker.
- * `authz`: Configure your authorization settings for Spinnaker.
- * `ui`: Configure and view the UI server's addressable URL.
+
+- `api`: Configure and view the API server's addressable URL and CORS policies.
+- `authn`: Configure your authentication settings for Spinnaker.
+- `authz`: Configure your authorization settings for Spinnaker.
+- `ui`: Configure and view the UI server's addressable URL.
---
+
## hal config security api
Configure and view the API server's addressable URL and CORS policies.
#### Usage
+
```
hal config security api [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `edit`: Configure access policies specific to Spinnaker's API server.
- * `ssl`: Configure and view SSL settings for Spinnaker's API gateway.
+
+- `edit`: Configure access policies specific to Spinnaker's API server.
+- `ssl`: Configure and view SSL settings for Spinnaker's API gateway.
---
+
## hal config security api edit
When Spinnaker is deployed to a remote host, the API server may be configured to accept auth requests from alternate sources, do SSL termination, or sit behind an externally configured proxy server or load balancer.
#### Usage
+
```
hal config security api edit [parameters]
```
#### Parameters
- * `--cors-access-pattern`: If you have authentication enabled, are accessing Spinnaker remotely, and are logging in from sources other than the UI, provide a regex matching all URLs authentication redirects may come from.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--override-base-url`: If you are accessing the API server remotely, provide the full base URL of whatever proxy or load balancer is fronting the API requests.
+- `--cors-access-pattern`: If you have authentication enabled, are accessing Spinnaker remotely, and are logging in from sources other than the UI, provide a regex matching all URLs authentication redirects may come from.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--override-base-url`: If you are accessing the API server remotely, provide the full base URL of whatever proxy or load balancer is fronting the API requests.
---
+
## hal config security api ssl
If you want the API server to do SSL termination, it must be enabled and configured here. If you are doing your own SSL termination, leave this disabled.
#### Usage
+
```
hal config security api ssl [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `disable`: Disable SSL for the API gateway.
- * `edit`: Edit SSL settings for your API server.
- * `enable`: Enable SSL for the API gateway.
+
+- `disable`: Disable SSL for the API gateway.
+- `edit`: Edit SSL settings for your API server.
+- `enable`: Enable SSL for the API gateway.
---
+
## hal config security api ssl disable
Disable SSL for the API gateway.
#### Usage
+
```
hal config security api ssl disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config security api ssl edit
Configure SSL termination to handled by the API server's Tomcat server.
#### Usage
+
```
hal config security api ssl edit [parameters]
```
#### Parameters
- * `--client-auth`: Declare 'WANT' when client auth is wanted but not mandatory, or 'NEED', when client auth is mandatory.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--key-alias`: Name of your keystore entry as generated with your keytool.
- * `--keystore`: Path to the keystore holding your security certificates.
- * `--keystore-password`: (*Sensitive data* - user will be prompted on standard input) The password to unlock your keystore. Due to a limitation in Tomcat, this must match your key's password in the keystore.
- * `--keystore-type`: The type of your keystore. Examples include JKS, and PKCS12.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--truststore`: Path to the truststore holding your trusted certificates.
- * `--truststore-password`: (*Sensitive data* - user will be prompted on standard input) The password to unlock your truststore.
- * `--truststore-type`: The type of your truststore. Examples include JKS, and PKCS12.
+- `--client-auth`: Declare 'WANT' when client auth is wanted but not mandatory, or 'NEED', when client auth is mandatory.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--key-alias`: Name of your keystore entry as generated with your keytool.
+- `--keystore`: Path to the keystore holding your security certificates.
+- `--keystore-password`: (_Sensitive data_ - user will be prompted on standard input) The password to unlock your keystore. Due to a limitation in Tomcat, this must match your key's password in the keystore.
+- `--keystore-type`: The type of your keystore. Examples include JKS, and PKCS12.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--truststore`: Path to the truststore holding your trusted certificates.
+- `--truststore-password`: (_Sensitive data_ - user will be prompted on standard input) The password to unlock your truststore.
+- `--truststore-type`: The type of your truststore. Examples include JKS, and PKCS12.
---
+
## hal config security api ssl enable
Enable SSL for the API gateway.
#### Usage
+
```
hal config security api ssl enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config security authn
This set of commands allows you to configure how users can authenticate against Spinnaker.
#### Usage
+
```
hal config security authn [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `iap`: Configure the iap method for authenticating.
- * `ldap`: Configure the ldap method for authenticating.
- * `oauth2`: Configure the oauth2 method for authenticating.
- * `saml`: Configure the saml method for authenticating.
- * `x509`: Configure the x509 method for authenticating.
+
+- `iap`: Configure the iap method for authenticating.
+- `ldap`: Configure the ldap method for authenticating.
+- `oauth2`: Configure the oauth2 method for authenticating.
+- `saml`: Configure the saml method for authenticating.
+- `x509`: Configure the x509 method for authenticating.
---
+
## hal config security authn iap
Configure the iap method for authenticating.
#### Usage
+
```
hal config security authn iap [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `disable`: Set the iap method as disabled
- * `edit`: Configure authentication using the Google Cloud Identity-Aware Proxy authentication model.
- * `enable`: Set the iap method as enabled
+
+- `disable`: Set the iap method as disabled
+- `edit`: Configure authentication using the Google Cloud Identity-Aware Proxy authentication model.
+- `enable`: Set the iap method as enabled
---
+
## hal config security authn iap disable
Set the iap method as disabled
#### Usage
+
```
hal config security authn iap disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config security authn iap edit
Google Cloud Identity-Aware Proxy (IAP) is an authentication model that utilizes Google OAuth2.0 and an authorization service to provide access control for users of GCP. After a user has been authenticated and authorized by IAP's service, a JWT token is passed along which Spinnaker uses to check for authenticity and to get the user email from the payload and sign the user in. To configure IAP, set the audience field retrieved from the IAP console.
#### Usage
+
```
hal config security authn iap edit [parameters]
```
#### Parameters
- * `--audience`: The Audience from the ID token payload. You can retrieve this field from the IAP console: [https://cloud.google.com/iap/docs/signed-headers-howto#verify_the_id_token_header](https://cloud.google.com/iap/docs/signed-headers-howto#verify_the_id_token_header).
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--iap-verify-key-url`: The URL containing the Cloud IAP public keys in JWK format.
- * `--issuer-id`: The Issuer from the ID token payload.
- * `--jwt-header`: The HTTP request header that contains the JWT token.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--audience`: The Audience from the ID token payload. You can retrieve this field from the IAP console: [https://cloud.google.com/iap/docs/signed-headers-howto#verify_the_id_token_header](https://cloud.google.com/iap/docs/signed-headers-howto#verify_the_id_token_header).
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--iap-verify-key-url`: The URL containing the Cloud IAP public keys in JWK format.
+- `--issuer-id`: The Issuer from the ID token payload.
+- `--jwt-header`: The HTTP request header that contains the JWT token.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config security authn iap enable
Set the iap method as enabled
#### Usage
+
```
hal config security authn iap enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config security authn ldap
Configure the ldap method for authenticating.
#### Usage
+
```
hal config security authn ldap [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `disable`: Set the ldap method as disabled
- * `edit`: Configure authentication using a LDAP identity provider.
- * `enable`: Set the ldap method as enabled
+
+- `disable`: Set the ldap method as disabled
+- `edit`: Configure authentication using a LDAP identity provider.
+- `enable`: Set the ldap method as enabled
---
+
## hal config security authn ldap disable
Set the ldap method as disabled
#### Usage
+
```
hal config security authn ldap disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config security authn ldap edit
Lightweight Directory Access Protocol (LDAP) is a standard way many organizations maintain user credentials and group memberships. Spinnaker uses the standard 'bind' approach for user authentication. This is a fancy way of saying that Gate uses your username and password to login to the LDAP server, and if the connection is successful, you're considered authenticated.
#### Usage
+
```
hal config security authn ldap edit [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--group-search-base`: The part of the directory tree under which group searches should be performed.
- * `--manager-dn`: An LDAP manager user is required for binding to the LDAP server for the user authentication process. This property refers to the DN of that entry. I.e. this is not the user which will be authenticated when logging into DHIS2, rather the user which binds to the LDAP server in order to do the authentication.
- * `--manager-password`: (*Sensitive data* - user will be prompted on standard input) The password for the LDAP manager user.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--url`: ldap:// or ldaps:// url of the LDAP server
- * `--user-dn-pattern`: The pattern for finding a user's DN using simple pattern matching. For example, if your LDAP server has the URL [ldap://mysite.com/dc=spinnaker,dc=org](ldap://mysite.com/dc=spinnaker,dc=org), and you have the pattern 'uid={0},ou=members', 'me' will map to a DN uid=me,ou=members,dc=spinnaker,dc=org. If no match is found, will try to find the user using user-search-filter, if set.
- * `--user-search-base`: The part of the directory tree under which user searches should be performed. If user-search-base isn't supplied, the search will be performed from the root.
- * `--user-search-filter`: The filter to use when searching for a user's DN. Will search either from user-search-base (if specified) or root for entires matching the filter, then attempt to bind as that user with the login password. For example, the filter 'uid={0}' would apply to any user where uid matched the user's login name. If --user-dn-pattern is also specified, will attempt to find a match using the specified pattern first, before searching with the specified search filter if no match is found from the pattern.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--group-search-base`: The part of the directory tree under which group searches should be performed.
+- `--manager-dn`: An LDAP manager user is required for binding to the LDAP server for the user authentication process. This property refers to the DN of that entry. I.e. this is not the user which will be authenticated when logging into DHIS2, rather the user which binds to the LDAP server in order to do the authentication.
+- `--manager-password`: (_Sensitive data_ - user will be prompted on standard input) The password for the LDAP manager user.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--url`: ldap:// or ldaps:// url of the LDAP server
+- `--user-dn-pattern`: The pattern for finding a user's DN using simple pattern matching. For example, if your LDAP server has the URL [ldap://mysite.com/dc=spinnaker,dc=org](ldap://mysite.com/dc=spinnaker,dc=org), and you have the pattern 'uid={0},ou=members', 'me' will map to a DN uid=me,ou=members,dc=spinnaker,dc=org. If no match is found, will try to find the user using user-search-filter, if set.
+- `--user-search-base`: The part of the directory tree under which user searches should be performed. If user-search-base isn't supplied, the search will be performed from the root.
+- `--user-search-filter`: The filter to use when searching for a user's DN. Will search either from user-search-base (if specified) or root for entires matching the filter, then attempt to bind as that user with the login password. For example, the filter 'uid={0}' would apply to any user where uid matched the user's login name. If --user-dn-pattern is also specified, will attempt to find a match using the specified pattern first, before searching with the specified search filter if no match is found from the pattern.
---
+
## hal config security authn ldap enable
Set the ldap method as enabled
#### Usage
+
```
hal config security authn ldap enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config security authn oauth2
Configure the oauth2 method for authenticating.
#### Usage
+
```
hal config security authn oauth2 [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `disable`: Set the oauth2 method as disabled
- * `edit`: Edit the oauth2 authentication method.
- * `enable`: Set the oauth2 method as enabled
+
+- `disable`: Set the oauth2 method as disabled
+- `edit`: Edit the oauth2 authentication method.
+- `enable`: Set the oauth2 method as enabled
---
+
## hal config security authn oauth2 disable
Set the oauth2 method as disabled
#### Usage
+
```
hal config security authn oauth2 disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config security authn oauth2 edit
Edit the oauth2 authentication method.
#### Usage
+
```
hal config security authn oauth2 edit [parameters]
```
#### Parameters
- * `--access-token-uri`: The access token uri for your OAuth provider.
- * `--client-authentication-scheme`: The client authentication scheme for your OAuth provider.
- * `--client-id`: The OAuth client ID you have configured with your OAuth provider.
- * `--client-secret`: The OAuth client secret you have configured with your OAuth provider.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--pre-established-redirect-uri`: The externally accessible URL for Gate. For use with load balancers that do any kind of address manipulation for Gate traffic, such as an SSL terminating load balancer.
- * `--provider`: The OAuth provider handling authentication. The supported options are Google, GitHub, Oracle, Azure and Other
- * `--scope`: The scope for your OAuth provider.
- * `--user-authorization-uri`: The user authorization uri for your OAuth provider.
- * `--user-info-mapping-email`: The email field returned from your OAuth provider.
- * `--user-info-mapping-first-name`: The first name field returned from your OAuth provider.
- * `--user-info-mapping-last-name`: The last name field returned from your OAuth provider.
- * `--user-info-mapping-username`: The username field returned from your OAuth provider.
- * `--user-info-requirements`: (*Default*: `(empty)`) The map of requirements the userInfo request must have. This is used to restrict user login to specific domains or having a specific attribute. Use equal signs between key and value, and additional key/value pairs need to repeat the flag. Example: '--user-info-requirements foo=bar --userInfoRequirements baz=qux'.
- * `--user-info-uri`: The user info uri for your OAuth provider.
+- `--access-token-uri`: The access token uri for your OAuth provider.
+- `--client-authentication-scheme`: The client authentication scheme for your OAuth provider.
+- `--client-id`: The OAuth client ID you have configured with your OAuth provider.
+- `--client-secret`: The OAuth client secret you have configured with your OAuth provider.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--pre-established-redirect-uri`: The externally accessible URL for Gate. For use with load balancers that do any kind of address manipulation for Gate traffic, such as an SSL terminating load balancer.
+- `--provider`: The OAuth provider handling authentication. The supported options are Google, GitHub, Oracle, Azure and Other
+- `--scope`: The scope for your OAuth provider.
+- `--user-authorization-uri`: The user authorization uri for your OAuth provider.
+- `--user-info-mapping-email`: The email field returned from your OAuth provider.
+- `--user-info-mapping-first-name`: The first name field returned from your OAuth provider.
+- `--user-info-mapping-last-name`: The last name field returned from your OAuth provider.
+- `--user-info-mapping-username`: The username field returned from your OAuth provider.
+- `--user-info-requirements`: (_Default_: `(empty)`) The map of requirements the userInfo request must have. This is used to restrict user login to specific domains or having a specific attribute. Use equal signs between key and value, and additional key/value pairs need to repeat the flag. Example: '--user-info-requirements foo=bar --userInfoRequirements baz=qux'.
+- `--user-info-uri`: The user info uri for your OAuth provider.
---
+
## hal config security authn oauth2 enable
Set the oauth2 method as enabled
#### Usage
+
```
hal config security authn oauth2 enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config security authn saml
Configure the saml method for authenticating.
#### Usage
+
```
hal config security authn saml [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `disable`: Set the saml method as disabled
- * `edit`: Configure authentication using a SAML identity provider.
- * `enable`: Set the saml method as enabled
+
+- `disable`: Set the saml method as disabled
+- `edit`: Configure authentication using a SAML identity provider.
+- `enable`: Set the saml method as enabled
---
+
## hal config security authn saml disable
Set the saml method as disabled
#### Usage
+
```
hal config security authn saml disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config security authn saml edit
-SAML authenticates users by passing cryptographically signed XML documents between the Gate server and an identity provider. Gate's key is stored and accessed via the --keystore parameters, while the identity provider's keys are included in the metadata.xml. Finally, the identity provider must redirect the control flow (through the user's browser) back to Gate by way of the --serviceAddressUrl. This is likely the address of Gate's load balancer.
+SAML authenticates users by passing cryptographically signed XML documents between the Gate server and an identity provider. Gate's key is stored and accessed via the --keystore parameters, while the identity provider's keys are included in the metadata.xml. Finally, the identity provider must redirect the control flow (through the user's browser) back to Gate by way of the --serviceAddressUrl. This is likely the address of Gate's load balancer.
#### Usage
+
```
hal config security authn saml edit [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--issuer-id`: The identity of the Spinnaker application registered with the SAML provider.
- * `--keystore`: Path to the keystore that contains this server's private key. This key is used to cryptographically sign SAML AuthNRequest objects.
- * `--keystore-alias`: The name of the alias under which this server's private key is stored in the --keystore file.
- * `--keystore-password`: The password used to access the file specified in --keystore
- * `--metadata`: The address to your identity provider's metadata XML file. This can be a URL or the path of a local file.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--service-address-url`: The address of the Gate server that will be accesible by the SAML identity provider. This should be the full URL, including port, e.g. [https://gate.org.com:8084/](https://gate.org.com:8084/). If deployed behind a load balancer, this would be the laod balancer's address.
- * `--user-attribute-mapping-email`: The email field returned from your SAML provider.
- * `--user-attribute-mapping-first-name`: The first name field returned from your SAML provider.
- * `--user-attribute-mapping-last-name`: The last name field returned from your SAML provider.
- * `--user-attribute-mapping-roles`: The roles field returned from your SAML provider.
- * `--user-attribute-mapping-roles-delimiter`: The roles delimiter field returned from your SAML provider.
- * `--user-attribute-mapping-username`: The username field returned from your SAML provider.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--issuer-id`: The identity of the Spinnaker application registered with the SAML provider.
+- `--keystore`: Path to the keystore that contains this server's private key. This key is used to cryptographically sign SAML AuthNRequest objects.
+- `--keystore-alias`: The name of the alias under which this server's private key is stored in the --keystore file.
+- `--keystore-password`: The password used to access the file specified in --keystore
+- `--metadata`: The address to your identity provider's metadata XML file. This can be a URL or the path of a local file.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--service-address-url`: The address of the Gate server that will be accesible by the SAML identity provider. This should be the full URL, including port, e.g. [https://gate.org.com:8084/](https://gate.org.com:8084/). If deployed behind a load balancer, this would be the laod balancer's address.
+- `--user-attribute-mapping-email`: The email field returned from your SAML provider.
+- `--user-attribute-mapping-first-name`: The first name field returned from your SAML provider.
+- `--user-attribute-mapping-last-name`: The last name field returned from your SAML provider.
+- `--user-attribute-mapping-roles`: The roles field returned from your SAML provider.
+- `--user-attribute-mapping-roles-delimiter`: The roles delimiter field returned from your SAML provider.
+- `--user-attribute-mapping-username`: The username field returned from your SAML provider.
---
+
## hal config security authn saml enable
Set the saml method as enabled
#### Usage
+
```
hal config security authn saml enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config security authn x509
Configure the x509 method for authenticating.
#### Usage
+
```
hal config security authn x509 [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `disable`: Set the x509 method as disabled
- * `edit`: Configure authentication and role information for a x509 authentication scheme
- * `enable`: Set the x509 method as enabled
+
+- `disable`: Set the x509 method as disabled
+- `edit`: Configure authentication and role information for a x509 authentication scheme
+- `enable`: Set the x509 method as enabled
---
+
## hal config security authn x509 disable
Set the x509 method as disabled
#### Usage
+
```
hal config security authn x509 disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config security authn x509 edit
x509 authenticates users via client certificate and a corresponding private key These certificates optionally provide authorization information via custom Oids with corresponding group information for the user. This can be configured via --roleOid
#### Usage
+
```
hal config security authn x509 edit [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--role-oid`: The OID that encodes roles that the user specified in the x509 certificate belongs to
- * `--subject-principal-regex`: The regex used to parse the subject principal name embedded in the x509 certificate if necessary
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--role-oid`: The OID that encodes roles that the user specified in the x509 certificate belongs to
+- `--subject-principal-regex`: The regex used to parse the subject principal name embedded in the x509 certificate if necessary
---
+
## hal config security authn x509 enable
Set the x509 method as enabled
#### Usage
+
```
hal config security authn x509 enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config security authz
This set of commands allows you to configure what resources users of Spinnaker can read and modify.
#### Usage
+
```
hal config security authz [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `disable`: Set Spinnaker's role-based authorization to disabled
- * `edit`: Edit your roles provider settings.
- * `enable`: Set Spinnaker's role-based authorization to enabled
- * `file`: Configure the file role provider.
- * `github`: Configure the github role provider.
- * `google`: Configure the google role provider.
- * `ldap`: Configure the ldap role provider.
+
+- `disable`: Set Spinnaker's role-based authorization to disabled
+- `edit`: Edit your roles provider settings.
+- `enable`: Set Spinnaker's role-based authorization to enabled
+- `file`: Configure the file role provider.
+- `github`: Configure the github role provider.
+- `google`: Configure the google role provider.
+- `ldap`: Configure the ldap role provider.
---
+
## hal config security authz disable
Set Spinnaker's role-based authorization to disabled
#### Usage
+
```
hal config security authz disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config security authz edit
Edit your roles provider settings.
#### Usage
+
```
hal config security authz edit [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--type`: Set a roles provider type
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--type`: Set a roles provider type
---
+
## hal config security authz enable
Set Spinnaker's role-based authorization to enabled
#### Usage
+
```
hal config security authz enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config security authz file
Configure the file role provider.
#### Usage
+
```
hal config security authz file [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `edit`: Edit the file role provider.
+
+- `edit`: Edit the file role provider.
---
+
## hal config security authz file edit
Edit the file role provider.
#### Usage
+
```
hal config security authz file edit [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--file-path`: A path to a file describing the roles of each user.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--file-path`: A path to a file describing the roles of each user.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config security authz github
Configure the github role provider.
#### Usage
+
```
hal config security authz github [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `edit`: Edit the github role provider.
+
+- `edit`: Edit the github role provider.
---
+
## hal config security authz github edit
Edit the github role provider.
#### Usage
+
```
hal config security authz github edit [parameters]
```
#### Parameters
- * `--accessToken`: A personal access token of an account with access to your organization's GitHub Teams structure.
- * `--baseUrl`: Used if using GitHub enterprise some other non github.com GitHub installation.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--organization`: The GitHub organization under which to query for GitHub Teams.
+- `--accessToken`: A personal access token of an account with access to your organization's GitHub Teams structure.
+- `--baseUrl`: Used if using GitHub enterprise some other non github.com GitHub installation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--organization`: The GitHub organization under which to query for GitHub Teams.
---
+
## hal config security authz google
Configure the google role provider.
#### Usage
+
```
hal config security authz google [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `edit`: Edit the google role provider.
+
+- `edit`: Edit the google role provider.
---
+
## hal config security authz google edit
Edit the google role provider.
#### Usage
+
```
hal config security authz google edit [parameters]
```
#### Parameters
- * `--admin-username`: Your role provider's admin username e.g. admin@myorg.net
- * `--credential-path`: A path to a valid json service account that can authenticate against the Google role provider.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--domain`: The domain your role provider is configured for e.g. myorg.net.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--admin-username`: Your role provider's admin username e.g. admin@myorg.net
+- `--credential-path`: A path to a valid json service account that can authenticate against the Google role provider.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--domain`: The domain your role provider is configured for e.g. myorg.net.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config security authz ldap
Configure the ldap role provider.
#### Usage
+
```
hal config security authz ldap [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `edit`: Edit the ldap role provider.
+
+- `edit`: Edit the ldap role provider.
---
+
## hal config security authz ldap edit
Edit the ldap role provider.
#### Usage
+
```
hal config security authz ldap edit [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--group-role-attributes`: The attribute which contains the name of the authority defined by the group entry. Defaults to 'cn'.
- * `--group-search-base`: The part of the directory tree under which group searches should be performed.
- * `--group-search-filter`: The filter which is used to search for group membership. The default is 'uniqueMember={0}', corresponding to the groupOfUniqueMembers LDAP class. In this case, the substituted parameter is the full distinguished name of the user. The parameter '{1}' can be used if you want to filter on the login name.
- * `--manager-dn`: The manager user's distinguished name (principal) to use for querying ldap groups.
- * `--manager-password`: (*Sensitive data* - user will be prompted on standard input) The manager user's password to use for querying ldap groups.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--url`: ldap:// or ldaps:// url of the LDAP server
- * `--user-dn-pattern`: The pattern for finding a user's DN using simple pattern matching. For example, if your LDAP server has the URL [ldap://mysite.com/dc=spinnaker,dc=org](ldap://mysite.com/dc=spinnaker,dc=org), and you have the pattern 'uid={0},ou=members', 'me' will map to a DN uid=me,ou=members,dc=spinnaker,dc=org. If no match is found, will try to find the user using --user-search-filter, if set.
- * `--user-search-base`: The part of the directory tree under which user searches should be performed. If --user-search-base isn't supplied, the search will be performed from the root.
- * `--user-search-filter`: The filter to use when searching for a user's DN. Will search either from --user-search-base (if specified) or root for entires matching the filter.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--group-role-attributes`: The attribute which contains the name of the authority defined by the group entry. Defaults to 'cn'.
+- `--group-search-base`: The part of the directory tree under which group searches should be performed.
+- `--group-search-filter`: The filter which is used to search for group membership. The default is 'uniqueMember={0}', corresponding to the groupOfUniqueMembers LDAP class. In this case, the substituted parameter is the full distinguished name of the user. The parameter '{1}' can be used if you want to filter on the login name.
+- `--manager-dn`: The manager user's distinguished name (principal) to use for querying ldap groups.
+- `--manager-password`: (_Sensitive data_ - user will be prompted on standard input) The manager user's password to use for querying ldap groups.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--url`: ldap:// or ldaps:// url of the LDAP server
+- `--user-dn-pattern`: The pattern for finding a user's DN using simple pattern matching. For example, if your LDAP server has the URL [ldap://mysite.com/dc=spinnaker,dc=org](ldap://mysite.com/dc=spinnaker,dc=org), and you have the pattern 'uid={0},ou=members', 'me' will map to a DN uid=me,ou=members,dc=spinnaker,dc=org. If no match is found, will try to find the user using --user-search-filter, if set.
+- `--user-search-base`: The part of the directory tree under which user searches should be performed. If --user-search-base isn't supplied, the search will be performed from the root.
+- `--user-search-filter`: The filter to use when searching for a user's DN. Will search either from --user-search-base (if specified) or root for entires matching the filter.
---
+
## hal config security ui
Configure and view the UI server's addressable URL.
#### Usage
+
```
hal config security ui [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `edit`: Configure access policies specific to Spinnaker's UI server.
- * `ssl`: Configure and view SSL settings for Spinnaker's UI gateway.
+
+- `edit`: Configure access policies specific to Spinnaker's UI server.
+- `ssl`: Configure and view SSL settings for Spinnaker's UI gateway.
---
+
## hal config security ui edit
When Spinnaker is deployed to a remote host, the UI server may be configured to do SSL termination, or sit behind an externally configured proxy server or load balancer.
#### Usage
+
```
hal config security ui edit [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--override-base-url`: If you are accessing the UI server remotely, provide the full base URL of whatever proxy or load balancer is fronting the UI requests.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--override-base-url`: If you are accessing the UI server remotely, provide the full base URL of whatever proxy or load balancer is fronting the UI requests.
---
+
## hal config security ui ssl
If you want the UI server to do SSL termination, it must be enabled and configured here. If you are doing your own SSL termination, leave this disabled.
#### Usage
+
```
hal config security ui ssl [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `disable`: Disable SSL for the UI gateway.
- * `edit`: Edit SSL settings for your UI server.
- * `enable`: Enable SSL for the UI gateway.
+
+- `disable`: Disable SSL for the UI gateway.
+- `edit`: Edit SSL settings for your UI server.
+- `enable`: Enable SSL for the UI gateway.
---
+
## hal config security ui ssl disable
Disable SSL for the UI gateway.
#### Usage
+
```
hal config security ui ssl disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config security ui ssl edit
Configure SSL termination to handled by the UI server's Apache server.
#### Usage
+
```
hal config security ui ssl edit [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--ssl-certificate-ca-file`: Path to the .crt file for the CA that issued your SSL certificate. This is only needed for localgitdeployments that serve the UI using webpack dev server.
- * `--ssl-certificate-file`: Path to your .crt file.
- * `--ssl-certificate-key-file`: Path to your .key file.
- * `--ssl-certificate-passphrase`: (*Sensitive data* - user will be prompted on standard input) The passphrase needed to unlock your SSL certificate. This will be provided to Apache on startup.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--ssl-certificate-ca-file`: Path to the .crt file for the CA that issued your SSL certificate. This is only needed for localgitdeployments that serve the UI using webpack dev server.
+- `--ssl-certificate-file`: Path to your .crt file.
+- `--ssl-certificate-key-file`: Path to your .key file.
+- `--ssl-certificate-passphrase`: (_Sensitive data_ - user will be prompted on standard input) The passphrase needed to unlock your SSL certificate. This will be provided to Apache on startup.
---
+
## hal config security ui ssl enable
Enable SSL for the UI gateway.
#### Usage
+
```
hal config security ui ssl enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config stats
Show Spinnaker's stats settings.
#### Usage
+
```
hal config stats [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `disable`: Set Spinnaker's stats settings to disabled.
- * `edit`: Edit Spinnaker's stats settings.
- * `enable`: Set Spinnaker's stats settings to enabled.
+
+- `disable`: Set Spinnaker's stats settings to disabled.
+- `edit`: Edit Spinnaker's stats settings.
+- `enable`: Set Spinnaker's stats settings to enabled.
---
+
## hal config stats disable
Set Spinnaker's stats settings to disabled.
#### Usage
+
```
hal config stats disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config stats edit
Edit Spinnaker's stats settings.
#### Usage
+
```
hal config stats edit [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--endpoint`: Set the endpoint for stats metrics.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--endpoint`: Set the endpoint for stats metrics.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config stats enable
Set Spinnaker's stats settings to enabled.
#### Usage
+
```
hal config stats enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config storage
Show Spinnaker's persistent storage configuration.
#### Usage
+
```
hal config storage [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `azs`: Manage and view Spinnaker configuration for the "azs" persistent store.
- * `edit`: Edit Spinnaker's persistent storage.
- * `gcs`: Manage and view Spinnaker configuration for the "gcs" persistent store.
- * `oracle`: Manage and view Spinnaker configuration for the "oracle" persistent store.
- * `s3`: Manage and view Spinnaker configuration for the "s3" persistent store.
+
+- `azs`: Manage and view Spinnaker configuration for the "azs" persistent store.
+- `edit`: Edit Spinnaker's persistent storage.
+- `gcs`: Manage and view Spinnaker configuration for the "gcs" persistent store.
+- `oracle`: Manage and view Spinnaker configuration for the "oracle" persistent store.
+- `s3`: Manage and view Spinnaker configuration for the "s3" persistent store.
---
+
## hal config storage azs
Manage and view Spinnaker configuration for the "azs" persistent store.
#### Usage
+
```
hal config storage azs [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `edit`: Edit configuration for the "azs" persistent store.
+
+- `edit`: Edit configuration for the "azs" persistent store.
---
+
## hal config storage azs edit
Edit configuration for the "azs" persistent store.
#### Usage
+
```
hal config storage azs edit [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--storage-account-key`: The key to access the Azure Storage Account used for Spinnaker's persistent data.
- * `--storage-account-name`: The name of an Azure Storage Account used for Spinnaker's persistent data.
- * `--storage-container-name`: (*Default*: `spinnaker`) The container name in the chosen storage account to place all of Spinnaker's persistent data.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--storage-account-key`: The key to access the Azure Storage Account used for Spinnaker's persistent data.
+- `--storage-account-name`: The name of an Azure Storage Account used for Spinnaker's persistent data.
+- `--storage-container-name`: (_Default_: `spinnaker`) The container name in the chosen storage account to place all of Spinnaker's persistent data.
---
+
## hal config storage edit
Edit Spinnaker's persistent storage.
#### Usage
+
```
hal config storage edit [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--type`: (*Required*) The type of the persistent store to use for Spinnaker.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--type`: (_Required_) The type of the persistent store to use for Spinnaker.
---
+
## hal config storage gcs
Manage and view Spinnaker configuration for the "gcs" persistent store.
#### Usage
+
```
hal config storage gcs [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `edit`: Edit configuration for the "gcs" persistent store.
+
+- `edit`: Edit configuration for the "gcs" persistent store.
---
+
## hal config storage gcs edit
Edit configuration for the "gcs" persistent store.
#### Usage
+
```
hal config storage gcs edit [parameters]
```
#### Parameters
- * `--bucket`: The name of a storage bucket that your specified account has access to. If not specified, a random name will be chosen. If you specify a globally unique bucket name that doesn't exist yet, Halyard will create that bucket for you.
- * `--bucket-location`: This is only required if the bucket you specify doesn't exist yet. In that case, the bucket will be created in that location. See [https://cloud.google.com/storage/docs/managing-buckets#manage-class-location](https://cloud.google.com/storage/docs/managing-buckets#manage-class-location).
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--json-path`: A path to a JSON service account with permission to read and write to the bucket to be used as a backing store.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--project`: The Google Cloud Platform project you are using to host the GCS bucket as a backing store.
- * `--root-folder`: The root folder in the chosen bucket to place all of Spinnaker's persistent data in.
+- `--bucket`: The name of a storage bucket that your specified account has access to. If not specified, a random name will be chosen. If you specify a globally unique bucket name that doesn't exist yet, Halyard will create that bucket for you.
+- `--bucket-location`: This is only required if the bucket you specify doesn't exist yet. In that case, the bucket will be created in that location. See [https://cloud.google.com/storage/docs/managing-buckets#manage-class-location](https://cloud.google.com/storage/docs/managing-buckets#manage-class-location).
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--json-path`: A path to a JSON service account with permission to read and write to the bucket to be used as a backing store.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--project`: The Google Cloud Platform project you are using to host the GCS bucket as a backing store.
+- `--root-folder`: The root folder in the chosen bucket to place all of Spinnaker's persistent data in.
---
+
## hal config storage oracle
Manage and view Spinnaker configuration for the "oracle" persistent store.
#### Usage
+
```
hal config storage oracle [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `edit`: Edit configuration for the "oracle" persistent store.
+
+- `edit`: Edit configuration for the "oracle" persistent store.
---
+
## hal config storage oracle edit
Edit configuration for the "oracle" persistent store.
#### Usage
+
```
hal config storage oracle edit [parameters]
```
#### Parameters
- * `--bucket-name`: The bucket name to store persistent state object in
- * `--compartment-id`: Provide the OCID of the Oracle Compartment to use.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--fingerprint`: Fingerprint of the public key
- * `--namespace`: The namespace the bucket and objects should be created in
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--private-key-passphrase`: (*Sensitive data* - user will be prompted on standard input) Passphrase used for the private key, if it is encrypted
- * `--region`: An Oracle region (e.g., us-phoenix-1)
- * `--ssh-private-key-file-path`: Path to the private key in PEM format
- * `--tenancy-id`: Provide the OCID of the Oracle Tenancy to use.
- * `--user-id`: Provide the OCID of the Oracle User you're authenticating as
+- `--bucket-name`: The bucket name to store persistent state object in
+- `--compartment-id`: Provide the OCID of the Oracle Compartment to use.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--fingerprint`: Fingerprint of the public key
+- `--namespace`: The namespace the bucket and objects should be created in
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--private-key-passphrase`: (_Sensitive data_ - user will be prompted on standard input) Passphrase used for the private key, if it is encrypted
+- `--region`: An Oracle region (e.g., us-phoenix-1)
+- `--ssh-private-key-file-path`: Path to the private key in PEM format
+- `--tenancy-id`: Provide the OCID of the Oracle Tenancy to use.
+- `--user-id`: Provide the OCID of the Oracle User you're authenticating as
---
+
## hal config storage s3
Manage and view Spinnaker configuration for the "s3" persistent store.
#### Usage
+
```
hal config storage s3 [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `edit`: Edit configuration for the "s3" persistent store.
+
+- `edit`: Edit configuration for the "s3" persistent store.
---
+
## hal config storage s3 edit
Edit configuration for the "s3" persistent store.
#### Usage
+
```
hal config storage s3 edit [parameters]
```
#### Parameters
- * `--access-key-id`: Your AWS Access Key ID. If not provided, Halyard/Spinnaker will try to find AWS credentials as described at [http://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/credentials.html#credentials-default](http://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/credentials.html#credentials-default)
- * `--assume-role`: If set, Halyard will configure a credentials provider that uses AWS Security Token Service to assume the specified role.
+
+- `--access-key-id`: Your AWS Access Key ID. If not provided, Halyard/Spinnaker will try to find AWS credentials as described at [http://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/credentials.html#credentials-default](http://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/credentials.html#credentials-default)
+- `--assume-role`: If set, Halyard will configure a credentials provider that uses AWS Security Token Service to assume the specified role.
Example: "user/spinnaker" or "role/spinnakerManaged"
- * `--bucket`: The name of a storage bucket that your specified account has access to. If not specified, a random name will be chosen. If you specify a globally unique bucket name that doesn't exist yet, Halyard will create that bucket for you.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--endpoint`: An alternate endpoint that your S3-compatible storage can be found at. This is intended for self-hosted storage services with S3-compatible APIs, e.g. Minio. If supplied, this storage type cannot be validated.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--path-style-access`: (*Default*: `false`) when true, use path-style to access bucket; when false, use virtual hosted-style to access bucket. See [https://docs.aws.amazon.com/AmazonS3/latest/dev/VirtualHosting.html#VirtualHostingExamples](https://docs.aws.amazon.com/AmazonS3/latest/dev/VirtualHosting.html#VirtualHostingExamples).
- * `--region`: This is only required if the bucket you specify doesn't exist yet. In that case, the bucket will be created in that region. See [http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region](http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region).
- * `--root-folder`: The root folder in the chosen bucket to place all of Spinnaker's persistent data in.
- * `--secret-access-key`: (*Sensitive data* - user will be prompted on standard input) Your AWS Secret Key.
- * `--server-side-encryption`: Use Amazon Server-Side Encryption ('x-amz-server-side-encryption' header). Supports 'AES256' (for Amazon S3-managed encryption keys, equivalent to a header value of 'AES256') and 'AWSKMS' (for AWS KMS-managed encryption keys, equivalent to a header value of 'aws:kms'.
+- `--bucket`: The name of a storage bucket that your specified account has access to. If not specified, a random name will be chosen. If you specify a globally unique bucket name that doesn't exist yet, Halyard will create that bucket for you.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--endpoint`: An alternate endpoint that your S3-compatible storage can be found at. This is intended for self-hosted storage services with S3-compatible APIs, e.g. Minio. If supplied, this storage type cannot be validated.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--path-style-access`: (_Default_: `false`) when true, use path-style to access bucket; when false, use virtual hosted-style to access bucket. See [https://docs.aws.amazon.com/AmazonS3/latest/dev/VirtualHosting.html#VirtualHostingExamples](https://docs.aws.amazon.com/AmazonS3/latest/dev/VirtualHosting.html#VirtualHostingExamples).
+- `--region`: This is only required if the bucket you specify doesn't exist yet. In that case, the bucket will be created in that region. See [http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region](http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region).
+- `--root-folder`: The root folder in the chosen bucket to place all of Spinnaker's persistent data in.
+- `--secret-access-key`: (_Sensitive data_ - user will be prompted on standard input) Your AWS Secret Key.
+- `--server-side-encryption`: Use Amazon Server-Side Encryption ('x-amz-server-side-encryption' header). Supports 'AES256' (for Amazon S3-managed encryption keys, equivalent to a header value of 'AES256') and 'AWSKMS' (for AWS KMS-managed encryption keys, equivalent to a header value of 'aws:kms'.
---
+
## hal config version
Configure & view the current deployment of Spinnaker's version.
#### Usage
+
```
hal config version [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `edit`: Set the desired Spinnaker version.
+
+- `edit`: Set the desired Spinnaker version.
---
+
## hal config version edit
Set the desired Spinnaker version.
#### Usage
+
```
hal config version edit [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--version`: (*Required*) Must be either a version number "X.Y.Z" for a specific release of Spinnaker, or "$BRANCH-latest-unvalidated" for the most recently built (unvalidated) Spinnaker on $BRANCH.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--version`: (_Required_) Must be either a version number "X.Y.Z" for a specific release of Spinnaker, or "$BRANCH-latest-unvalidated" for the most recently built (unvalidated) Spinnaker on $BRANCH.
---
+
## hal config webhook
Show Spinnaker's webhook configuration.
#### Usage
+
```
hal config webhook [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `trust`: Show Spinnaker's webhook trust configuration.
+
+- `trust`: Show Spinnaker's webhook trust configuration.
---
+
## hal config webhook trust
Show Spinnaker's webhook trust configuration.
#### Usage
+
```
hal config webhook trust [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `disable`: Set Spinnaker's webhook trust to disabled.
- * `edit`: Edit Spinnaker's webhook trust configuration.
- * `enable`: Set Spinnaker's webhook trust to enabled.
+
+- `disable`: Set Spinnaker's webhook trust to disabled.
+- `edit`: Edit Spinnaker's webhook trust configuration.
+- `enable`: Set Spinnaker's webhook trust to enabled.
---
+
## hal config webhook trust disable
Set Spinnaker's webhook trust to disabled.
#### Usage
+
```
hal config webhook trust disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal config webhook trust edit
Edit Spinnaker's webhook trust configuration.
#### Usage
+
```
hal config webhook trust edit [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--trustStore`: The path to a key store in JKS format containing certification authorities that should be trusted by webhook stages.
- * `--trustStorePassword`: (*Sensitive data* - user will be prompted on standard input) The password for the supplied trustStore.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--trustStore`: The path to a key store in JKS format containing certification authorities that should be trusted by webhook stages.
+- `--trustStorePassword`: (_Sensitive data_ - user will be prompted on standard input) The password for the supplied trustStore.
---
+
## hal config webhook trust enable
Set Spinnaker's webhook trust to enabled.
#### Usage
+
```
hal config webhook trust enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal deploy
Manage the deployment of Spinnaker. This includes where it's deployed, what the infrastructure footprint looks like, what the currently running deployment looks like, etc...
#### Usage
+
```
hal deploy [subcommands]
```
#### Subcommands
- * `apply`: Deploy or update the currently configured instance of Spinnaker to a selected environment.
- * `clean`: Remove all Spinnaker artifacts in your target deployment environment.
- * `collect-logs`: Collect logs from the specified Spinnaker services.
- * `connect`: Connect to your Spinnaker deployment.
- * `details`: Get details about your currently deployed Spinnaker installation.
- * `diff`: This shows what changes you have made since Spinnaker was last deployed.
- * `rollback`: Rollback Spinnaker to the prior version on a selected environment.
+
+- `apply`: Deploy or update the currently configured instance of Spinnaker to a selected environment.
+- `clean`: Remove all Spinnaker artifacts in your target deployment environment.
+- `collect-logs`: Collect logs from the specified Spinnaker services.
+- `connect`: Connect to your Spinnaker deployment.
+- `details`: Get details about your currently deployed Spinnaker installation.
+- `diff`: This shows what changes you have made since Spinnaker was last deployed.
+- `rollback`: Rollback Spinnaker to the prior version on a selected environment.
---
+
## hal deploy apply
This command deploys Spinnaker, depending on how you've configured your deployment. Local deployments are applied to the machine running Halyard, whereas Distributed deployments are applied to a cloud provider. Local deployments are subject to downtime during updates, whereas Distributed deployments are deployed and updated via a headless 'bootstrap' deployment of Spinnaker, and don't suffer downtime.
#### Usage
+
```
hal deploy apply [parameters]
```
#### Parameters
- * `--auto-run`: This command will generate a script to be run on your behalf. By default, the script will run without intervention - if you want to override this, provide "true" or "false" to this flag.
- * `--delete-orphaned-services`: (*Default*: `false`) Deletes unused Spinnaker services after the deploy succeeds. This flag is not allowed when using the --service-names or --exclude-service-names arg.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--exclude-service-names`: (*Default*: `[]`) When supplied, do not install or update the specified Spinnaker services.
- * `--flush-infrastructure-caches`: (*Default*: `false`) WARNING: This is considered an advanced command, and may break your deployment if used incorrectly.
+
+- `--auto-run`: This command will generate a script to be run on your behalf. By default, the script will run without intervention - if you want to override this, provide "true" or "false" to this flag.
+- `--delete-orphaned-services`: (_Default_: `false`) Deletes unused Spinnaker services after the deploy succeeds. This flag is not allowed when using the --service-names or --exclude-service-names arg.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--exclude-service-names`: (_Default_: `[]`) When supplied, do not install or update the specified Spinnaker services.
+- `--flush-infrastructure-caches`: (_Default_: `false`) WARNING: This is considered an advanced command, and may break your deployment if used incorrectly.
This flushes infrastructure caches (clouddriver) after the deploy succeeds.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--omit-config`: (*Default*: `false`) WARNING: This is considered an advanced command, and may break your deployment if used incorrectly.
+
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--omit-config`: (_Default_: `false`) WARNING: This is considered an advanced command, and may break your deployment if used incorrectly.
This guarantees that no configuration will be generated for this deployment. This is useful for staging artifacts for later manual configuration.
- * `--prep-only`: (*Default*: `false`) This does just the prep work, and not the actual deployment. Only useful at the moment if you want to just clone the repositories for a localgit setup.
- * `--service-names`: (*Default*: `[]`) When supplied, only install or update the specified Spinnaker services.
- * `--wait-for-completion`: (*Default*: `false`) When supplied, wait for all containers to be ready before returning (only applies to Kubernetes V2 provider).
- * `--wait-for-completion-timeout-minutes`: Specify timeout for deploy apply command.
+- `--prep-only`: (_Default_: `false`) This does just the prep work, and not the actual deployment. Only useful at the moment if you want to just clone the repositories for a localgit setup.
+- `--service-names`: (_Default_: `[]`) When supplied, only install or update the specified Spinnaker services.
+- `--wait-for-completion`: (_Default_: `false`) When supplied, wait for all containers to be ready before returning (only applies to Kubernetes V2 provider).
+- `--wait-for-completion-timeout-minutes`: Specify timeout for deploy apply command.
---
+
## hal deploy clean
This command destroys all Spinnaker artifacts in your target deployment environment. This cannot be undone, so use with care. This does not delete Halyard nor any of the configuration.
#### Usage
+
```
hal deploy clean [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal deploy collect-logs
This command collects logs from all Spinnaker services, and depending on how it was deployed, it will collect logs from sidecars and startup scripts as well.
#### Usage
+
```
hal deploy collect-logs [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--exclude-service-names`: (*Default*: `[]`) When supplied, logs from the specified services will be not collected
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--service-names`: (*Default*: `[]`) When supplied, logs from only the specified services will be collected.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--exclude-service-names`: (_Default_: `[]`) When supplied, logs from the specified services will be not collected
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--service-names`: (_Default_: `[]`) When supplied, logs from only the specified services will be collected.
---
+
## hal deploy connect
This command connects to your Spinnaker deployment, assuming it was already deployed. In the case of the `Local*` deployment type, this is a NoOp.
#### Usage
+
```
hal deploy connect [parameters]
```
#### Parameters
- * `--auto-run`: This command will generate a script to be run on your behalf. By default, the script will run without intervention - if you want to override this, provide "true" or "false" to this flag.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--service-names`: (*Default*: `[]`) When supplied, connections to the specified Spinnaker services are opened. When omitted, connections to the UI & API servers are opened to allow you to interact with Spinnaker in your browser.
+- `--auto-run`: This command will generate a script to be run on your behalf. By default, the script will run without intervention - if you want to override this, provide "true" or "false" to this flag.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--service-names`: (_Default_: `[]`) When supplied, connections to the specified Spinnaker services are opened. When omitted, connections to the UI & API servers are opened to allow you to interact with Spinnaker in your browser.
---
+
## hal deploy details
Get details about your currently deployed Spinnaker installation.
#### Usage
+
```
hal deploy details [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--service-name`: (*Required*) The name of the service to inspect.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--service-name`: (_Required_) The name of the service to inspect.
---
+
## hal deploy diff
This shows what changes you have made since Spinnaker was last deployed.
#### Usage
+
```
hal deploy diff [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal deploy rollback
This command attempts to rollback Spinnaker to the prior deployed version, depending on how you've configured your deployment. Local deployments have their prior packages installed and reconfigured, whereas Distributed deployments are rolled back via a headless 'bootstrap' deployment of Spinnaker, and don't suffer downtime.
#### Usage
+
```
hal deploy rollback [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--exclude-service-names`: (*Default*: `[]`) When supplied, do not install or update the specified Spinnaker services.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--service-names`: (*Default*: `[]`) When supplied, only install or update the specified Spinnaker services.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--exclude-service-names`: (_Default_: `[]`) When supplied, do not install or update the specified Spinnaker services.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--service-names`: (_Default_: `[]`) When supplied, only install or update the specified Spinnaker services.
---
+
## hal plugins
Show Spinnaker's configured plugins.
#### Usage
+
```
hal plugins [parameters] [subcommands]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
#### Subcommands
- * `add`: Add a plugin
- * `delete`: Delete a plugin
- * `disable`: Enable or disable all plugins
- * `disable-downloading`: Enable or disable the ability for Spinnaker services to download jars for plugins
- * `edit`: Edit a plugin
- * `enable`: Enable or disable all plugins
- * `enable-downloading`: Enable or disable the ability for Spinnaker services to download jars for plugins
- * `list`: List all plugins
- * `repository`: Configure, validate, and view the specified plugin repository.
+
+- `add`: Add a plugin
+- `delete`: Delete a plugin
+- `disable`: Enable or disable all plugins
+- `disable-downloading`: Enable or disable the ability for Spinnaker services to download jars for plugins
+- `edit`: Edit a plugin
+- `enable`: Enable or disable all plugins
+- `enable-downloading`: Enable or disable the ability for Spinnaker services to download jars for plugins
+- `list`: List all plugins
+- `repository`: Configure, validate, and view the specified plugin repository.
---
+
## hal plugins add
Add a plugin
#### Usage
+
```
hal plugins add PLUGIN [parameters]
```
#### Parameters
+
`PLUGIN`: The name of the plugin to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--enabled`: To enable or disable the plugin.
- * `--extensions`: A comma separated list of extensions to enable
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--ui-resource-location`: The location of the plugin's ui resource.
- * `--version`: The plugin version to use
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--enabled`: To enable or disable the plugin.
+- `--extensions`: A comma separated list of extensions to enable
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--ui-resource-location`: The location of the plugin's ui resource.
+- `--version`: The plugin version to use
---
+
## hal plugins delete
Delete a plugin
#### Usage
+
```
hal plugins delete PLUGIN [parameters]
```
#### Parameters
+
`PLUGIN`: The name of the plugin to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal plugins disable
Enable or disable all plugins
#### Usage
+
```
hal plugins disable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal plugins disable-downloading
Enable or disable the ability for Spinnaker services to download jars for plugins
#### Usage
+
```
hal plugins disable-downloading [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal plugins edit
Edit a plugin
#### Usage
+
```
hal plugins edit PLUGIN [parameters]
```
#### Parameters
+
`PLUGIN`: The name of the plugin to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--enabled`: To enable or disable the plugin.
- * `--extensions`: A comma separated list of extensions to create
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--ui-resource-location`: The location of the plugin's ui resource.
- * `--version`: The plugin version to use
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--enabled`: To enable or disable the plugin.
+- `--extensions`: A comma separated list of extensions to create
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--ui-resource-location`: The location of the plugin's ui resource.
+- `--version`: The plugin version to use
---
+
## hal plugins enable
Enable or disable all plugins
#### Usage
+
```
hal plugins enable [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal plugins enable-downloading
Enable or disable the ability for Spinnaker services to download jars for plugins
#### Usage
+
```
hal plugins enable-downloading [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal plugins list
List all plugins
#### Usage
+
```
hal plugins list [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal plugins repository
Configure, validate, and view the specified plugin repository.
#### Usage
+
```
hal plugins repository [subcommands]
```
#### Subcommands
- * `add`: Add a plugin repository
- * `delete`: Delete a plugin repository
- * `edit`: Edit a plugin repository
- * `list`: List all plugin repositories
+
+- `add`: Add a plugin repository
+- `delete`: Delete a plugin repository
+- `edit`: Edit a plugin repository
+- `list`: List all plugin repositories
---
+
## hal plugins repository add
Add a plugin repository
#### Usage
+
```
hal plugins repository add REPOSITORY [parameters]
```
#### Parameters
+
`REPOSITORY`: The name of the plugin repository to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--url`: (*Required*) The location of the plugin repository.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--url`: (_Required_) The location of the plugin repository.
---
+
## hal plugins repository delete
Delete a plugin repository
#### Usage
+
```
hal plugins repository delete REPOSITORY [parameters]
```
#### Parameters
+
`REPOSITORY`: The name of the plugin repository to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal plugins repository edit
Edit a plugin repository
#### Usage
+
```
hal plugins repository edit REPOSITORY [parameters]
```
#### Parameters
+
`REPOSITORY`: The name of the plugin repository to operate on.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
- * `--url`: The location of the plugin repository.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
+- `--url`: The location of the plugin repository.
---
+
## hal plugins repository list
List all plugin repositories
#### Usage
+
```
hal plugins repository list [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal shutdown
Shutdown the halyard daemon.
#### Usage
+
```
hal shutdown
```
-
---
+
## hal spin
Manage the lifecycle of spin CLI.
#### Usage
+
```
hal spin [subcommands]
```
#### Subcommands
- * `install`: Installs the spin CLI.
+
+- `install`: Installs the spin CLI.
---
+
## hal spin install
This command installs the spin CLI.
#### Usage
+
```
hal spin install [parameters]
```
#### Parameters
- * `--auto-run`: This command will generate a script to be run on your behalf. By default, the script will run without intervention - if you want to override this, provide "true" or "false" to this flag.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--auto-run`: This command will generate a script to be run on your behalf. By default, the script will run without intervention - if you want to override this, provide "true" or "false" to this flag.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal task
-Every unit of work Halyard carries out is bundled in a Task. This set of commands exposes some information about these tasks. The commands here are mainly for troubleshooting.
+Every unit of work Halyard carries out is bundled in a Task. This set of commands exposes some information about these tasks. The commands here are mainly for troubleshooting.
#### Usage
+
```
hal task [subcommands]
```
#### Subcommands
- * `interrupt`: Interrupt (attempt to kill) a given task.
- * `list`: List the currently running Tasks.
+
+- `interrupt`: Interrupt (attempt to kill) a given task.
+- `list`: List the currently running Tasks.
---
+
## hal task interrupt
Interrupt (attempt to kill) a given task.
#### Usage
+
```
hal task interrupt UUID
```
-
---
+
## hal task list
List the currently running Tasks.
#### Usage
+
```
hal task list
```
-
---
+
## hal version
Get information about the available Spinnaker versions.
#### Usage
+
```
hal version [subcommands]
```
#### Subcommands
- * `bom`: Get the Bill of Materials (BOM) for the specified version.
- * `latest`: Get the latest released, validated version number of Spinnaker.
- * `list`: List the available Spinnaker versions and their changelogs.
+
+- `bom`: Get the Bill of Materials (BOM) for the specified version.
+- `latest`: Get the latest released, validated version number of Spinnaker.
+- `list`: List the available Spinnaker versions and their changelogs.
---
+
## hal version bom
The Bill of Materials (BOM) is the manifest Halyard and Spinnaker use to agree on what subcomponent versions comprise a top-level release of Spinnaker. This command can be used with a main parameter (VERSION) to get the BOM for a given version of Spinnaker, or without a parameter to get the BOM for whatever version of Spinnaker you are currently configuring.
#### Usage
+
```
hal version bom VERSION [parameters]
```
#### Parameters
+
`VERSION`: The version whose Bill of Materials (BOM) to lookup.
- * `--artifact-name`: When supplied, print the version of this artifact only.
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--artifact-name`: When supplied, print the version of this artifact only.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
+
## hal version latest
Get the latest released, validated version number of Spinnaker.
#### Usage
+
```
hal version latest
```
-
---
+
## hal version list
All Spinnaker releases that have been fully validated are listed here. You can pick one of these releases to deploy using the `hal config version edit` command. There are unlisted, non-supported releases as well, but we advise against running them. For more information, contact the developers at [https://join.spinnaker.io](https://join.spinnaker.io).
#### Usage
+
```
hal version list [parameters]
```
#### Parameters
- * `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
- * `--no-validate`: (*Default*: `false`) Skip validation.
+- `--deployment`: If supplied, use this Halyard deployment. This will _not_ create a new deployment.
+- `--no-validate`: (_Default_: `false`) Skip validation.
---
diff --git a/content/en/docs/releases/_index.md b/content/en/docs/releases/_index.md
new file mode 100644
index 00000000..984414a2
--- /dev/null
+++ b/content/en/docs/releases/_index.md
@@ -0,0 +1,6 @@
+---
+title: 'Releases'
+linkTitle: 'Releases'
+weight:
+description:
+---
diff --git a/content/en/docs/releases/next-release-preview/index.md b/content/en/docs/releases/next-release-preview/index.md
new file mode 100644
index 00000000..13c1395a
--- /dev/null
+++ b/content/en/docs/releases/next-release-preview/index.md
@@ -0,0 +1,12 @@
+---
+title: 'Next Release Preview'
+linkTitle: 'Next Release Preview'
+weight: 2
+description:
+---
+
+Please make a pull request to describe any changes you wish to highlight
+in the next release of Spinnaker. These notes will be prepended to the release
+changelog.
+
+## Coming Soon in Release 1.27
diff --git a/content/en/community/stay-informed/releases/release-cadence/branches.png b/content/en/docs/releases/release-cadence/branches.png
similarity index 100%
rename from content/en/community/stay-informed/releases/release-cadence/branches.png
rename to content/en/docs/releases/release-cadence/branches.png
diff --git a/content/en/community/stay-informed/releases/release-cadence/index.md b/content/en/docs/releases/release-cadence/index.md
similarity index 100%
rename from content/en/community/stay-informed/releases/release-cadence/index.md
rename to content/en/docs/releases/release-cadence/index.md
diff --git a/content/en/community/stay-informed/releases/release-manager-runbook/index.md b/content/en/docs/releases/release-manager-runbook/index.md
similarity index 100%
rename from content/en/community/stay-informed/releases/release-manager-runbook/index.md
rename to content/en/docs/releases/release-manager-runbook/index.md
diff --git a/content/en/community/stay-informed/releases/roadmap.md b/content/en/docs/releases/roadmap.md
similarity index 100%
rename from content/en/community/stay-informed/releases/roadmap.md
rename to content/en/docs/releases/roadmap.md
diff --git a/content/en/community/stay-informed/releases/support-policy.md b/content/en/docs/releases/support-policy.md
similarity index 100%
rename from content/en/community/stay-informed/releases/support-policy.md
rename to content/en/docs/releases/support-policy.md
diff --git a/content/en/community/stay-informed/releases/versions.md b/content/en/docs/releases/versions.md
similarity index 58%
rename from content/en/community/stay-informed/releases/versions.md
rename to content/en/docs/releases/versions.md
index 9f5c8056..10ba3976 100644
--- a/content/en/community/stay-informed/releases/versions.md
+++ b/content/en/docs/releases/versions.md
@@ -1,8 +1,9 @@
---
-layout: single
-title: "Versions"
-sidebar:
- nav: community
+title: 'Versions'
+linkTitle: 'Versions'
+menu:
+ main:
+ weight: 20
---
The Spinnaker releases listed below are top-level versions tying together each
@@ -23,34 +24,20 @@ subcomponent.
## Latest stable
+{{% pageinfo color="primary" %}}
**Note**: In upcoming versions, Spinnaker will be migrating to Java 11 from Java 8. This should not affect Spinnaker users. If you extend Spinnaker, this may affect you. For more information about the current status of the migration, see the [Java 11 RFC](https://github.com/spinnaker/governance/blob/master/rfc/java11.md).
-{: .notice--info}
+{{% /pageinfo %}}
+{{% pageinfo color="primary" %}}
**Note**: Spinnaker versions 1.18.0 and later require Halyard version 1.29.0 or later.
-{: .notice--info}
-
-{% assign reversed = site.changelogs | sort: 'date' | reverse %}
-{% for post in reversed %}
- {% unless post.tags contains 'deprecated' %}
-{% if post.version == blank %}
-#### {{ post.changelog_title }}
-{% else %}
-#### Version {{ post.version }}
-{% endif %}
-Released: {{ post.date | date: '%Y-%m-%d %H:%M %Z' }}
-Changelog
- {% endunless %}
-{% endfor %}
+{{% /pageinfo %}}
+
+{{< latest-stable >}}
> To be notified when new Spinnaker versioned releases are available, please join the
-[spinnaker-announce](https://groups.google.com/forum/#!forum/spinnaker-announce) Google
-Group (requires a Google account).
+> [spinnaker-announce](https://groups.google.com/forum/#!forum/spinnaker-announce) Google
+> Group (requires a Google account).
## Deprecated Versions
-{% for post in reversed %}
- {% if post.tags contains 'deprecated' %}
-#### {{ post.changelog_title }}
-Released: {{ post.date | date: '%Y-%m-%d %H:%M %Z' }}
-Changelog
- {% endif %}
-{% endfor %}
+
+{{< deprecated-versions >}}
diff --git a/content/en/getting-started/_index.html b/content/en/getting-started/_index.html
deleted file mode 100644
index 3cc15312..00000000
--- a/content/en/getting-started/_index.html
+++ /dev/null
@@ -1,37 +0,0 @@
----
-title: Getting Started
-linkTitle: Getting Started
-menu:
- main:
- weight: 1
----
-
-
-{{< blocks/cover title="About Goldydocs" image_anchor="bottom" height="min" >}}
-
-
A sample site using the Docsy Hugo theme.
-
-
-{{< /blocks/cover >}}
-
-{{% blocks/lead %}}
-Goldydocs is a sample site using the Docsy Hugo theme that shows what it can do and provides you with a template site structure. It’s designed for you to clone and edit as much as you like. See the different sections of the documentation and site for more ideas.
-{{% /blocks/lead %}}
-
-
-{{< blocks/section >}}
-
-
-{{< /blocks/section >}}
diff --git a/content/en/getting-started/featured-background.jpg b/content/en/getting-started/featured-background.jpg
deleted file mode 100644
index 7476923a..00000000
Binary files a/content/en/getting-started/featured-background.jpg and /dev/null differ
diff --git a/content/en/success-stories/Avast_10-25-19.pdf b/content/en/success-stories/Avast_10-25-19.pdf
new file mode 100644
index 00000000..97cbc8a0
Binary files /dev/null and b/content/en/success-stories/Avast_10-25-19.pdf differ
diff --git a/content/en/success-stories/Case Study Makerbot - Letter size_10-23-19.pdf b/content/en/success-stories/Case Study Makerbot - Letter size_10-23-19.pdf
new file mode 100644
index 00000000..44d13374
Binary files /dev/null and b/content/en/success-stories/Case Study Makerbot - Letter size_10-23-19.pdf differ
diff --git a/content/en/success-stories/Lookout_10072019.pdf b/content/en/success-stories/Lookout_10072019.pdf
new file mode 100644
index 00000000..734533c1
Binary files /dev/null and b/content/en/success-stories/Lookout_10072019.pdf differ
diff --git a/content/en/success-stories/_index.md b/content/en/success-stories/_index.md
new file mode 100644
index 00000000..71531c18
--- /dev/null
+++ b/content/en/success-stories/_index.md
@@ -0,0 +1,14 @@
+---
+layout: 'single'
+title: 'Spinnaker Success Stories'
+subtitle: 'Real world use cases about the transformative power of Spinnaker'
+subtitle_1: 'See how developers are the key change agents in their companies'
+linkTitle: 'Success Stories'
+name: 'success-stories'
+
+menu:
+ main:
+ weight: 3
+description: >
+ The Spinnaker OSS project was started at Netflix. Now, it thrives on the contributions of the broader DevOps community who have adopted it as their Continuous Delivery tool.
+---
diff --git a/content/en/success-stories/cases-logos/avast.jpg b/content/en/success-stories/cases-logos/avast.jpg
new file mode 100644
index 00000000..7154bf95
Binary files /dev/null and b/content/en/success-stories/cases-logos/avast.jpg differ
diff --git a/content/en/success-stories/cases-logos/lookout.jpg b/content/en/success-stories/cases-logos/lookout.jpg
new file mode 100644
index 00000000..8b2b25fa
Binary files /dev/null and b/content/en/success-stories/cases-logos/lookout.jpg differ
diff --git a/content/en/success-stories/cases-logos/markerbot.jpg b/content/en/success-stories/cases-logos/markerbot.jpg
new file mode 100644
index 00000000..7fe825a1
Binary files /dev/null and b/content/en/success-stories/cases-logos/markerbot.jpg differ
diff --git a/content/en/success-stories/cases-logos/netflix.jpg b/content/en/success-stories/cases-logos/netflix.jpg
new file mode 100644
index 00000000..d50026e1
Binary files /dev/null and b/content/en/success-stories/cases-logos/netflix.jpg differ
diff --git a/content/en/success-stories/cases-logos/waze.jpg b/content/en/success-stories/cases-logos/waze.jpg
new file mode 100644
index 00000000..5d1eda78
Binary files /dev/null and b/content/en/success-stories/cases-logos/waze.jpg differ
diff --git a/content/en/success-stories/featured-quotes/biden.jpg b/content/en/success-stories/featured-quotes/biden.jpg
new file mode 100644
index 00000000..4fcd8ad6
Binary files /dev/null and b/content/en/success-stories/featured-quotes/biden.jpg differ
diff --git a/content/en/success-stories/stories.svg b/content/en/success-stories/stories.svg
new file mode 100644
index 00000000..19e0ff73
--- /dev/null
+++ b/content/en/success-stories/stories.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/content/en/success-stories/testimonials-logos/adobe_logo.png b/content/en/success-stories/testimonials-logos/adobe_logo.png
new file mode 100644
index 00000000..699bbb06
Binary files /dev/null and b/content/en/success-stories/testimonials-logos/adobe_logo.png differ
diff --git a/content/en/success-stories/testimonials-logos/airbnb_logo.png b/content/en/success-stories/testimonials-logos/airbnb_logo.png
new file mode 100644
index 00000000..cc3cbc5f
Binary files /dev/null and b/content/en/success-stories/testimonials-logos/airbnb_logo.png differ
diff --git a/content/en/success-stories/testimonials-logos/comcast.png b/content/en/success-stories/testimonials-logos/comcast.png
new file mode 100644
index 00000000..f884a8d8
Binary files /dev/null and b/content/en/success-stories/testimonials-logos/comcast.png differ
diff --git a/content/en/success-stories/testimonials-logos/curefit_logo.png b/content/en/success-stories/testimonials-logos/curefit_logo.png
new file mode 100644
index 00000000..6d3f9014
Binary files /dev/null and b/content/en/success-stories/testimonials-logos/curefit_logo.png differ
diff --git a/content/en/success-stories/testimonials-logos/diligent_logo.png b/content/en/success-stories/testimonials-logos/diligent_logo.png
new file mode 100644
index 00000000..986483a3
Binary files /dev/null and b/content/en/success-stories/testimonials-logos/diligent_logo.png differ
diff --git a/content/en/success-stories/testimonials-logos/dins_logo.png b/content/en/success-stories/testimonials-logos/dins_logo.png
new file mode 100644
index 00000000..57d30359
Binary files /dev/null and b/content/en/success-stories/testimonials-logos/dins_logo.png differ
diff --git a/content/en/success-stories/testimonials-logos/jamf_logo.png b/content/en/success-stories/testimonials-logos/jamf_logo.png
new file mode 100644
index 00000000..5041dae2
Binary files /dev/null and b/content/en/success-stories/testimonials-logos/jamf_logo.png differ
diff --git a/content/en/success-stories/testimonials-logos/sap.png b/content/en/success-stories/testimonials-logos/sap.png
new file mode 100644
index 00000000..7c781a62
Binary files /dev/null and b/content/en/success-stories/testimonials-logos/sap.png differ
diff --git a/content/en/success-stories/testimonials-logos/transunion.png b/content/en/success-stories/testimonials-logos/transunion.png
new file mode 100644
index 00000000..bfed7a5d
Binary files /dev/null and b/content/en/success-stories/testimonials-logos/transunion.png differ
diff --git a/content/en/success-stories/testimonials-logos/veamly_logo.png b/content/en/success-stories/testimonials-logos/veamly_logo.png
new file mode 100644
index 00000000..70d0be4a
Binary files /dev/null and b/content/en/success-stories/testimonials-logos/veamly_logo.png differ
diff --git a/content/en/success-stories/testimonials-logos/wescale_logo.png b/content/en/success-stories/testimonials-logos/wescale_logo.png
new file mode 100644
index 00000000..7a366837
Binary files /dev/null and b/content/en/success-stories/testimonials-logos/wescale_logo.png differ
diff --git a/data/about_copy.yaml b/data/about_copy.yaml
new file mode 100644
index 00000000..c520276a
--- /dev/null
+++ b/data/about_copy.yaml
@@ -0,0 +1,16 @@
+multi_cloud_row:
+ title: Multi-Cloud
+ excerpt: 'Deploy across multiple cloud providers including AWS EC2, Kubernetes, Google Compute Engine, Google Kubernetes Engine, Google App Engine, Microsoft Azure, Openstack, Cloud Foundry, and Oracle Cloud Infrastructure, with DC/OS coming soon.'
+ image_path: assets/images/cloud.svg
+ alt: 'Multi-Cloud Logo'
+automated_releases_row:
+ title: Automated Releases
+ excerpt: 'Create deployment pipelines that run integration and system tests, spin up and down server groups, and monitor your rollouts. Trigger pipelines via git events, Jenkins, Travis CI, Docker, CRON, or other Spinnaker pipelines.'
+ image_path: assets/images/automated-releases.svg
+ alt: 'Automated Releases Logo'
+best_practices_row:
+ title: Built-in Deployment Best Practices
+ excerpt: 'Create and deploy immutable images for faster rollouts, easier rollbacks, and the elimination of hard to debug configuration drift issues. Leverage an immutable infrastructure in the cloud with built-in deployment strategies such as red/black and canary deployments.'
+ image_path: assets/images/best-practices.svg
+ image_class: best_practices_img
+ alt: 'Best Practices Logo'
diff --git a/data/cloud_providers.yaml b/data/cloud_providers.yaml
new file mode 100644
index 00000000..c0a5e9b6
--- /dev/null
+++ b/data/cloud_providers.yaml
@@ -0,0 +1,24 @@
+aws_provider:
+ image_path: /images/aws.png
+ alt: 'AWS Logo'
+ image_class: spin_cloud_provider__aws
+gcp_provider:
+ image_path: /images/gcp.png
+ alt: 'GCP Logo'
+ image_class: spin_cloud_provider__gcp
+k8s_provider:
+ image_path: /images/k8s.png
+ alt: 'Kubernetes Logo'
+ image_class: spin_cloud_provider__k8s
+azure_provider:
+ image_path: /images/azure.svg
+ alt: 'Azure Logo'
+ image_class: spin_cloud_provider__azure
+cf_provider:
+ image_path: /images/cf.png
+ alt: 'Cloud Foundry Logo'
+ image_class: spin_cloud_provider__cf
+oracle_provider:
+ image_path: /images/oracle.svg
+ alt: 'Oracle Cloud Infrastructure Logo'
+ image_class: spin_cloud_provider__oracle
diff --git a/data/features.yaml b/data/features.yaml
new file mode 100644
index 00000000..675f3cec
--- /dev/null
+++ b/data/features.yaml
@@ -0,0 +1,30 @@
+ci_integrations_feature:
+ title: CI Integrations
+ content: 'Listen to events, collect artifacts, and trigger pipelines from Jenkins or Travis CI. Triggers via git, cron, or a new image in a docker registry are also supported.'
+monitoring_integrations_feature:
+ title: Monitoring Integrations
+ content: 'Tie your releases to monitoring services Datadog, Prometheus, Stackdriver, SignalFx, or New Relic using their metrics for canary analysis.'
+cli_feature:
+ title: CLI for Setup and Admin
+ content: 'Install, configure, and update your Spinnaker instance with halyard, Spinnaker’s CLI tool.'
+deployment_strategies_feature:
+ title: Deployment Strategies
+ content: 'Configure pipelines with built-in deployment strategies such as highlander and red/black, with rolling red/black and canary in active development, or define your own custom strategy.'
+vm_bakery_feature:
+ title: VM Bakery
+ content: 'Bake immutable VM images via Packer, which comes packaged with Spinnaker and offers support for Chef and Puppet templates.'
+notifications_feature:
+ title: Notifications
+ content: 'Set up event notifications for email, Slack, HipChat, or SMS (via Twilio).'
+access_control_feature:
+ title: Role-based Access Control
+ content: 'Restrict access to projects or accounts by hooking into your internal authentication system using OAuth, SAML, LDAP, X.509 certs, Google Groups, Azure Groups, or GitHub Teams.'
+manual_judgments_feature:
+ title: Manual Judgments
+ content: 'Require a manual approval prior to releasing an update with a manual judgement stage.'
+execution_windows_feature:
+ title: Restricted Execution Windows
+ content: 'Restrict the execution of stages to certain windows of time, making sure deployments happen during off-peak traffic or when the right people are on hand to monitor the roll-out.'
+chaos_monkey_feature:
+ title: Chaos Monkey Integration
+ content: 'Test that your application can survive instance failures by terminating them on purpose.'
diff --git a/data/roles.yaml b/data/roles.yaml
index 1b46859e..6bbff00f 100644
--- a/data/roles.yaml
+++ b/data/roles.yaml
@@ -1,24 +1,19 @@
-- id: exec
- name: Executive
- shortdesc: Aliquip excepteur velit cillum qui
- prompt: Enim veniam
- longdesc: >
- Aliquip excepteur velit cillum qui exercitation non velit ut enim aliqua nulla dolore eu nostrud ea. Dolore excepteur excepteur commodo consectetur dolore reprehenderit pariatur. Id id eiusmod id anim id consequat excepteur deserunt et ad ut enim voluptate. Enim veniam ipsum aute nulla dolor non labore est veniam incididunt ex sint labore mollit. Commodo non et et minim laboris ut eu fugiat eu. Consectetur ullamco quis consectetur commodo id laboris ea qui esse exercitation deserunt cillum esse amet veniam ipsum.
+- id: captains_log
+ name: State of Spinnaker
+ prompt: Visualize the story of the Spinnaker’s growth
+ link: /docs/community/stay-informed/captains-log/
+
- id: op
- name: Operator
- shortdesc: Aliquip excepteur velit cillum qui
- prompt: Enim veniam
- longdesc: >
- Aliquip excepteur velit cillum qui exercitation non velit ut enim aliqua nulla dolore eu nostrud ea. Dolore excepteur excepteur commodo consectetur dolore reprehenderit pariatur. Id id eiusmod id anim id consequat excepteur deserunt et ad ut enim voluptate. Enim veniam ipsum aute nulla dolor non labore est veniam incididunt ex sint labore mollit. Commodo non et et minim laboris ut eu fugiat eu. Consectetur ullamco quis consectetur commodo id laboris ea qui esse exercitation deserunt cillum esse amet veniam ipsum.
-- id: appdev
- name: App Developer
- shortdesc: Aliquip excepteur velit cillum qui
- prompt: Enim veniam
- longdesc: >
- Aliquip excepteur velit cillum qui exercitation non velit ut enim aliqua nulla dolore eu nostrud ea. Dolore excepteur excepteur commodo consectetur dolore reprehenderit pariatur. Id id eiusmod id anim id consequat excepteur deserunt et ad ut enim voluptate. Enim veniam ipsum aute nulla dolor non labore est veniam incididunt ex sint labore mollit. Commodo non et et minim laboris ut eu fugiat eu. Consectetur ullamco quis consectetur commodo id laboris ea qui esse exercitation deserunt cillum esse amet veniam ipsum.
-- id: contrib
- name: Individual Contributor
- shortdesc: Aliquip excepteur velit cillum qui
- prompt: Enim veniam
- longdesc: >
- Aliquip excepteur velit cillum qui exercitation non velit ut enim aliqua nulla dolore eu nostrud ea. Dolore excepteur excepteur commodo consectetur dolore reprehenderit pariatur. Id id eiusmod id anim id consequat excepteur deserunt et ad ut enim voluptate. Enim veniam ipsum aute nulla dolor non labore est veniam incididunt ex sint labore mollit. Commodo non et et minim laboris ut eu fugiat eu. Consectetur ullamco quis consectetur commodo id laboris ea qui esse exercitation deserunt cillum esse amet veniam ipsum.
+ name: For Operators
+ prompt: Guides for setting up, operating, & migrating components
+ link: /docs/guides/operator/
+
+- id: users
+ name: For Users
+ prompt: From getting started to using pipelines, and more
+ link: /docs/guides/user/
+
+- id: tutorials
+ name: Tutorials
+ prompt: Video tutorials and codelabs
+ link: /docs/guides/tutorials/
diff --git a/data/success_stories.json b/data/success_stories.json
new file mode 100644
index 00000000..7d20999a
--- /dev/null
+++ b/data/success_stories.json
@@ -0,0 +1,297 @@
+{
+ "featured_quotes": [
+ {
+ "name": "Biden for President",
+ "logo": "featured-quotes/biden.jpg",
+ "text": "For the 2020 campaign, we relied heavily on Spinnaker for our daily workflows. It managed thousands of deployments throughout the course of the campaign. Security and high-availability was a fundamental engineering priority for us, and embracing immutable infra was a key part of that. I've used Spinnaker at a number of organizations, and its ability to manage zero-downtime deployments made it an obvious choice for the Biden campaign tech needs. At the end of the day, we were building and shipping fast, and we didn't want to spend additional effort on release engineering.",
+ "attribution": "– Matt Hodges, Engineering Director, Biden For President"
+ }
+ ],
+ "cases": [
+ {
+ "name": "Avast",
+ "link": "Avast_10-25-19.pdf",
+ "logo": "cases-logos/avast.jpg",
+ "text": "The whole goal here is to not wake people up in the middle of the night. The rollback and no-downtime deployment features are things everybody wants to do. The thing that Spinnaker promises is automated canary analysis. That to me is the holy grail to enabling continuous deployment."
+ },
+ {
+ "name": "Lookout",
+ "link": "Lookout_10072019.pdf",
+ "logo": "cases-logos/lookout.jpg",
+ "text": "We knew our product had game changing potential in the government sector, but our existing deployment framework was too human-intensive and time consuming for FedRAMP compliance. Spinnaker provided the platform, support, and delivery pipeline we needed to bring our patch deployment times up to speed."
+ },
+ {
+ "name": "MakerBot",
+ "link": "Case%20Study%20Makerbot%20-%20Letter%20size_10-23-19.pdf",
+ "logo": "cases-logos/markerbot.jpg",
+ "text": "We originally envisioned transitioning toward Kubernetes on Google Cloud over three quarters. With Spinnaker’s open source flexibility, we completed the full migration in just 2.5 months."
+ },
+ {
+ "name": "Netflix",
+ "link": "https://medium.com/netflix-techblog/global-continuous-delivery-with-spinnaker-2a6896c23ba7",
+ "logo": "cases-logos/netflix.jpg",
+ "text": "The community uptake has been tremendous. Having a platform that has an extensible model, and accommodates multiple cloud providers out of the box, means that we are one large community rather than a bunch of micro-communities focused on various forks. This has the benefit of allowing everyone within the community to take advantage of various innovations."
+ },
+ {
+ "name": "Waze",
+ "link": "https://cloud.google.com/blog/products/gcp/guest-post-multi-cloud-continuous-delivery-using-spinnaker-at-waze",
+ "logo": "cases-logos/waze.jpg",
+ "text": "Thanks to Spinnaker, developers can focus on developing business logic rather than becoming experts on each cloud platform. Teams can track the lifecycle of a deployment using several notification mechanisms including email, Slack, and SMS, allowing them to coordinate handoffs between developer and QA teams."
+ }
+ ],
+ "testimonials": [
+ {
+ "name": "Adobe",
+ "logo": "testimonials-logos/adobe_logo.png",
+ "quote": "Today, we're using Spinnaker to deploy some of our most critical apps to production.",
+ "questions": [
+ {
+ "question": "How did you discover Spinnaker?",
+ "answer": "We first heard about Spinnaker in 2016, when Netflix published a blog post about it, as a successor of Asgard. We didn't quite have the bandwidth at the time to give it a try, but later on, once our deployment process started to become more and more of a problem, a bell rang, and Spinnaker came into the picture."
+ },
+ {
+ "question": "What was your experience getting started with Spinnaker?",
+ "answer": "We started using Spinnaker at Adobe in 2017, when we came across a nice starting guide from AWS. It relied on CloudFormation to create the required resources and it took us under an hour to boot up Spinnaker and hook into our account.\nWe quickly fell in love with it. When it came to using it for our production apps, we encountered an issue though. At the time, Spinnaker was packaged for Debian (Ubuntu), but our company was pushing towards using Centos.\nWe spent quite a lot of time repackaging the Spinnaker services as RPMs and making them work, but after a few months we were able to achieve this goal. It wasn’t ideal, because we were quickly left behind with the new Spinnaker versions and services (eg. Kayenta, as the new service for automatic canary analysis, came into its existence afterwards).\nWe were excited to hear that Spinnaker could be deployed to Kubernetes and once it was packaged as a helm chart, we gave it a try. We are now quite happy with the way things are, with Spinnaker deployed to Kubernetes, using a highly available setup."
+ },
+ {
+ "question": "Where are you today with Spinnaker? What benefits has it provided to your team?",
+ "answer": "Today, we're using Spinnaker to deploy some of our most critical apps to production. Most of these apps are deployed to AWS EC2 (virtual machines), but since the beginning of 2019 we've been moving and more towards deploying our microservices to Kubernetes, using Spinnaker.\nDeploying our apps before using Spinnaker was a cumbersome process, which took quite a lot of engineering effort and was error prone. Spinnaker saved us a lot of man hours and brought a more reliable deployment process for our team. Spinnaker caught the attention of more and more teams inside Adobe and we're now onboarding them in a single Spinnaker instance."
+ },
+ {
+ "question": "What is missing or could be improved in Spinnaker?",
+ "answer": "One recurring pain point we hear from our colleagues regarding Spinnaker is the complexity of using it. In order to improve the user experience, we'd love to see more investment in the User Interface. The UI can be quite intimidating for people that are new to Spinnaker, especially when trying to deploying to Kubernetes (using the V2 integration). We're hopeful things will get better in this area and we're already starting to see progress."
+ }
+ ]
+ },
+ {
+ "name": "Airbnb",
+ "logo": "testimonials-logos/airbnb_logo.png",
+ "quote": "We are planning to open up Spinnaker to all services and make it the default deployment tool in 2020.",
+ "questions": [
+ {
+ "question": "How did you discover Spinnaker?",
+ "answer": "I watched a tech talk in 2017 about how Waze was using Spinnaker and Automated Canary Analysis. I'd been following Spinnaker's development ever since.\nThere had been several discussions in the past about Spinnaker, but these never really materialized.\nLate 2018, when the time was right for Airbnb to consider a new solution for Continuous Delivery, Spinnaker was added to the shortlist."
+ },
+ {
+ "question": "What was your experience getting started with Spinnaker?",
+ "answer": "Airbnb's existing deployment tooling (Deployboard), wasn't built with multi-stage releases in mind. While it does a good job at deploying to a specific environment. It didn't allow for orchestration of deployment pipelines. While we built good validation tooling like integration testing frameworks and traffic replay tools in-house, we couldn't integrate them into the deployment process due to the lack of deployment pipelines. As a result, these tools were not living up to their full potential.\nAs Airbnb transitioned into a Service Oriented Architecture, the deployment process became more complex. Teams ended up writing manual run books with many steps to follow to deploy a service. As the complexity increased, so did the number of incidents.\nDeployment related incidents started having a material effect on our overall website up-time. Spinnaker provides Automated Canary Analysis out of the box. Which is another big lever for us.\nRather than extending the tooling we have, we decided to invest in Spinnaker. We can leverage the community and contribute back, rather than building a closed-source in-house deployment tool. Many of the deployment challenges we face are not unique to just Airbnb."
+ },
+ {
+ "question": "Where are you today with Spinnaker? What benefits has it provided to your team?",
+ "answer": "Our tech stack consists of many Java and Ruby backend services running on Kubernetes. Our frontend is powered by Node. Airbnb is doing a large push to migrate all of its infrastructure to Kubernetes. We are migrating our monolith to SOA.\nWe are adopting Spinnaker slowly; rather than doing a forced mass-migration, we want to prove it's value-add for Airbnb engineering. We started by deploying Spinnaker with Spinnaker, so that we could get a handle on what it would take to deploy Airbnb services with Spinnaker.\nAfter that, we migrated a small subset of non-critical services. We used customer feedback from these very early adopters to drive feature development. Some Airbnb specific tooling like our in-house CI system needed to be integrated with Spinnaker.\nOnce we'd proven that we could deploy these services, we moved towards onboarding the most critical services onto Spinnaker. The goal here is to prevent regressions. This is where we are currently at.\nWe are in the process migrating all of Airbnb's payments stack and most of our core services to Spinnaker. We are already seeing the effectiveness of Spinnaker and ACA. It has already prevented a dozen regressions.\nIn parallel, we continue feature development and are load-testing Spinnaker to ensure that we can handle all of Airbnb's services. We are planning to open up Spinnaker to all services and make it the default deployment tool in 2020."
+ },
+ {
+ "question": "What is missing or could be improved in Spinnaker?",
+ "answer": "Spinnaker's User Interface can be hit or miss. Some parts are not as user-friendly. For example, figuring out why ACA failed can take up to 5 mouse-clicks. We are working on improving some parts of this and are hoping to eventually contribute back to the open source community.\nWe are very excited about the work being done around a plugin-based architecture. While Spinnaker itself is already fairly extensible as a result of it being built in Spring-boot, the team believes this will really turn Spinnaker into an extensible platform for Continuous Delivery.\nIn 2020, once our traffic tooling supports this, we will try and leverage some of the more advanced deployment patterns Spinnaker provides like Blue/Green deployments.\nWe are also excited to use Spinnaker as a more general workflow tool to run things like migrations, database schema changes, and many other processes that can be automated with deployment pipelines.\nWe'd also love to integrate ACA with our feature-flagging system (Trebuchet) so that we can safely launch features and ramp up the rollout over time."
+ }
+ ]
+ },
+ {
+ "name": "Comcast",
+ "logo": "testimonials-logos/comcast.png",
+ "quote": "Installing it on a VM was a breeze.",
+ "questions": [
+ {
+ "question": "How did you discover Spinnaker?",
+ "answer": "I was actively using Spinnaker in a previous client project."
+ },
+ {
+ "question": "What was your experience getting started with Spinnaker?",
+ "answer": "Installing it on VM was a breeze whereas installing it on K8s needed some extra steps and was not clearly documented."
+ },
+ {
+ "question": "Where are you today with Spinnaker? What benefits has it provided to your team?",
+ "answer": "Spinnaker is a good CD tool for K8s deployments."
+ },
+ {
+ "question": "What is missing or could be improved in Spinnaker?",
+ "answer": "Documentation could be improved."
+ }
+ ]
+ },
+ {
+ "name": "Cure.fit",
+ "logo": "testimonials-logos/curefit_logo.png",
+ "quote": "We wanted Jenkins to do nothing more than its CI job and were looking for something that does CD reliably.",
+ "questions": [
+ {
+ "question": "How did you discover Spinnaker?",
+ "answer": "We were planning to move our backends from VMs to Kubernetes. kubectl is a CLI that is used to update k8s' metadata and perform deployments. However, when you are an engineering division with 100 engineers, allowing each one to independently perform `kubectl apply` may result in unexpected state of services, especially when you have 50 of those. And giving Jenkins significant permissions to do that also felt wrong. We wanted Jenkins to do nothing more than its CI job and were looking for something that does CD reliably. We explored Jenkins-X, Harness, Kubeflow and Spinnaker. We tried them all and finally settled with Spinnaker for multiple reasons:\n 1. Easy pipelines\n 2. Auth and Authz\n 3. Capable of maintaining multiple k8s accounts easily: stage, alpha, prod, backup, integration.\n 4. versioned config maps and secrets.\n 5. Easy rollbacks...\n Just to name a few.\n"
+ },
+ {
+ "question": "What was your experience getting started with Spinnaker?",
+ "answer": "Since the initial k8s setup was going to be small, we deployed Spinnaker as a part of the cluster itself. As of today, we're migrating Spinnaker to its own cluster because it needs to manage many clusters, so we see having it as a separate entity useful. We had Jenkins create Docker images for applications, and push it to ECR. Jenkins also updated the helm charts if required and pushed it to a chart museum. Spinnaker pipelines take Jenkins as a trigger, and uses the build.properties from Jenkins if required. It then bakes data from build.properties into the helm chart and deploys it to the respective cluster.\nWe used halyard to deploy Spinnaker. We have a set of commands that are part of the values.yaml for Spinnaker. Using helm install deploys Spinnaker onto the prod cluster."
+ },
+ {
+ "question": "Where are you today with Spinnaker? What benefits has it provided to your team?",
+ "answer": "Currently Spinnaker serves 50% of all our service covering 70% of all our deployments pipelines. It allows for teams to test their changes on alpha before deploying to prod via manual judgement, which is the most popular feature here. It has reduced the amount of bad code entering production significantly. Moreover, having multiple environments has become easier because deploying in them is easy. Earlier we only had stage and prod as that alone was hard to manage for a small team. The deployment time is significantly lesser than what it was when we were on VMs, almost by 80%. Rollbacks is super easy, esp with versioned configmaps and secrets. This was one thing that went as a feature request in a meeting with Jenkins-X team."
+ },
+ {
+ "question": "What is missing or could be improved in Spinnaker?",
+ "answer": "It takes 2 mins for new deployments to show up after a bad deployment has been detected. So it's not possible to immediately rollback on the first error occurrence. Instant rollback trigger is a much required feature.\nFor 2 mins, it wont show the new deployment under infrastructure, hence rollback is not possible."
+ }
+ ]
+ },
+ {
+ "name": "Diligent",
+ "logo": "testimonials-logos/diligent_logo.png",
+ "quote": "2000% faster to create new services.",
+ "questions": [
+ {
+ "question": "How did you discover Spinnaker?",
+ "answer": "After a lot of R&D looking at improving our delivery model, we found Spinnaker to be the best tool for the job.\n"
+ },
+ {
+ "question": "What was your experience getting started with Spinnaker?",
+ "answer": "Some software solutions get harder to use the more you find their limitations. Spinnaker is the opposite - we have got faster and faster the more we use it."
+ },
+ {
+ "question": "Where are you today with Spinnaker? What benefits has it provided to your team?",
+ "answer": "A few metrics: \n 1600% improvement in Cycle time in some spaces (68 days to 4 days).\n 2000% faster to create new services (160 elapsed hours to under a day)\n"
+ },
+ {
+ "question": "What is missing or could be improved in Spinnaker?",
+ "answer": "The base Spinnaker docs are not good.\nArmory provides much more useful documentation."
+ }
+ ]
+ },
+ {
+ "name": "DINS",
+ "logo": "testimonials-logos/dins_logo.png",
+ "quote": "[Spinnaker is] responsible for the deployment of more than 30 different services and 100s to come.",
+ "questions": [
+ {
+ "question": "How did you discover Spinnaker?",
+ "answer": "We were trying to build an automated Continuous Delivery pipeline and searching for appropriate tools."
+ },
+ {
+ "question": "What was your experience getting started with Spinnaker?",
+ "answer": "Spinnaker is integrated with our internal systems, also Jenkins, Gitlab CI. Spinnaker became a core tool for Kubernetes deployments."
+ },
+ {
+ "question": "Where are you today with Spinnaker? What benefits has it provided to your team?",
+ "answer": "4 Spinnaker instances. Responsible for the deployment of more than 30 different services and 100s to come."
+ },
+ {
+ "question": "What is missing or could be improved in Spinnaker?",
+ "answer": "Lack of documentation related to API and pipeline as a code."
+ }
+ ]
+ },
+ {
+ "name": "Jamf",
+ "logo": "testimonials-logos/jamf_logo.png",
+ "quote": "The pipelines allow for easy auditing and ensuring all changes to pipelines are run through our controls for proper change control management.",
+ "questions": [
+ {
+ "question": "How did you discover Spinnaker?",
+ "answer": "When researching how we were planning on deploying a new set of microservices into production, we happened upon Spinnaker."
+ },
+ {
+ "question": "What was your experience getting started with Spinnaker?",
+ "answer": "It took a little bit of time to figure out how to properly configure both Spinnaker itself as well as how we structure our pipelines. This was pre v2 of the Kubernetes provider, so there was a bit of magic happening that was not well understood right away. Once we got a handle on all the features we were able to easily scale out to new services quickly and easily."
+ },
+ {
+ "question": "Where are you today with Spinnaker? What benefits has it provided to your team?",
+ "answer": "Today we are deploying a number of different production workloads with several teams across many different EKS clusters. Some teams are under SOC2 controls, while others have not made it to that point as of yet. With this in mind, the pipelines allow for easy auditing and ensuring all changes to pipelines are run through our controls for proper change control management.\nAs we look toward the future we are planning to migrate our largest application to utilize Spinnaker to do all of the heavy lifting work of application management per customer."
+ },
+ {
+ "question": "What is missing or could be improved in Spinnaker?",
+ "answer": "Ops is probably the biggest issue we have today. There is not a great way of maintaining Spinnaker while allowing for easily creating a testing environment.\nThe other issue we face as we continue to add clusters to our purview is being able to template out a pipeline to run against every cluster added to Spinnaker. Currently this is a manual operation on all of the infrastructure pieces that our team owns (logging, monitoring, node draining, calico, ingress) to add a new cluster to all of these individual pipelines. \nA way of templating that out would be beneficial from the operational aspect of managing all of these clusters for the applications that are the same."
+ }
+ ]
+ },
+ {
+ "name": "SAP Customer Experience",
+ "logo": "testimonials-logos/sap.png",
+ "quote": "Our largest development projects are deploying 25 times in production (daily average).",
+ "questions": [
+ {
+ "question": "How did you discover Spinnaker?",
+ "answer": "SAP CX Site Reliability Engineering team discovered Spinnaker a year ago. At that time our team was tasked to build a blueprint for a standard CI/CD pipeline that could improve developer's productivity and reduce the lengthy development cycles. We explored various solutions from GitLab, Bamboo, Jenkins and Concourse. During our POCs, we got a lot of success with Spinnaker."
+ },
+ {
+ "question": "What was your experience getting started with Spinnaker?",
+ "answer": "The experience in general was a mix of challenges and positiveness coming from the fact that Spinnaker was open source. We spent a lot of time on the various community Slack channels, asking questions and getting help from peers. We also did a lot of trial and error while configuring Spinnaker. But eventually, we started to understand how Spinnaker was architected and it made our experience more intuitive. We did not attend a class or webinar on Spinnaker back then. The decision to use it was solely based on the successful POC we did."
+ },
+ {
+ "question": "Where are you today with Spinnaker? What benefits has it provided to your team?",
+ "answer": "Today, we are using Spinnaker to run deployment pipelines for 10 development units. It translates to 30 Kubernetes clusters in production and 40 distinct deployment pipelines based on official templates that our team is maintaining.\nOur largest development projects are deploying 25 times in production (daily average). We have teams performing 200 daily deployments in what we call PR namespaces, which are temporary namespaces to validate features before they reach the master branch and hit production.\nSpinnaker has helped us scale our CI/CD service beyond our line of business. We are now offering it as a shared service across SAP. In addition to the scale it provided, the speed to onboard new teams has been another important benefit. By leveraging the Halyard configuration coupled with a GitOps approach, we are able to onboard teams using a self service model. Spinnaker also allows transparency and collaboration, its integration with Slack which was already widely used helps the teams providing insights on their deployment flows."
+ },
+ {
+ "question": "What is missing or could be improved in Spinnaker?",
+ "answer": "Documentation and API to manage the Halyard configuration are two important things for us. We would to programmatically configure Spinnaker without having to manipulate config files. our team has started wrapping Halyard into an API, but that work is moving slowly since we want to see where Spinnaker is heading to. We also need more security, especially around the docker images that are used by Spinnaker."
+ }
+ ]
+ },
+ {
+ "name": "TransUnion",
+ "logo": "testimonials-logos/transunion.png",
+ "quote": "We love the simple command-line interface for administration, integration with multiple platforms, and easy configurability using pipelines.",
+ "questions": [
+ {
+ "question": "How did you discover Spinnaker?",
+ "answer": "We love the simple command-line interface for administration, integration with multiple platforms, and easy configurability using pipelines."
+ },
+ {
+ "question": "What was your experience getting started with Spinnaker?",
+ "answer": "In our infrastructure, we were using Ansible and slowly Spinnaker started replacing it."
+ },
+ {
+ "question": "Where are you today with Spinnaker? What benefits has it provided to your team?",
+ "answer": "We are using Spinnaker in dev, test, and production. We have implemented Spinnaker as a deployment tool for many applications. Key advantages include faster deployments, user confirmation when needed, and access control."
+ },
+ {
+ "question": "What is missing or could be improved in Spinnaker?",
+ "answer": "The UI can be made more intuitive and troubleshooting can be made a lot easier."
+ }
+ ]
+ },
+ {
+ "name": "Veamly",
+ "logo": "testimonials-logos/veamly_logo.png",
+ "quote": "It's a true enabler for companies to embrace continuous deployment and change the way software is shipped to production.",
+ "questions": [
+ {
+ "question": "How did you discover Spinnaker?",
+ "answer": "I learnt about Spinnaker when I attended Google Cloud Summit in New York City in 2017. I was fascinated by the potential of this technology. It's a true enabler for companies to embrace continuous deployment and change the way software is shipped to production."
+ },
+ {
+ "question": "What was your experience getting started with Spinnaker?",
+ "answer": "Prior to using Spinnaker our build/deployment model was built around Jenkins. We used an internally managed Jenkins version to build and ship code to production. Jenkins quickly became a bottleneck with a high price tag for a young startup like Veamly.\nAs part of migrating our CI/CD infrastructure, we ended up using Google Cloud Build and Spinnaker to deploy docker images to our Kubernetes clusters. After we migrated our build process to use Google Cloud Build, we decided to use Spinnaker especially given that we were looking at doing canary releases instead of blue/green deployments. The transition was smooth and done in the course of a day of work."
+ },
+ {
+ "question": "Where are you today with Spinnaker? What benefits has it provided to your team?",
+ "answer": "Today, all our production deployments are done using Spinnaker, By doing so, we gained more stability, more flexibility to do rollbacks, and faster deployments. Spinnaker has also offered us more visibility about which Kubernetes cluster will be updated by a given Spinnaker pipeline."
+ },
+ {
+ "question": "What is missing or could be improved in Spinnaker?",
+ "answer": "Given our size, we have not yet run into any limitations with Spinnaker."
+ }
+ ]
+ },
+ {
+ "name": "wescale",
+ "logo": "testimonials-logos/wescale_logo.png",
+ "quote": "Spinnaker has provided my client...with more stability in their pipelines, speedier deliveries, and a strong understanding of the application delivery process.",
+ "questions": [
+ {
+ "question": "How did you discover Spinnaker?",
+ "answer": "I first discovered Spinnaker through the Netflix Engineering tech blog, which I was already following for Java-related topics."
+ },
+ {
+ "question": "What was your experience getting started with Spinnaker?",
+ "answer": "It was kind of hard to get started with it back in the old days (circa 2015-2016), then came along halyard, which allowed a smoother experience. But, it still feels a little overwhelming for newcomers to the Spinnaker platform, so I would say better than before but still far from Zero To Hero in a few commands.\nWe should provide a simple halyard template file for the most common installations options (including setting up the provider, authentication, CI tool, etc.) in just one command. More defaults should already be configured, but just in a disabled state."
+ },
+ {
+ "question": "Where are you today with Spinnaker? What benefits has it provided to your team?",
+ "answer": "Spinnaker has provided my client (I work for a consulting company) with more stability in their pipelines, speedier deliveries, and a strong understanding of the application delivery process."
+ },
+ {
+ "question": "What is missing or could be improved in Spinnaker?",
+ "answer": "My main concern or the missing link has always been a community-standardised way of doing pipeline as code with Spinnaker (PAC). This is something that has prevented Spinnaker adoption in some organisations."
+ }
+ ]
+ }
+ ]
+}
diff --git a/layouts/_default/baseof.html b/layouts/_default/baseof.html
index 27d4350f..39e6c1ce 100644
--- a/layouts/_default/baseof.html
+++ b/layouts/_default/baseof.html
@@ -4,11 +4,20 @@
{{ partial "head.html" . }}
-
+
+
{{ partial "navbar.html" . }}
-
-
+ {{ range $.Site.Data.cloud_providers }}
+
+
+
+ {{ end }}
- {{ end }}
-
-
-
-
- powered by spinnaker row
-
+
-
-
- {{ range first 4 ( where $.Site.Data.companies "is_case_study" true ) }}
-
+
+
+
+
+ Spinnaker is an open source, multi-cloud continuous delivery platform for
+ releasing software changes with high velocity and confidence.
+
+
+ Created at Netflix, it has been battle-tested in production by hundreds of
+ teams over millions of deployments. It combines a powerful and flexible
+ pipeline management system with integrations to the major cloud providers.
+