salt-formula/salt/files/cloud.providers.d/ec2.conf

# This file managed by Salt, do not edit by hand!!
{% set cloud = salt['pillar.get']('salt:cloud', {}) -%}
{% if 'aws_key' in cloud %}
ec2_ubuntu_public:
  minion:
    master: {{ cloud.get('master', 'salt') }}
  grains:
    test: True
  ssh_interface: public_ips
  id: {{ cloud.get('aws_key', 'DEFAULT') }}
  key: '{{ cloud.get('aws_secret', 'DEFAULT') }}'
  private_key: /etc/salt/pki/cloud/ec2.pem
  keyname: keyname
  location: eu-west-1
  availability_zone: eu-west-1a
  ssh_username: ubuntu
  provider: ec2
{% endif %}
Added functionality to state for salt cloud and exampel for EC2 and GCE 2014-07-20 16:59:38 +02:00			`# This file managed by Salt, do not edit by hand!!`
Avoid “set salt” jinja calls that mask the usual salt variable Most include do not expect salt to be something else than the usual salt variable giving access to all the salt modules. Instead we use cfg_salt. And for consistency we rename the master/minion variables to cfg_master/cfg_minion too. 2014-12-24 16:12:40 +01:00			`{% set cloud = salt['pillar.get']('salt:cloud', {}) -%}`
ec2/gce profiles/providers are no longer configured if they are not used. Needed because salt-cloud will attempt to load them even if they are filled with invalid default values, creating error spam. 2015-04-17 16:48:47 +02:00			`{% if 'aws_key' in cloud %}`
Added functionality to state for salt cloud and exampel for EC2 and GCE 2014-07-20 16:59:38 +02:00			`ec2_ubuntu_public:`
			`minion:`
Supplied default values for all pillar queries in provider templates. These aren't intended to function; they're here to allow the use of file.recurse on the provider folder, without requiring the user to provide pillar data for templates they're not using. 2015-04-04 00:47:08 +02:00			`master: {{ cloud.get('master', 'salt') }}`
Added functionality to state for salt cloud and exampel for EC2 and GCE 2014-07-20 16:59:38 +02:00			`grains:`
			`test: True`
			`ssh_interface: public_ips`
Supplied default values for all pillar queries in provider templates. These aren't intended to function; they're here to allow the use of file.recurse on the provider folder, without requiring the user to provide pillar data for templates they're not using. 2015-04-04 00:47:08 +02:00			`id: {{ cloud.get('aws_key', 'DEFAULT') }}`
			`key: '{{ cloud.get('aws_secret', 'DEFAULT') }}'`
cloud.providers.d can now be redirected. This obsoletes the salt:cloud:folders and salt:cloud:providers pillar entries. Provider keys have been moved to /etc/salt/pki/cloud. 2015-04-04 01:30:26 +02:00			`private_key: /etc/salt/pki/cloud/ec2.pem`
Added functionality to state for salt cloud and exampel for EC2 and GCE 2014-07-20 16:59:38 +02:00			`keyname: keyname`
			`location: eu-west-1`
			`availability_zone: eu-west-1a`
			`ssh_username: ubuntu`
Avoid “set salt” jinja calls that mask the usual salt variable Most include do not expect salt to be something else than the usual salt variable giving access to all the salt modules. Instead we use cfg_salt. And for consistency we rename the master/minion variables to cfg_master/cfg_minion too. 2014-12-24 16:12:40 +01:00			`provider: ec2`
ec2/gce profiles/providers are no longer configured if they are not used. Needed because salt-cloud will attempt to load them even if they are filled with invalid default values, creating error spam. 2015-04-17 16:48:47 +02:00			`{% endif %}`