Get desktop application:
View/edit binary Protocol Buffers messages
Configuration for the Google App Engine (GAE) provider.
Used in: ,
Whether the provider is enabled.
The list of configured accounts.
The name of the primary account.
Configuration for an App Engine account.
Used in:
The interval in seconds at which Spinnaker will poll for updates in your App Engine clusters.
The environment name for the account. Many accounts can share the same environment (e.g., dev, test, prod).
The gcloud release track that Spinnaker will use when deploying to App Engine.
A username to be used when connecting to a remote git repository server over HTTPS. If set, `gitHttpsPassword` must also be set.
A password to be used when connecting to a remote git repository server over HTTPS. If set, `gitHttpsUsername` must also be set.
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 for more information.
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 for more information.
A local directory to be used to stage source files for App Engine deployments within Clouddriver. Defaults to `/var/tmp/clouddriver`.
A list of regular expressions. Any service matching one of these regexes will be ignored by Spinnaker.
A list of regular expressions. Any version matching one of these regexes will be ignored by Spinnaker.
The Google Cloud Platform project this Spinnaker account will manage.
Fiat permissions configuration.
(Deprecated): List of required Fiat permission groups. Configure `permissions` instead.
A list of regular expressions. Any service matching one of these regexes will be indexed by Spinnaker (unless the service also matches a regex in `omitServices`).
The path to a `known_hosts` file to be used when connecting with a remote git repository over SSH.
The path to an SSH private key to be used when connecting with a remote git repository over SSH. If set, `sshPrivateKeyPassphrase` must also be set.
The passphrase to an SSH private key to be used when connecting with a remote git repository over SSH. If set, `sshPrivateKeyFilePath` must also be set.
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. Defaults to false.
A list of regular expressions. Any version matching one of these regexes will be indexed by Spinnaker (unless the version also matches a regex in `omitVersions`).
The name of the account.
Configuration for the AWS provider.
Used in: , ,
Whether the provider is enabled.
The list of configured accounts.
The name of the primary account.
Your AWS Access Key ID. Note that if you are baking AMIs with Rosco, you may also need to set `AwsBakeryDefaults.awsAccessKey`.
Your AWS Secret Key. Note that if you are baking AMIs with Rosco, you may also need to set `AwsBakeryDefaults.awsSecretKey`.
List of default regions.
Configuration for AWS-specific features.
Configuration for Spinnaker's image bakery.
A template for generating the name of the AWS key-pair from the name of the account; only used for accounts where defaultKeyPair is not specified.
Default values for AWS deployments.
Configuration for an AWS account.
Used in:
The AWS account ID to manage. See http://docs.aws.amazon.com/IAM/latest/UserGuide/console_account-alias.html for more information.
If set, Spinnaker will configure a credentials provider that uses AWS Security Token Service to assume the specified role. Examples: `user/spinnaker`, `role/spinnakerManaged`.
The name of the AWS key-pair to use. See http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html for more information.
The endpoint at which your Eureka discovery system is reachable. See https://github.com/Netflix/eureka for more information. Example: `http://.eureka.url.to.use:8080/eureka-server/v2`. Using will make Spinnaker use AWS regions in the hostname to access discovery so that you can have discovery for multiple regions.
The endpoint at which Edda is reachable. Edda is not a hard dependency of Spinnaker, but is helpful for reducing the request volume against AWS. See https://github.com/Netflix/edda for more information.
The environment name for the account. Many accounts can share the same environment (e.g., dev, test, prod).
Fiat permissions configuration.
(Deprecated): List of required Fiat permission groups. Configure `permissions` instead.
List of configured AWS lifecycle hooks.
List of configured AWS regions.
The name of the account.
Optional parameter used to identify and control access to AWS resources. Set this to the same value as the ExternalID parameter in the trust policy for the role you want to assume.
Configuration for Spinnaker's image bakery.
Used in:
The default access key used to communicate with AWS.
The secret key used to communicate with AWS.
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.
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 `awsSubnetId`.
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.
The default type of virtualization for the AMI you are building. This option must match the supported virtualization type of `AwsVirtualizationSettings.sourceAmi`. Acceptable values: `pv`, `hvm`.
List of configured base images.
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, or supplied as described here: https://spinnaker.io/setup/bakery/.
Base image configuration.
Used in:
This is the identifier used by AWS to find this base image.
A short description to help human operators identify the image.
A long description to help human operators identify the image.
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.
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, or supplied as described here: https://spinnaker.io/setup/bakery/.
Configuration for a base image for the AWS provider's bakery.
Used in:
Base image configuration.
Base image virtualization settings.
Configuration for defaults for AWS deployments.
Used in:
The default IAM role to use for deployments, when not otherwise specified.
Configuration for AWS-specific features.
Used in:
Configuration for AWS CloudFormation.
Configuration for AWS CloudFormation.
Used in:
Whether AWS CloudFormation is enabled.
Configuration for AWS Auto Scaling Lifecycle Hooks. For more information, see: https://docs.aws.amazon.com/autoscaling/ec2/userguide/lifecycle-hooks.html
Used in:
Defines the action the Auto Scaling group should take when the lifecycle hook timeout elapses or if an unexpected failure occurs. Acceptable values: `CONTINUE`, `ABANDON`.
Set the heartbeat timeout in seconds for the lifecycle hook. Instances can remain in a wait state for a finite period of time. Must be greater than or equal to 30 and less than or equal to 7200. The default is 3600 (one hour).
Type of lifecycle transition. Acceptable values: `autoscaling:EC2_INSTANCE_LAUNCHING`, `autoscaling:EC2_INSTANCE_TERMINATING`
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.
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.
An AWS region.
Used in: ,
The name of the region.
Base image virtualization settings.
Used in:
The name of the region in which to launch the EC2 instance to create the AMI.
The type of virtualization for the AMI you are building. This option must match the supported virtualization type of `sourceAmi`. Acceptable values: `pv`, `hvm`.
The EC2 instance type to use while building the AMI, such as `t2.small`.
The source AMI whose root volume will be copied and provisioned on the currently running instance. This must be an EBS-backed AMI with a root volume snapshot that you have access to.
The username to connect to SSH with. Required if using SSH.
The username to use to connect to WinRM.
The maximum hourly price to pay for a spot instance to create the AMI. Spot instances are a type of instance that EC2 starts when the current spot price is less than the maximum price you specify. Spot price will be updated based on available spot instance capacity and current spot instance requests. It may save you some costs. You can set this to `auto` for Packer to automatically discover the best spot price or to "0" to use an on demand instance (default).
Required if `spotPrice` is set to `auto`. This tells Packer what sort of AMI you are launching to find the best spot price. This must be one of: `Linux/UNIX`, `SUSE Linux`, `Windows`, `Linux/UNIX (Amazon VPC)`, `SUSE Linux (Amazon VPC)`, `Windows (Amazon VPC)`.
Configuration for the Azure provider.
Used in: , ,
Whether the provider is enabled.
The list of configured accounts.
The name of the primary account.
Configuration for Spinnaker's image bakery.
Configuration for an Azure account.
Used in:
The name of the account.
(Required) The `appKey` (password) of your service principal.
(Required) The `clientId` (also called `appId`) of your service principal.
(Required) The name of a KeyVault that contains the user name, password, and ssh public key used to create VMs
(Required) The default resource group to contain any non-application specific resources.
The environment name for the account. Many accounts can share the same environment (e.g., dev, test, prod).
The `objectId` of your service principal. This is only required if using Packer to bake Windows images.
The resource group to use if baking images with Packer.
The storage account to use if baking images with Packer.
Fiat permissions configuration.
(Deprecated): List of required Fiat permission groups. Configure `permissions` instead.
The Azure regions this Spinnaker account will manage.
(Required) The `subscriptionId` to which your service principal is assigned.
(Required) The `tenantId` to which your service principal is assigned.
If true, the SSH public key is used to provision the linux VM. If false, the password is used instead.
Configuration for Spinnaker's image bakery.
Used in:
List of configured base images.
Base image configuration.
Used in:
A short description to help human operators identify the image.
A long description to help human operators identify the image.
(Required) The Publisher name for your base image. See https://aka.ms/azspinimage to get a list of images.
(Required) The offer for your base image. See https://aka.ms/azspinimage to get a list of images.
(Required) The SKU for your base image. See https://aka.ms/azspinimage to get a list of images.
The version of your base image. This defaults to `latest` if not specified.
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.
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, or supplied as described here: https://spinnaker.io/setup/bakery/.
Configuration for a base image for the Azure provider's bakery.
Used in:
Base image configuration.
Configuration for the Cloud Foundry provider.
Used in: ,
Whether the provider is enabled.
The list of configured accounts.
The name of the primary account.
Configuration for a Spinnaker Cloud Foundry account.
Used in:
The name of the account.
(Required) Host of the Cloud Foundry Foundation API endpoint (e.g., `api.sys.somesystem.com`).
HTTP(S) URL of the Apps Manager application for the Cloud Foundry Foundation (e.g., `https://apps.sys.somesystem.com`).
The environment name for the account. Many accounts can share the same environment (e.g., dev, test, prod).
HTTP(S) URL of the metrics application for the Cloud Foundry Foundation (e.g., `https://metrics.sys.somesystem.com`).
(Required) Password for the account to use for this Cloud Foundry Foundation.
(Default: `false`) Skip SSL server certificate validation of the API endpoint.
(Required) User name for the account to use for this Cloud Foundry Foundation.
Fiat permissions configuration.
(Deprecated): List of required Fiat permission groups. Configure `permissions` instead.
Configuration for Consul.
Used in:
Whether Consul is enabled.
Reachable Consul node endpoint connected to the Consul cluster. Defaults to localhost.
Port consul is running on for every agent. Defaults to 8500.
List of data centers to cache and keep updated. Defaults to all.
Configuration for the DC/OS (Distributed Cloud Operating System) provider.
Used in: ,
Whether the provider is enabled.
The list of configured accounts.
The name of the primary account.
The list of configured clusters.
Credentials to authenticate against one or more DC/OS clusters.
Used in:
(Required) The name of the account.
(Required) The clusters against which this account will authenticate.
The environment name for the account. Many accounts can share the same environment (e.g., dev, test, prod).
(Required) The list of Docker registries to use with this DC/OS account.
Fiat permissions configuration.
(Deprecated) List of required Fiat permission groups. Configure `permissions` instead.
Configuration for a DC/OS cluster associated with a `DcosAccount`.
Used in:
(Required) The name of the cluster. Must match the name of a `DcosCluster` defined for this provider.
(Required) User or service account identifier.
Path to a file containing the secret key for service account authentication. If set, `password` should not be set.
Password for a user account. If set, `serviceKeyFile` should not be set.
Configuration for a Docker registry associated with a `DcosAccount`.
Used in:
The name of the Docker registry. Must be the name of an account configured with the Docker registry provider.
Configuration for a DC/OS cluster.
Used in:
(Required) The name of the cluster.
Root certificate file to trust for connections to the cluster.
(Required) URL of the endpoint for the DC/OS cluster's admin router.
Configuration for a DC/OS load balancer.
If `true`, disables verification of certificates from the cluster (insecure).
Configuration for a DC/OS load balancer.
Used in:
Marathon-lb image to use when creating a load balancer with Spinnaker.
Name of the secret to use for allowing marathon-lb to authenticate with the cluster. Only necessary for clusters with strict or permissive security.
Configuration for the Docker Registry provider.
Used in: ,
Whether the provider is enabled.
The list of configured accounts.
The name of the primary account.
A credential able to authenticate against a set of Docker repositories.
Used in:
The name of the account.
(Required) The registry address from which to pull and deploy images (e.g., `https://index.docker.io`).
The number of seconds between polling the Docker registry. Certain registries are sensitive to over-polling, and larger intervals (e.g., 10 minutes = 600 seconds) are desirable if you experience rate limiting. Defaults to `30`.
The number of threads on which to cache all provided repositories. Really only useful if you have a ton of repos. Defaults to 1.
Timeout in milliseconds for provided repositories. Defaults to `60,000`.
The email associated with your Docker registry. Often this only needs to be well-formed, rather than be a real address.
The environment name for the account. Many accounts can share the same environment (e.g., dev, test, prod).
If `true`, Spinnaker will treat the Docker registry as insecure and not validate the SSL certificate. Defaults to `false`.
Pagination size for the Docker `repository _catalog` endpoint. Defaults to `100`.
The Docker registry password. Only one of `password`, `passwordCommand`, and `passwordFile` should be specified.
Command to retrieve Docker token/password. The command must be available in the environment. Only one of `password`, `passwordCommand`, and `passwordFile` should be specified.
The path to a file containing your Docker password in plaintext (not a Docker `config.json` file). Only one of `password`, `passwordCommand`, and `passwordFile` should be specified.
Fiat permissions configuration.
(Deprecated) List of required Fiat permission groups. Configure `permissions` instead.
An optional list of repositories from which to cache images. If not provided, Spinnaker will attempt to read accessible repositories from the `registries _catalog` endpoint. In the case of registries that support nested paths, like GCR, you can target nested paths by including them sans their registry domain. For example: `gcr.io/my-project/path/to/image` => `my-project/path/to/image`
If `true`, Spinnaker will sort tags by creation date. Defaults to `false`. Not recommended for use with large registries; sorting performance scales poorly due to limitations of the Docker V2 API.
If `true`, Spinnaker will track digest changes. This is not recommended because it greatly increases queries to the registry, and most registries are flaky. Defaults to `false`.
The username associated with this Docker registry.
Configuration for the ECS provider.
Used in: ,
Whether the provider is enabled.
The list of configured accounts.
The name of the primary account.
Configuration for an ECS account.
Used in:
The name of the account.
The environment name for the account. Many accounts can share the same environment (e.g., dev, test, prod).
(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 for more information.
Fiat permissions configuration.
(Deprecated) List of required Fiat permission groups. Configure `permissions` instead.
Represents a release track of the gcloud tool.
Used in:
Unspecified. Do not directly use, instead omit the field.
Standard release track; runs commands via `gcloud...`
Alpha release track; runs commands via `gcloud beta...`
Alpha release track; runs commands via `gcloud alpha...`
Configuration for Spinnaker's image bakery.
Used in:
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, or supplied as described here: https://spinnaker.io/setup/bakery/.
List of configured base images.
The default zone in which to bake an image.
The Google Compute network ID or URL to use for the launched instance. Defaults to default.
If true, use the instance's internal IP instead of its external IP during baking.
The default project ID for the network and subnet to use for the VM baking your image.
Base image configuration.
Used in:
This is the identifier used by GCP to find this base image.
A short description to help human operators identify the image.
A long description to help human operators identify the image.
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.
If set to true, Deck will annotate the popup tooltip to indicate that the selected option represents an image family.
Configuration for a base image for the Google provider's bakery.
Used in:
Base image configuration.
Image source configuration.
Configuration for the Google Compute Engine (GCE) provider.
Used in: , ,
Whether the provider is enabled.
The list of configured accounts.
The name of the primary account.
Configuration for Spinnaker's image bakery.
Configuration for a Spinnaker Google account. An account maps to a credential that can authenticate against a GCP project.
Used in:
The name of the account.
(Deprecated): List of required Fiat permission groups. Configure `permissions` instead.
Fiat permissions configuration.
The GCP project this Spinnaker account will manage.
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 for more information.
Enable this flag if your GCP project has access to alpha features and you want Spinnaker to take advantage of them.
A list of GCP projects from which Spinnaker will be able to cache and deploy images. 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 for more information about sharing images across GCP projects.
Configuration for Consul.
A list of regions for caching and mutating calls. This overwrites any default regions set on the provider.
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 for more information.
Configuration for the Huawei Cloud provider.
Used in: , ,
Whether the provider is enabled.
The list of configured accounts.
The name of the primary account.
Configuration for Spinnaker's image bakery.
Configuration for a Huawei Cloud account.
Used in:
The name of the account.
The type of account.
(Deprecated) List of required Fiat permission groups. Configure `permissions` instead.
Fiat permissions configuration.
(Required) The auth URL of the cloud.
(Required) The domain name of the cloud.
The environment name for the account. Many accounts can share the same environment (e.g., dev, test, prod).
If `true`, disables certificate validation on SSL connections. Needed if certificates are self-signed. Defaults to `false`.
(Required) The password used to access the cloud.
(Required) The name of the project within the cloud.
(Required) The region(s) of the cloud.
(Required) The username used to access the cloud.
Configuration for Spinnaker's image bakery.
Used in:
List of configured base images.
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, or supplied as described here: https://spinnaker.io/setup/bakery/.
(Required) The default auth URL in which images will be baked.
(Required) The default username with which images will be baked.
(Required) The default password with which images will be baked.
The name of the default project in which images will be baked.
(Required) The default domain name in which images will be baked.
The security setting for connecting to the Huawei Cloud account. Defaults to `false`.
(Required) The VPC in which images will be baked.
(Required) The subnet in which images will be baked.
(Required) The default security group in which images will be baked.
(Required) The bandwidth size of EIP in which images will be baked.
Huawei Cloud base image settings.
Used in:
The name of the base image.
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.
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, or supplied as described here: https://spinnaker.io/setup/bakery/.
A short description to help human operators identify the image.
A long description to help human operators identify the image.
Configuration for a base image for the Huawei Cloud provider's bakery.
Used in:
Base image configuration.
Image source configuration.
Huawei Cloud virtualization settings.
Used in:
(Required) The region for the baking configuration.
(Required) The instance type for the baking configuration.
(Required) The source image ID for the baking configuration.
(Required) The SSH username for the baking configuration.
(Required) The EIP type for the baking configuration. See the API doc to get its value.
Configuration for the Kubernetes provider.
Used in: ,
Whether the provider is enabled.
The list of configured accounts.
The name of the primary account.
Configuration for a Spinnaker Kubernetes account. An account maps to a credential that can authenticate against your Kubernetes cluster.
Used in:
The name of the account.
A list of resource kinds this Spinnaker account can deploy and will cache. When no kinds are configured, this defaults to all kinds described here: https://spinnaker.io/reference/providers/kubernetes-v2/. This can only be set when omitKinds is empty or not set.
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.
The kubernetes context to be managed by Spinnaker. See 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.
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.
A list of namespaces this Spinnaker account can deploy to and will cache. When no namespaces are configured, this defaults to all namespaces.
A list of namespaces this Spinnaker account cannot deploy to or cache. This can only be set when namespaces is empty or not set.
The list of custom resources Clouddriver will manage and make available for use in Patch and Delete (Manifest) stages.
The list of kind-specific caching policies.
The 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.
The list of OAuth scopes used by kubectl to fetch an OAuth token.
The path to your kubeconfig file. By default, it will be under the Spinnaker user's home directory in the typical .kube/config location.
Fiat permissions configuration.
(Deprecated): List of required Fiat permission groups. Configure `permissions` instead.
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. Defaults to false.
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/. Defaults to false.
The raw contents of your kubeconfig file. Ignored if kubeconfigFile is set.
The path to the kubectl executable. This should be omitted unless you want to override the default kubectl exectuable.
If set, all calls to kubectl will time out after the specified number of seconds.
Whether to check whether the account has permission to read configured kinds before caching them. Kinds that the account does not have permission to read will be omitted from caching. This field defaults to true, and it is recommended to leave it at the default. If this field is set to false, any Kubernetes objects that are unreadable by the account will break caching for all objects.
When using OAuth to authenticate with your cluster, the name of the service account to use.
If true, only cache Kubernetes objects that have been deployed by Spinnaker, and ignore any other objects that exist in the cluster. Defaults to false.
If true, enable detailed logging for all communications with the Kubernetes cluster for this account. Defaults to false.
Configuration for a Docker registry.
Used in:
The configured name of the Docker registry.
The list of Docker registry namespaces usable as image sources.
Configuration for a kind-specific caching policy.
Used in:
The Kubernetes kind to which the policy applies.
The maximum number of resources an agent will cache of the specified Kubernetes kind.
Configuration for a CRD to be managed by Spinnaker. If Spinnaker does not have permission to list CRDs but you need Spinnaker to manage CRDs, you need to explicitly register each CRD.
Used in:
The Kubernetes kind of the custom resource.
The Spinnaker kind to which you would like the custom resource to map.
An integer representing the deployment priority of this resource. Resources with lower values are deployed before resources with higher values.
Whether Spinnaker should manage versioning this resource.
Whether the resource is namespaced. Defaults to true.
Configuration for the Oracle provider.
Used in: , ,
Whether the provider is enabled.
The list of configured accounts.
The name of the primary account.
Configuration for Spinnaker's image bakery.
Configuration for an Oracle account. An account maps to an Oracle Cloud Infrastructure (OCI) user.
Used in:
The name of the account.
(Deprecated) List of required Fiat permission groups. Configure `permissions` instead.
Fiat permissions configuration.
(Required) The OCID of the Oracle Compartment to use.
The environment name for the account. Many accounts can share the same environment (e.g., dev, test, prod).
(Required) Fingerprint of the public key.
Passphrase used for the private key, if it is encrypted.
(Required) An Oracle region (e.g., `us-phoenix-1`).
(Required) Path to the private key in PEM format.
(Required) The OCID of the Oracle Tenancy to use.
(Required) The OCID of the Oracle User with which to authenticate.
Configuration for Spinnaker's image bakery.
Used in:
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, or supplied as described here: https://spinnaker.io/setup/bakery/.
List of configured base images.
(Required) The name of the Availability Domain within which a new instance is launched and provisioned.
(Required) The shape for a newly created instance.
(Required) The name of the subnet within which a new instance is launched and provisioned.
Oracle base image configuration.
Used in:
The name of the base image.
A short description to help human operators identify the image.
A long description to help human operators identify the image.
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.
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, or supplied as described here: https://spinnaker.io/setup/bakery/.
Configuration for a base image for the Oracle provider's bakery.
Used in:
Oracle base image configuration.
Oracle virtualization settings.
Oracle virtualization settings.
Used in:
(Required) The OCID of the base image ID for the baking configuration.
(Required) The ssh username for the baking configuration.
Configuration for cloud provider integrations.
Used in:
Image source configuration.
Used in:
The source image. If both sourceImage and sourceImageFamily are set, sourceImage will take precedence.
The source image family to create the image from. The newest, non-deprecated image is used. If both sourceImage and sourceImageFamily are set, sourceImage will take precedence.