ResiLien
/
terraform
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
terraform/builtin/providers/aws/provider.go

576 lines
28 KiB
Go
Raw Normal View History

providers/aws: create an empty schema.Provider
2014-08-20 00:40:48 +02:00
package aws
import (
Move endpoint options into endpoints block
2016-02-07 22:40:51 +01:00
"bytes"
"fmt"
provider/aws: Add assume_role block to provider This replaces the previous `role_arn` with a block which looks like this: ``` provider "aws" { // secret key, access key etc assume_role { role_arn = "<Role ARN>" session_name = "<Session Name>" external_id = "<External ID>" } } ``` We also modify the configuration structure and read the values from the block if present into those values and adjust the call to AssumeRole to include the SessionName and ExternalID based on the values set in the configuration block. Finally we clean up the tests and add in missing error checks, and clean up the error handling logic in the Auth helper functions.
2016-09-02 19:36:01 +02:00
"log"
Move endpoint options into endpoints block
2016-02-07 22:40:51 +01:00
"github.com/hashicorp/terraform/helper/hashcode"
provider/aws: serialize SG rule access to fix race condition Because `aws_security_group_rule` resources are an abstraction on top of Security Groups, they must interact with the AWS Security Group APIs in a pattern that often results in lots of parallel requests interacting with the same security group. We've found that this pattern can trigger race conditions resulting in inconsistent behavior, including: * Rules that report as created but don't actually exist on AWS's side * Rules that show up in AWS but don't register as being created locally, resulting in follow up attempts to authorize the rule failing w/ Duplicate errors Here, we introduce a per-SG mutex that must be held by any security group before it is allowed to interact with AWS APIs. This protects the space between `DescribeSecurityGroup` and `Authorize*` / `Revoke*` calls, ensuring that no other rules interact with the SG during that span. The included test exposes the race by applying a security group with lots of rules, which based on the dependency graph can all be handled in parallel. This fails most of the time without the new locking behavior. I've omitted the mutex from `Read`, since it is only called during the Refresh walk when no changes are being made, meaning a bunch of parallel `DescribeSecurityGroup` API calls should be consistent in that case.
2015-08-24 15:59:54 +02:00
"github.com/hashicorp/terraform/helper/mutexkv"
providers/aws: create an empty schema.Provider
2014-08-20 00:40:48 +02:00
"github.com/hashicorp/terraform/helper/schema"
Refactored the last two resources
2014-11-24 14:04:48 +01:00
"github.com/hashicorp/terraform/terraform"
providers/aws: create an empty schema.Provider
2014-08-20 00:40:48 +02:00
)
Refactored the last two resources
2014-11-24 14:04:48 +01:00
// Provider returns a terraform.ResourceProvider.
func Provider() terraform.ResourceProvider {
providers/aws: create an empty schema.Provider
2014-08-20 00:40:48 +02:00
// TODO: Move the validation to this, requires conditional schemas
// TODO: Move the configuration to this, requires validation
providers/aws: style nitpick
2015-06-29 07:46:49 +02:00
// The actual provider
providers/aws: create an empty schema.Provider
2014-08-20 00:40:48 +02:00
return &schema.Provider{
providers/aws: convert validation to helper/schema
2014-09-10 06:44:31 +02:00
Schema: map[string]*schema.Schema{
provider/aws: Clean up AWS provider schema defns Remove unnecessary &schema.Schema from the AWS provider schema definition.
2016-09-02 19:29:59 +02:00
"access_key": {
provider/aws: Refactor AWS Authentication chain - update auth checking to check metadata header - refactor tests to not export os env vars
2015-12-10 22:43:13 +01:00
Type: schema.TypeString,
Optional: true,
Default: "",
Add descriptions for AWS inputs
2014-09-29 22:30:28 +02:00
Description: descriptions["access_key"],
providers/aws: convert validation to helper/schema
2014-09-10 06:44:31 +02:00
},
provider/aws: Clean up AWS provider schema defns Remove unnecessary &schema.Schema from the AWS provider schema definition.
2016-09-02 19:29:59 +02:00
"secret_key": {
provider/aws: Refactor AWS Authentication chain - update auth checking to check metadata header - refactor tests to not export os env vars
2015-12-10 22:43:13 +01:00
Type: schema.TypeString,
Optional: true,
Default: "",
Add descriptions for AWS inputs
2014-09-29 22:30:28 +02:00
Description: descriptions["secret_key"],
providers/aws: convert validation to helper/schema
2014-09-10 06:44:31 +02:00
},
Refactored about 90% Still need to update 2 resources and check the acceptance tests, but overall we’re nearly there :smiley:
2014-11-21 17:58:34 +01:00
provider/aws: Clean up AWS provider schema defns Remove unnecessary &schema.Schema from the AWS provider schema definition.
2016-09-02 19:29:59 +02:00
"profile": {
provider/aws: Add profile to provider config This allows specification of the profile for the shared credentials provider for AWS to be specified in Terraform configuration. This is useful if defining providers with aliases, or if you don't want to set environment variables. Example: $ aws configure --profile this_is_dog ... enter keys $ cat main.tf provider "aws" { profile = "this_is_dog" # Optionally also specify the path to the credentials file shared_credentials_file = "/tmp/credentials" } This is equivalent to specifying AWS_PROFILE or AWS_SHARED_CREDENTIALS_FILE in the environment.
2016-01-11 16:22:09 +01:00
Type: schema.TypeString,
Optional: true,
Default: "",
Description: descriptions["profile"],
},
provider/aws: Add assume_role block to provider This replaces the previous `role_arn` with a block which looks like this: ``` provider "aws" { // secret key, access key etc assume_role { role_arn = "<Role ARN>" session_name = "<Session Name>" external_id = "<External ID>" } } ``` We also modify the configuration structure and read the values from the block if present into those values and adjust the call to AssumeRole to include the SessionName and ExternalID based on the values set in the configuration block. Finally we clean up the tests and add in missing error checks, and clean up the error handling logic in the Auth helper functions.
2016-09-02 19:36:01 +02:00
"assume_role": assumeRoleSchema(),
provider/aws: Clean up AWS provider schema defns Remove unnecessary &schema.Schema from the AWS provider schema definition.
2016-09-02 19:29:59 +02:00
"shared_credentials_file": {
provider/aws: Add profile to provider config This allows specification of the profile for the shared credentials provider for AWS to be specified in Terraform configuration. This is useful if defining providers with aliases, or if you don't want to set environment variables. Example: $ aws configure --profile this_is_dog ... enter keys $ cat main.tf provider "aws" { profile = "this_is_dog" # Optionally also specify the path to the credentials file shared_credentials_file = "/tmp/credentials" } This is equivalent to specifying AWS_PROFILE or AWS_SHARED_CREDENTIALS_FILE in the environment.
2016-01-11 16:22:09 +01:00
Type: schema.TypeString,
Optional: true,
Default: "",
Description: descriptions["shared_credentials_file"],
},
provider/aws: Clean up AWS provider schema defns Remove unnecessary &schema.Schema from the AWS provider schema definition.
2016-09-02 19:29:59 +02:00
"token": {
provider/aws: Refactor AWS Authentication chain - update auth checking to check metadata header - refactor tests to not export os env vars
2015-12-10 22:43:13 +01:00
Type: schema.TypeString,
Optional: true,
Default: "",
Support session token in AWS credentials Session tokens are necessary to utilize temporary credentials. http://docs.aws.amazon.com/STS/latest/UsingSTS/Welcome.html
2015-04-20 20:26:59 +02:00
Description: descriptions["token"],
},
provider/aws: Clean up AWS provider schema defns Remove unnecessary &schema.Schema from the AWS provider schema definition.
2016-09-02 19:29:59 +02:00
"region": {
Read the "standard" AWS environment variables This is 100% backwards-compatible
2015-01-22 21:30:27 +01:00
Type: schema.TypeString,
Required: true,
DefaultFunc: schema.MultiEnvDefaultFunc([]string{
"AWS_REGION",
"AWS_DEFAULT_REGION",
}, nil),
Refactored about 90% Still need to update 2 resources and check the acceptance tests, but overall we’re nearly there :smiley:
2014-11-21 17:58:34 +01:00
Description: descriptions["region"],
InputDefault: "us-east-1",
},
AWS account ID protection added
2015-04-20 00:54:42 +02:00
provider/aws: Clean up AWS provider schema defns Remove unnecessary &schema.Schema from the AWS provider schema definition.
2016-09-02 19:29:59 +02:00
"max_retries": {
aws: make MaxRetries for API calls configurable - Make it configurable in the AWS provider by add an option 'max_retries'. - Set the default from 3 to 11 retries.
2015-05-03 11:08:47 +02:00
Type: schema.TypeInt,
Optional: true,
Default: 11,
Description: descriptions["max_retries"],
},
provider/aws: Clean up AWS provider schema defns Remove unnecessary &schema.Schema from the AWS provider schema definition.
2016-09-02 19:29:59 +02:00
"allowed_account_ids": {
AWS account ID protection added
2015-04-20 00:54:42 +02:00
Type: schema.TypeSet,
Elem: &schema.Schema{Type: schema.TypeString},
Optional: true,
ConflictsWith: []string{"forbidden_account_ids"},
Use built-in schema.HashString.
2016-02-08 00:51:26 +01:00
Set: schema.HashString,
AWS account ID protection added
2015-04-20 00:54:42 +02:00
},
provider/aws: Clean up AWS provider schema defns Remove unnecessary &schema.Schema from the AWS provider schema definition.
2016-09-02 19:29:59 +02:00
"forbidden_account_ids": {
AWS account ID protection added
2015-04-20 00:54:42 +02:00
Type: schema.TypeSet,
Elem: &schema.Schema{Type: schema.TypeString},
Optional: true,
ConflictsWith: []string{"allowed_account_ids"},
Use built-in schema.HashString.
2016-02-08 00:51:26 +01:00
Set: schema.HashString,
AWS account ID protection added
2015-04-20 00:54:42 +02:00
},
dynamodb-local Add `dynamodb_endpoint` allowing to change the DynamoDB Endpoint for example to connect to dynamodb-local
2015-07-22 23:57:29 +02:00
provider/aws: Clean up AWS provider schema defns Remove unnecessary &schema.Schema from the AWS provider schema definition.
2016-09-02 19:29:59 +02:00
"dynamodb_endpoint": {
dynamodb-local Add `dynamodb_endpoint` allowing to change the DynamoDB Endpoint for example to connect to dynamodb-local
2015-07-22 23:57:29 +02:00
Type: schema.TypeString,
Optional: true,
Default: "",
Description: descriptions["dynamodb_endpoint"],
},
provider/aws: allow local kinesis
2015-09-16 18:58:46 +02:00
provider/aws: Clean up AWS provider schema defns Remove unnecessary &schema.Schema from the AWS provider schema definition.
2016-09-02 19:29:59 +02:00
"kinesis_endpoint": {
provider/aws: allow local kinesis
2015-09-16 18:58:46 +02:00
Type: schema.TypeString,
Optional: true,
Default: "",
Description: descriptions["kinesis_endpoint"],
},
Skip IAM/STS validation and metadata check (#7874) * Skip IAM/STS validation and metadata check * Skip IAM/STS identity validation - For environments or other api implementations where there are no IAM/STS endpoints available, this option lets you opt out from that provider initialization step. * Skip metdata api check - For environments in which you know ahead of time there isn't going to be a metadta api endpoint, this option lets you opt out from that check to save time. * Allow iam/sts initialization even if skipping account/cred validation (#7874) * Split out skip of IAM validation into credentials and account id (#7874)
2016-08-10 16:10:34 +02:00
Move endpoint options into endpoints block
2016-02-07 22:40:51 +01:00
"endpoints": endpointsSchema(),
provider/aws: Clean up AWS provider schema defns Remove unnecessary &schema.Schema from the AWS provider schema definition.
2016-09-02 19:29:59 +02:00
"insecure": {
Move endpoint options into endpoints block
2016-02-07 22:40:51 +01:00
Type: schema.TypeBool,
Optional: true,
Default: false,
Description: descriptions["insecure"],
},
Skip IAM/STS validation and metadata check (#7874) * Skip IAM/STS validation and metadata check * Skip IAM/STS identity validation - For environments or other api implementations where there are no IAM/STS endpoints available, this option lets you opt out from that provider initialization step. * Skip metdata api check - For environments in which you know ahead of time there isn't going to be a metadta api endpoint, this option lets you opt out from that check to save time. * Allow iam/sts initialization even if skipping account/cred validation (#7874) * Split out skip of IAM validation into credentials and account id (#7874)
2016-08-10 16:10:34 +02:00
provider/aws: Clean up AWS provider schema defns Remove unnecessary &schema.Schema from the AWS provider schema definition.
2016-09-02 19:29:59 +02:00
"skip_credentials_validation": {
Skip IAM/STS validation and metadata check (#7874) * Skip IAM/STS validation and metadata check * Skip IAM/STS identity validation - For environments or other api implementations where there are no IAM/STS endpoints available, this option lets you opt out from that provider initialization step. * Skip metdata api check - For environments in which you know ahead of time there isn't going to be a metadta api endpoint, this option lets you opt out from that check to save time. * Allow iam/sts initialization even if skipping account/cred validation (#7874) * Split out skip of IAM validation into credentials and account id (#7874)
2016-08-10 16:10:34 +02:00
Type: schema.TypeBool,
Optional: true,
Default: false,
aws: Change field names + desc according to reality - skip_iam_creds_validation => skip_credentials_validation - skip_iam_account_id => skip_requesting_account_id
2016-08-10 17:46:02 +02:00
Description: descriptions["skip_credentials_validation"],
Skip IAM/STS validation and metadata check (#7874) * Skip IAM/STS validation and metadata check * Skip IAM/STS identity validation - For environments or other api implementations where there are no IAM/STS endpoints available, this option lets you opt out from that provider initialization step. * Skip metdata api check - For environments in which you know ahead of time there isn't going to be a metadta api endpoint, this option lets you opt out from that check to save time. * Allow iam/sts initialization even if skipping account/cred validation (#7874) * Split out skip of IAM validation into credentials and account id (#7874)
2016-08-10 16:10:34 +02:00
},
provider/aws: Clean up AWS provider schema defns Remove unnecessary &schema.Schema from the AWS provider schema definition.
2016-09-02 19:29:59 +02:00
"skip_requesting_account_id": {
Skip IAM/STS validation and metadata check (#7874) * Skip IAM/STS validation and metadata check * Skip IAM/STS identity validation - For environments or other api implementations where there are no IAM/STS endpoints available, this option lets you opt out from that provider initialization step. * Skip metdata api check - For environments in which you know ahead of time there isn't going to be a metadta api endpoint, this option lets you opt out from that check to save time. * Allow iam/sts initialization even if skipping account/cred validation (#7874) * Split out skip of IAM validation into credentials and account id (#7874)
2016-08-10 16:10:34 +02:00
Type: schema.TypeBool,
Optional: true,
Default: false,
aws: Change field names + desc according to reality - skip_iam_creds_validation => skip_credentials_validation - skip_iam_account_id => skip_requesting_account_id
2016-08-10 17:46:02 +02:00
Description: descriptions["skip_requesting_account_id"],
Skip IAM/STS validation and metadata check (#7874) * Skip IAM/STS validation and metadata check * Skip IAM/STS identity validation - For environments or other api implementations where there are no IAM/STS endpoints available, this option lets you opt out from that provider initialization step. * Skip metdata api check - For environments in which you know ahead of time there isn't going to be a metadta api endpoint, this option lets you opt out from that check to save time. * Allow iam/sts initialization even if skipping account/cred validation (#7874) * Split out skip of IAM validation into credentials and account id (#7874)
2016-08-10 16:10:34 +02:00
},
provider/aws: Clean up AWS provider schema defns Remove unnecessary &schema.Schema from the AWS provider schema definition.
2016-09-02 19:29:59 +02:00
"skip_metadata_api_check": {
Skip IAM/STS validation and metadata check (#7874) * Skip IAM/STS validation and metadata check * Skip IAM/STS identity validation - For environments or other api implementations where there are no IAM/STS endpoints available, this option lets you opt out from that provider initialization step. * Skip metdata api check - For environments in which you know ahead of time there isn't going to be a metadta api endpoint, this option lets you opt out from that check to save time. * Allow iam/sts initialization even if skipping account/cred validation (#7874) * Split out skip of IAM validation into credentials and account id (#7874)
2016-08-10 16:10:34 +02:00
Type: schema.TypeBool,
Optional: true,
Default: false,
Description: descriptions["skip_metadata_api_check"],
},
Add S3 endpoint override ability and expose S3 path style option (#7871) * Overriding S3 endpoint - Enable specifying your own S3 api endpoint to override the default one, under endpoints. * Force S3 path style - Expose this option from the aws-sdk-go configuration to the provider.
2016-08-12 18:52:12 +02:00
provider/aws: Clean up AWS provider schema defns Remove unnecessary &schema.Schema from the AWS provider schema definition.
2016-09-02 19:29:59 +02:00
"s3_force_path_style": {
Add S3 endpoint override ability and expose S3 path style option (#7871) * Overriding S3 endpoint - Enable specifying your own S3 api endpoint to override the default one, under endpoints. * Force S3 path style - Expose this option from the aws-sdk-go configuration to the provider.
2016-08-12 18:52:12 +02:00
Type: schema.TypeBool,
Optional: true,
Default: false,
Description: descriptions["s3_force_path_style"],
},
providers/aws: convert validation to helper/schema
2014-09-10 06:44:31 +02:00
},
provider/aws: Add aws_availability_zones source This commit adds a data source with a single list, `instance` for the schema which gets populated with the availability zones to which an account has access.
2016-05-14 20:18:51 +02:00
DataSourcesMap: map[string]*schema.Resource{
Add aws_ecs_container_definition data source this datasource allows terraform to work with externally modified state, e.g. when you're using an ECS service which is continously updated by your CI via the AWS CLI. right now you'd have to wrap terraform into a shell script which looks up the current image digest, so running terraform won't change the updated service. using the aws_ecs_container_definition data source you can now leverage terraform, removing the wrapper entirely.
2016-06-15 19:55:45 +02:00
"aws_ami": dataSourceAwsAmi(),
provider/aws: availability zone data source This adds a singular data source in addition to the existing plural one. This allows retrieving data about a specific AZ. As a helper for writing reusable modules, the AZ letter (without its usual region name prefix) is exposed so that it can be used in region-agnostic mappings where a different value is used per AZ, such as for subnet numbering schemes.
2016-05-22 19:21:02 +02:00
"aws_availability_zone": dataSourceAwsAvailabilityZone(),
Add aws_ecs_container_definition data source this datasource allows terraform to work with externally modified state, e.g. when you're using an ECS service which is continously updated by your CI via the AWS CLI. right now you'd have to wrap terraform into a shell script which looks up the current image digest, so running terraform won't change the updated service. using the aws_ecs_container_definition data source you can now leverage terraform, removing the wrapper entirely.
2016-06-15 19:55:45 +02:00
"aws_availability_zones": dataSourceAwsAvailabilityZones(),
Add AWS Billing & Cost Management service account This adds a very simple data source for the AWS Billing account ID magic number. Used to allow AWS to dump detailed billing reports into an S3 bucket you control. http://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/billing-getting-started.html#step-2
2016-09-07 07:43:45 +02:00
"aws_billing_service_account": dataSourceAwsBillingServiceAccount(),
provider/aws: Add aws_caller_identity data source This data source provides access during configuration to the ID of the AWS account for the connection to AWS. It is primarily useful for interpolating into policy documents, for example when creating the policy for an ELB or ALB access log bucket. This will need revisiting and further testing once the work for AssumeRole is integrated.
2016-08-15 23:43:24 +02:00
"aws_caller_identity": dataSourceAwsCallerIdentity(),
provider/aws: Add cloudformation_stack data source
2016-06-02 11:08:12 +02:00
"aws_cloudformation_stack": dataSourceAwsCloudFormationStack(),
provider/aws: DataSource for RedShift Account ID (#8224) When you need to enable monitoring for Redshift, you need to create the correct policy in the bucket for logging. This needs to have the Redshift Account ID for a given region. This data source provides a handy lookup for this http://docs.aws.amazon.com/redshift/latest/mgmt/db-auditing.html#db-auditing-enable-logging % make testacc TEST=./builtin/providers/aws % TESTARGS='-run=TestAccAWSRedshiftAccountId_basic' 2 ↵ ✹ ✭ ==> Checking that code complies with gofmt requirements... /Users/stacko/Code/go/bin/stringer go generate $(go list ./... | grep -v /terraform/vendor/) 2016/08/16 14:39:35 Generated command/internal_plugin_list.go TF_ACC=1 go test ./builtin/providers/aws -v -run=TestAccAWSRedshiftAccountId_basic -timeout 120m === RUN TestAccAWSRedshiftAccountId_basic --- PASS: TestAccAWSRedshiftAccountId_basic (19.47s) PASS ok github.com/hashicorp/terraform/builtin/providers/aws 19.483s
2016-08-16 18:58:46 +02:00
"aws_ecs_container_definition": dataSourceAwsEcsContainerDefinition(),
aws: Implement naming changes for aws_elb_service_account
2016-08-16 22:05:27 +02:00
"aws_elb_service_account": dataSourceAwsElbServiceAccount(),
Add aws_ecs_container_definition data source this datasource allows terraform to work with externally modified state, e.g. when you're using an ECS service which is continously updated by your CI via the AWS CLI. right now you'd have to wrap terraform into a shell script which looks up the current image digest, so running terraform won't change the updated service. using the aws_ecs_container_definition data source you can now leverage terraform, removing the wrapper entirely.
2016-06-15 19:55:45 +02:00
"aws_iam_policy_document": dataSourceAwsIamPolicyDocument(),
Added IP ranges from AWS
2016-08-04 19:20:14 +02:00
"aws_ip_ranges": dataSourceAwsIPRanges(),
provider/aws: Data source to provides details about a specific AWS prefix list (#9566) * Add AWS Prefix List data source. AWS Prefix List data source acceptance test. AWS Prefix List data source documentation. * Improve error message when PL not matched.
2016-10-27 15:58:24 +02:00
"aws_prefix_list": dataSourceAwsPrefixList(),
provider/aws: DataSource for RedShift Account ID (#8224) When you need to enable monitoring for Redshift, you need to create the correct policy in the bucket for logging. This needs to have the Redshift Account ID for a given region. This data source provides a handy lookup for this http://docs.aws.amazon.com/redshift/latest/mgmt/db-auditing.html#db-auditing-enable-logging % make testacc TEST=./builtin/providers/aws % TESTARGS='-run=TestAccAWSRedshiftAccountId_basic' 2 ↵ ✹ ✭ ==> Checking that code complies with gofmt requirements... /Users/stacko/Code/go/bin/stringer go generate $(go list ./... | grep -v /terraform/vendor/) 2016/08/16 14:39:35 Generated command/internal_plugin_list.go TF_ACC=1 go test ./builtin/providers/aws -v -run=TestAccAWSRedshiftAccountId_basic -timeout 120m === RUN TestAccAWSRedshiftAccountId_basic --- PASS: TestAccAWSRedshiftAccountId_basic (19.47s) PASS ok github.com/hashicorp/terraform/builtin/providers/aws 19.483s
2016-08-16 18:58:46 +02:00
"aws_redshift_service_account": dataSourceAwsRedshiftServiceAccount(),
provider/aws: aws_region data source The primary purpose of this data source is to ask the question "what is my current region?", but it can also be used to retrieve the endpoint hostname for a particular (possibly non-current) region, should that be useful for some esoteric case.
2016-05-22 19:22:09 +02:00
"aws_region": dataSourceAwsRegion(),
Add aws_ecs_container_definition data source this datasource allows terraform to work with externally modified state, e.g. when you're using an ECS service which is continously updated by your CI via the AWS CLI. right now you'd have to wrap terraform into a shell script which looks up the current image digest, so running terraform won't change the updated service. using the aws_ecs_container_definition data source you can now leverage terraform, removing the wrapper entirely.
2016-06-15 19:55:45 +02:00
"aws_s3_bucket_object": dataSourceAwsS3BucketObject(),
provider/aws: aws_subnet data source
2016-05-22 17:23:25 +02:00
"aws_subnet": dataSourceAwsSubnet(),
provider/aws: data source for AWS Security Group (#9604) * provider/aws: data source for AWS Security Group * provider/aws: add documentation for data source for AWS Security Group * provider/aws: data source for AWS Security Group (improve if condition and syntax) * fix fmt
2016-10-27 19:17:58 +02:00
"aws_security_group": dataSourceAwsSecurityGroup(),
provider/aws: aws_vpc data source
2016-05-22 17:25:30 +02:00
"aws_vpc": dataSourceAwsVpc(),
provider/aws: Add aws_availability_zones source This commit adds a data source with a single list, `instance` for the schema which gets populated with the availability zones to which an account has access.
2016-05-14 20:18:51 +02:00
},
providers/aws: resource_aws_eip is in new framework
2014-08-20 01:56:23 +02:00
ResourcesMap: map[string]*schema.Resource{
provider/aws: Add `aws_alb` resource This commit adds a resource, acceptance tests and documentation for the new Application Load Balancer (aws_alb). We choose to use the name alb over the package name, elbv2, in order to avoid confusion. This is the first in a series of commits to fully support the new resources necessary for Application Load Balancers.
2016-08-15 23:09:40 +02:00
"aws_alb": resourceAwsAlb(),
provider/aws: Add aws_alb_listener resource This commit adds the `aws_alb_listener` resource and associated acceptance tests and documentation.
2016-08-17 19:42:18 +02:00
"aws_alb_listener": resourceAwsAlbListener(),
provider/aws: Add aws_alb_listener_rule resource This commit adds the aws_alb_listener_rule resource along with acceptance tests and documentation.
2016-08-19 00:43:11 +02:00
"aws_alb_listener_rule": resourceAwsAlbListenerRule(),
provider/aws: Add aws_alb_target_group resource This commit adds a resource, acceptance tests and documentation for the Target Groups for Application Load Balancers. This is the second in a series of commits to fully support the new resources necessary for Application Load Balancers.
2016-08-15 23:10:54 +02:00
"aws_alb_target_group": resourceAwsAlbTargetGroup(),
provider/aws: Add aws_alb_target_group_attachment
2016-08-19 17:12:19 +02:00
"aws_alb_target_group_attachment": resourceAwsAlbTargetGroupAttachment(),
provider/aws: Add Elastic Beanstalk Application, Configuration Template, and Environment This adds support for Elastic Beanstalk Applications, Configuration Templates, and Environments. This is a combined work of @catsby, @dharrisio, @Bowbaq, and @jen20
2016-03-07 21:42:30 +01:00
"aws_ami": resourceAwsAmi(),
"aws_ami_copy": resourceAwsAmiCopy(),
"aws_ami_from_instance": resourceAwsAmiFromInstance(),
Implementing aws_ami_launch_permission. (#7365)
2016-07-22 00:08:32 +02:00
"aws_ami_launch_permission": resourceAwsAmiLaunchPermission(),
provider/aws: Add support for api_gateway_account (#6321)
2016-04-27 14:08:59 +02:00
"aws_api_gateway_account": resourceAwsApiGatewayAccount(),
provider/aws: Add Elastic Beanstalk Application, Configuration Template, and Environment This adds support for Elastic Beanstalk Applications, Configuration Templates, and Environments. This is a combined work of @catsby, @dharrisio, @Bowbaq, and @jen20
2016-03-07 21:42:30 +01:00
"aws_api_gateway_api_key": resourceAwsApiGatewayApiKey(),
provider/aws: Add support for api_gateway_authorizer (#6320)
2016-04-25 13:22:37 +02:00
"aws_api_gateway_authorizer": resourceAwsApiGatewayAuthorizer(),
provider/aws: aws_api_gateway_base_path_mapping resource implementation API Gateway allows users to "claim" a domain name for use as a custom hostname for deployed API endpoints, and then use this base path mapping resource to expose a particular API deployment at a path on such a domain. The acceptance tests use certificates from the aws_api_gateway_domain_name tests which expire in 2026; we'll need to generate some more certificates before we get there.
2016-08-21 22:41:59 +02:00
"aws_api_gateway_base_path_mapping": resourceAwsApiGatewayBasePathMapping(),
provider/aws: Add API Gateway Client Certificate
2016-09-11 16:14:10 +02:00
"aws_api_gateway_client_certificate": resourceAwsApiGatewayClientCertificate(),
provider/aws: Add Elastic Beanstalk Application, Configuration Template, and Environment This adds support for Elastic Beanstalk Applications, Configuration Templates, and Environments. This is a combined work of @catsby, @dharrisio, @Bowbaq, and @jen20
2016-03-07 21:42:30 +01:00
"aws_api_gateway_deployment": resourceAwsApiGatewayDeployment(),
provider/aws: aws_api_gateway_domain_name resource implementation API Gateway allows users to "claim" a domain name for use as a custom hostname for deployed API endpoints. The domain name resource just claims the domain name; a user would then use a "base path mapping" resource (to be implemented in a later commit) to map a particular API to a particular path prefix on that domain. The acceptance tests contain some TLS certificates that expire in 2026; we'll need to generate some more certificates before we get there.
2016-08-21 18:19:48 +02:00
"aws_api_gateway_domain_name": resourceAwsApiGatewayDomainName(),
provider/aws: Add Elastic Beanstalk Application, Configuration Template, and Environment This adds support for Elastic Beanstalk Applications, Configuration Templates, and Environments. This is a combined work of @catsby, @dharrisio, @Bowbaq, and @jen20
2016-03-07 21:42:30 +01:00
"aws_api_gateway_integration": resourceAwsApiGatewayIntegration(),
"aws_api_gateway_integration_response": resourceAwsApiGatewayIntegrationResponse(),
"aws_api_gateway_method": resourceAwsApiGatewayMethod(),
"aws_api_gateway_method_response": resourceAwsApiGatewayMethodResponse(),
"aws_api_gateway_model": resourceAwsApiGatewayModel(),
"aws_api_gateway_resource": resourceAwsApiGatewayResource(),
"aws_api_gateway_rest_api": resourceAwsApiGatewayRestApi(),
"aws_app_cookie_stickiness_policy": resourceAwsAppCookieStickinessPolicy(),
AWS Application AutoScaling Initial work on two new resource types: * `aws_appautoscaling_target` * `aws_appautoscaling_policy` Fix acc tests
2016-07-15 13:54:36 +02:00
"aws_appautoscaling_target": resourceAwsAppautoscalingTarget(),
"aws_appautoscaling_policy": resourceAwsAppautoscalingPolicy(),
provider/aws: Add Elastic Beanstalk Application, Configuration Template, and Environment This adds support for Elastic Beanstalk Applications, Configuration Templates, and Environments. This is a combined work of @catsby, @dharrisio, @Bowbaq, and @jen20
2016-03-07 21:42:30 +01:00
"aws_autoscaling_group": resourceAwsAutoscalingGroup(),
"aws_autoscaling_notification": resourceAwsAutoscalingNotification(),
"aws_autoscaling_policy": resourceAwsAutoscalingPolicy(),
"aws_autoscaling_schedule": resourceAwsAutoscalingSchedule(),
"aws_cloudformation_stack": resourceAwsCloudFormationStack(),
CloudFront distribution and origin access identity support (#5221) * CloudFront implementation v3 * Update tests * Refactor - new resource: aws_cloudfront_distribution * Includes a complete re-write of the old aws_cloudfront_web_distribution resource to bring it to feature parity with API and CloudFormation. * Also includes the aws_cloudfront_origin_access_identity resource to generate origin access identities for use with S3.
2016-04-14 21:55:11 +02:00
"aws_cloudfront_distribution": resourceAwsCloudFrontDistribution(),
"aws_cloudfront_origin_access_identity": resourceAwsCloudFrontOriginAccessIdentity(),
provider/aws: Add Elastic Beanstalk Application, Configuration Template, and Environment This adds support for Elastic Beanstalk Applications, Configuration Templates, and Environments. This is a combined work of @catsby, @dharrisio, @Bowbaq, and @jen20
2016-03-07 21:42:30 +01:00
"aws_cloudtrail": resourceAwsCloudTrail(),
"aws_cloudwatch_event_rule": resourceAwsCloudWatchEventRule(),
"aws_cloudwatch_event_target": resourceAwsCloudWatchEventTarget(),
"aws_cloudwatch_log_group": resourceAwsCloudWatchLogGroup(),
provider/aws: Add support for CloudWatch Log Metric Filter
2016-02-29 14:07:45 +01:00
"aws_cloudwatch_log_metric_filter": resourceAwsCloudWatchLogMetricFilter(),
provider/aws: `aws_cloudwatch_log_stream` resource This is a requirement for enabling CloudWatch Logging on Kinesis Firehost % make testacc TEST=./builtin/providers/aws TESTARGS='-run=TestAccAWSCloudWatchLogStream_' ==> Checking that code complies with gofmt requirements... go generate $(go list ./... | grep -v /terraform/vendor/) 2016/09/02 16:19:14 Generated command/internal_plugin_list.go TF_ACC=1 go test ./builtin/providers/aws -v -run=TestAccAWSCloudWatchLogStream_ -timeout 120m === RUN TestAccAWSCloudWatchLogStream_basic --- PASS: TestAccAWSCloudWatchLogStream_basic (22.31s) === RUN TestAccAWSCloudWatchLogStream_disappears --- PASS: TestAccAWSCloudWatchLogStream_disappears (21.21s) PASS ok github.com/hashicorp/terraform/builtin/providers/aws 43.538s
2016-09-02 13:29:48 +02:00
"aws_cloudwatch_log_stream": resourceAwsCloudWatchLogStream(),
Add cloudwatch_logs_subscription_filter provider (#5996)
2016-04-20 21:05:21 +02:00
"aws_cloudwatch_log_subscription_filter": resourceAwsCloudwatchLogSubscriptionFilter(),
provider/aws: Add Elastic Beanstalk Application, Configuration Template, and Environment This adds support for Elastic Beanstalk Applications, Configuration Templates, and Environments. This is a combined work of @catsby, @dharrisio, @Bowbaq, and @jen20
2016-03-07 21:42:30 +01:00
"aws_autoscaling_lifecycle_hook": resourceAwsAutoscalingLifecycleHook(),
"aws_cloudwatch_metric_alarm": resourceAwsCloudWatchMetricAlarm(),
"aws_codedeploy_app": resourceAwsCodeDeployApp(),
"aws_codedeploy_deployment_group": resourceAwsCodeDeployDeploymentGroup(),
"aws_codecommit_repository": resourceAwsCodeCommitRepository(),
Added Codecommit Trigger
2016-09-08 10:54:54 +02:00
"aws_codecommit_trigger": resourceAwsCodeCommitTrigger(),
provider/aws: Add Elastic Beanstalk Application, Configuration Template, and Environment This adds support for Elastic Beanstalk Applications, Configuration Templates, and Environments. This is a combined work of @catsby, @dharrisio, @Bowbaq, and @jen20
2016-03-07 21:42:30 +01:00
"aws_customer_gateway": resourceAwsCustomerGateway(),
Added RDS event subscriptions (#6367)
2016-05-05 12:14:25 +02:00
"aws_db_event_subscription": resourceAwsDbEventSubscription(),
provider/aws: Add Elastic Beanstalk Application, Configuration Template, and Environment This adds support for Elastic Beanstalk Applications, Configuration Templates, and Environments. This is a combined work of @catsby, @dharrisio, @Bowbaq, and @jen20
2016-03-07 21:42:30 +01:00
"aws_db_instance": resourceAwsDbInstance(),
Scaffold the AWS DB Option Group resource Change the AWS DB Instance to now include the DB Option Group param. Adds a test to prove that it works Add acceptance tests for the AWS DB Option Group work. This ensures that Options can be added and updated Documentation for the AWS DB Option resource
2015-12-21 10:15:52 +01:00
"aws_db_option_group": resourceAwsDbOptionGroup(),
provider/aws: Add Elastic Beanstalk Application, Configuration Template, and Environment This adds support for Elastic Beanstalk Applications, Configuration Templates, and Environments. This is a combined work of @catsby, @dharrisio, @Bowbaq, and @jen20
2016-03-07 21:42:30 +01:00
"aws_db_parameter_group": resourceAwsDbParameterGroup(),
"aws_db_security_group": resourceAwsDbSecurityGroup(),
"aws_db_subnet_group": resourceAwsDbSubnetGroup(),
"aws_directory_service_directory": resourceAwsDirectoryServiceDirectory(),
"aws_dynamodb_table": resourceAwsDynamoDbTable(),
"aws_ebs_volume": resourceAwsEbsVolume(),
"aws_ecr_repository": resourceAwsEcrRepository(),
"aws_ecr_repository_policy": resourceAwsEcrRepositoryPolicy(),
"aws_ecs_cluster": resourceAwsEcsCluster(),
"aws_ecs_service": resourceAwsEcsService(),
"aws_ecs_task_definition": resourceAwsEcsTaskDefinition(),
"aws_efs_file_system": resourceAwsEfsFileSystem(),
"aws_efs_mount_target": resourceAwsEfsMountTarget(),
"aws_eip": resourceAwsEip(),
provider/aws: Change `aws_elastic_ip_association` to have computed parameters (#6552) * New top level AWS resource aws_eip_association * Add documentation for aws_eip_association * Add tests for aws_eip_association * provider/aws: Change `aws_elastic_ip_association` to have computed parameters The AWS API was send ing more parameters than we had set. Therefore, Terraform was showing constant changes when plans were being formed
2016-05-09 19:40:45 +02:00
"aws_eip_association": resourceAwsEipAssociation(),
provider/aws: Add Elastic Beanstalk Application, Configuration Template, and Environment This adds support for Elastic Beanstalk Applications, Configuration Templates, and Environments. This is a combined work of @catsby, @dharrisio, @Bowbaq, and @jen20
2016-03-07 21:42:30 +01:00
"aws_elasticache_cluster": resourceAwsElasticacheCluster(),
"aws_elasticache_parameter_group": resourceAwsElasticacheParameterGroup(),
provider/aws: Implement the `aws_elasticache_replication_group` resource (#8275)
2016-08-18 20:42:29 +02:00
"aws_elasticache_replication_group": resourceAwsElasticacheReplicationGroup(),
provider/aws: Add Elastic Beanstalk Application, Configuration Template, and Environment This adds support for Elastic Beanstalk Applications, Configuration Templates, and Environments. This is a combined work of @catsby, @dharrisio, @Bowbaq, and @jen20
2016-03-07 21:42:30 +01:00
"aws_elasticache_security_group": resourceAwsElasticacheSecurityGroup(),
"aws_elasticache_subnet_group": resourceAwsElasticacheSubnetGroup(),
"aws_elastic_beanstalk_application": resourceAwsElasticBeanstalkApplication(),
"aws_elastic_beanstalk_configuration_template": resourceAwsElasticBeanstalkConfigurationTemplate(),
"aws_elastic_beanstalk_environment": resourceAwsElasticBeanstalkEnvironment(),
"aws_elasticsearch_domain": resourceAwsElasticSearchDomain(),
Add support for Amazon Elastic Transcoder - Add resources for elastic transcoder pipelines and presets
2016-05-27 00:29:42 +02:00
"aws_elastictranscoder_pipeline": resourceAwsElasticTranscoderPipeline(),
"aws_elastictranscoder_preset": resourceAwsElasticTranscoderPreset(),
re-go-fmt after rebase use us-west-2 region in tests update test with working config provider/aws: Update EMR contribution with passing test, polling for instance in DELETE method remove defaulted role document emr_cluster rename aws_emr -> aws_emr_cluster update docs for name change update delete timeout/polling rename emr taskgroup to emr instance group default instance group count to 0, down from 60 update to ref emr_cluster, emr_instance_group more cleanups for instance groups; need to read and update add read, delete method for instance groups refactor the read method to seperate out the fetching of the specific group more refactoring for finding instance groups update emr instance group docs err check on reading HTTP. Dont' return the error, just log it refactor the create method to catch optionals additional cleanups, added a read method update test to be non-master-only wrap up the READ method for clusters poll for instance group to be running after a modification patch up a possible deref provider/aws: EMR cleanups fix test naming remove outdated docs randomize emr_profile names
2016-09-22 21:59:13 +02:00
"aws_elb": resourceAwsElb(),
"aws_elb_attachment": resourceAwsElbAttachment(),
"aws_emr_cluster": resourceAwsEMRCluster(),
"aws_emr_instance_group": resourceAwsEMRInstanceGroup(),
"aws_flow_log": resourceAwsFlowLog(),
"aws_glacier_vault": resourceAwsGlacierVault(),
"aws_iam_access_key": resourceAwsIamAccessKey(),
provider/aws: Add Elastic Beanstalk Application, Configuration Template, and Environment This adds support for Elastic Beanstalk Applications, Configuration Templates, and Environments. This is a combined work of @catsby, @dharrisio, @Bowbaq, and @jen20
2016-03-07 21:42:30 +01:00
"aws_iam_account_password_policy": resourceAwsIamAccountPasswordPolicy(),
"aws_iam_group_policy": resourceAwsIamGroupPolicy(),
"aws_iam_group": resourceAwsIamGroup(),
"aws_iam_group_membership": resourceAwsIamGroupMembership(),
provider/aws: Add per user, role and group policy attachment (supersedes #5816) (#6858) * Add per user, role and group policy attachment * Add docs for new IAM policy attachment resources. * Make policy attachment resources manage only 1 entity<->policy attachment * provider/aws: Tidy up IAM Group/User/Role attachments
2016-05-25 18:03:43 +02:00
"aws_iam_group_policy_attachment": resourceAwsIamGroupPolicyAttachment(),
provider/aws: Add Elastic Beanstalk Application, Configuration Template, and Environment This adds support for Elastic Beanstalk Applications, Configuration Templates, and Environments. This is a combined work of @catsby, @dharrisio, @Bowbaq, and @jen20
2016-03-07 21:42:30 +01:00
"aws_iam_instance_profile": resourceAwsIamInstanceProfile(),
"aws_iam_policy": resourceAwsIamPolicy(),
"aws_iam_policy_attachment": resourceAwsIamPolicyAttachment(),
provider/aws: Add per user, role and group policy attachment (supersedes #5816) (#6858) * Add per user, role and group policy attachment * Add docs for new IAM policy attachment resources. * Make policy attachment resources manage only 1 entity<->policy attachment * provider/aws: Tidy up IAM Group/User/Role attachments
2016-05-25 18:03:43 +02:00
"aws_iam_role_policy_attachment": resourceAwsIamRolePolicyAttachment(),
provider/aws: Add Elastic Beanstalk Application, Configuration Template, and Environment This adds support for Elastic Beanstalk Applications, Configuration Templates, and Environments. This is a combined work of @catsby, @dharrisio, @Bowbaq, and @jen20
2016-03-07 21:42:30 +01:00
"aws_iam_role_policy": resourceAwsIamRolePolicy(),
"aws_iam_role": resourceAwsIamRole(),
"aws_iam_saml_provider": resourceAwsIamSamlProvider(),
"aws_iam_server_certificate": resourceAwsIAMServerCertificate(),
provider/aws: Add per user, role and group policy attachment (supersedes #5816) (#6858) * Add per user, role and group policy attachment * Add docs for new IAM policy attachment resources. * Make policy attachment resources manage only 1 entity<->policy attachment * provider/aws: Tidy up IAM Group/User/Role attachments
2016-05-25 18:03:43 +02:00
"aws_iam_user_policy_attachment": resourceAwsIamUserPolicyAttachment(),
provider/aws: Add Elastic Beanstalk Application, Configuration Template, and Environment This adds support for Elastic Beanstalk Applications, Configuration Templates, and Environments. This is a combined work of @catsby, @dharrisio, @Bowbaq, and @jen20
2016-03-07 21:42:30 +01:00
"aws_iam_user_policy": resourceAwsIamUserPolicy(),
provider/aws: Scaffold `aws_iam_user_ssh_key` resource
2016-03-22 02:19:16 +01:00
"aws_iam_user_ssh_key": resourceAwsIamUserSshKey(),
provider/aws: Add Elastic Beanstalk Application, Configuration Template, and Environment This adds support for Elastic Beanstalk Applications, Configuration Templates, and Environments. This is a combined work of @catsby, @dharrisio, @Bowbaq, and @jen20
2016-03-07 21:42:30 +01:00
"aws_iam_user": resourceAwsIamUser(),
provider/aws: aws_iam_user_login_profile resource This commit introduces an `aws_iam_user_login_profile` resource which creates a password for an IAM user, and encrypts it using a PGP key specified in the configuration or obtained from Keybase. For example: ``` resource "aws_iam_user" "u" { name = "auser" path = "/" force_destroy = true } resource "aws_iam_user_login_profile" "u" { user = "${aws_iam_user.u.name}" pgp_key = "keybase:some_person_that_exists" } output "password" { value = "${aws_iam_user_login_profile.u.encrypted_password}" } ``` The resulting attribute "encrypted_password" can be decrypted using PGP or Keybase - for example: ``` terraform output password | base64 --decode | keybase pgp decrypt ``` Optionally the user can retain the password rather than the default of being forced to change it at first login. Generated passwords are currently 20 characters long.
2016-10-25 17:33:42 +02:00
"aws_iam_user_login_profile": resourceAwsIamUserLoginProfile(),
provider/aws: Add Elastic Beanstalk Application, Configuration Template, and Environment This adds support for Elastic Beanstalk Applications, Configuration Templates, and Environments. This is a combined work of @catsby, @dharrisio, @Bowbaq, and @jen20
2016-03-07 21:42:30 +01:00
"aws_instance": resourceAwsInstance(),
"aws_internet_gateway": resourceAwsInternetGateway(),
"aws_key_pair": resourceAwsKeyPair(),
"aws_kinesis_firehose_delivery_stream": resourceAwsKinesisFirehoseDeliveryStream(),
"aws_kinesis_stream": resourceAwsKinesisStream(),
Added AWS KMS key & alias support
2015-09-09 17:58:24 +02:00
"aws_kms_alias": resourceAwsKmsAlias(),
"aws_kms_key": resourceAwsKmsKey(),
provider/aws: Add Elastic Beanstalk Application, Configuration Template, and Environment This adds support for Elastic Beanstalk Applications, Configuration Templates, and Environments. This is a combined work of @catsby, @dharrisio, @Bowbaq, and @jen20
2016-03-07 21:42:30 +01:00
"aws_lambda_function": resourceAwsLambdaFunction(),
"aws_lambda_event_source_mapping": resourceAwsLambdaEventSourceMapping(),
"aws_lambda_alias": resourceAwsLambdaAlias(),
"aws_lambda_permission": resourceAwsLambdaPermission(),
"aws_launch_configuration": resourceAwsLaunchConfiguration(),
"aws_lb_cookie_stickiness_policy": resourceAwsLBCookieStickinessPolicy(),
rename aws load balancer policy resources team redundancy team had a good run, but is over now
2016-08-08 04:34:26 +02:00
"aws_load_balancer_policy": resourceAwsLoadBalancerPolicy(),
"aws_load_balancer_backend_server_policy": resourceAwsLoadBalancerBackendServerPolicies(),
"aws_load_balancer_listener_policy": resourceAwsLoadBalancerListenerPolicies(),
Add new resource aws_lb_ssl_negotiation_policy Added new resource to create an AWS ELB SSL negotiation policy, and an acceptance test.
2016-03-15 05:13:44 +01:00
"aws_lb_ssl_negotiation_policy": resourceAwsLBSSLNegotiationPolicy(),
provider/aws: Add Elastic Beanstalk Application, Configuration Template, and Environment This adds support for Elastic Beanstalk Applications, Configuration Templates, and Environments. This is a combined work of @catsby, @dharrisio, @Bowbaq, and @jen20
2016-03-07 21:42:30 +01:00
"aws_main_route_table_association": resourceAwsMainRouteTableAssociation(),
"aws_nat_gateway": resourceAwsNatGateway(),
"aws_network_acl": resourceAwsNetworkAcl(),
provider/aws: Default Network ACL resource (#6165) * provider/aws: Default Network ACL resource Provides a resource to manage the default AWS Network ACL. VPC Only. * Remove subnet_id update, mark as computed value. Remove extra tag update * refactor default rule number to be a constant * refactor revokeRulesForType to be revokeAllNetworkACLEntries Refactor method to delete all network ACL entries, regardless of type. The previous implementation was under the assumption that we may only eliminate some rule types and possibly not others, so the split was necessary. We're now removing them all, so the logic isn't necessary Several doc and test cleanups are here as well * smite subnet_id, improve docs
2016-04-18 18:02:00 +02:00
"aws_default_network_acl": resourceAwsDefaultNetworkAcl(),
provider/aws: Add aws_default_route_table resource (#8323) * provider/aws: Add docs for Default Route Table * add new default_route_table_id attribute, test to VPC * stub * add warning to docs * rough implementation * first test * update test, add swap test * fix typo
2016-08-25 23:02:44 +02:00
"aws_default_route_table": resourceAwsDefaultRouteTable(),
provider/aws: Add Elastic Beanstalk Application, Configuration Template, and Environment This adds support for Elastic Beanstalk Applications, Configuration Templates, and Environments. This is a combined work of @catsby, @dharrisio, @Bowbaq, and @jen20
2016-03-07 21:42:30 +01:00
"aws_network_acl_rule": resourceAwsNetworkAclRule(),
"aws_network_interface": resourceAwsNetworkInterface(),
Opsworks Application support
2015-12-22 17:45:27 +01:00
"aws_opsworks_application": resourceAwsOpsworksApplication(),
provider/aws: Add Elastic Beanstalk Application, Configuration Template, and Environment This adds support for Elastic Beanstalk Applications, Configuration Templates, and Environments. This is a combined work of @catsby, @dharrisio, @Bowbaq, and @jen20
2016-03-07 21:42:30 +01:00
"aws_opsworks_stack": resourceAwsOpsworksStack(),
"aws_opsworks_java_app_layer": resourceAwsOpsworksJavaAppLayer(),
"aws_opsworks_haproxy_layer": resourceAwsOpsworksHaproxyLayer(),
"aws_opsworks_static_web_layer": resourceAwsOpsworksStaticWebLayer(),
"aws_opsworks_php_app_layer": resourceAwsOpsworksPhpAppLayer(),
"aws_opsworks_rails_app_layer": resourceAwsOpsworksRailsAppLayer(),
"aws_opsworks_nodejs_app_layer": resourceAwsOpsworksNodejsAppLayer(),
"aws_opsworks_memcached_layer": resourceAwsOpsworksMemcachedLayer(),
"aws_opsworks_mysql_layer": resourceAwsOpsworksMysqlLayer(),
"aws_opsworks_ganglia_layer": resourceAwsOpsworksGangliaLayer(),
"aws_opsworks_custom_layer": resourceAwsOpsworksCustomLayer(),
Add support for Opsworks Instances New resource checklist - [x] Acceptance testing - [x] Documentation - [x] Well-formed code
2015-12-12 00:35:22 +01:00
"aws_opsworks_instance": resourceAwsOpsworksInstance(),
providers/aws: Opsworks permission resource (#6304) * add opsworks permission resource * add docs * remove permission from state if the permission object could not be found * remove nil validate function. validation is done in schema.Resource. * add id to the list of exported values * renge over permission to check that we have found got the correct one * removed comment * removed set id * fix unknown region us-east-1c * add user_profile resource * add docs * add default value
2016-07-21 01:29:33 +02:00
"aws_opsworks_user_profile": resourceAwsOpsworksUserProfile(),
"aws_opsworks_permission": resourceAwsOpsworksPermission(),
provider/aws: Add Elastic Beanstalk Application, Configuration Template, and Environment This adds support for Elastic Beanstalk Applications, Configuration Templates, and Environments. This is a combined work of @catsby, @dharrisio, @Bowbaq, and @jen20
2016-03-07 21:42:30 +01:00
"aws_placement_group": resourceAwsPlacementGroup(),
"aws_proxy_protocol_policy": resourceAwsProxyProtocolPolicy(),
"aws_rds_cluster": resourceAwsRDSCluster(),
"aws_rds_cluster_instance": resourceAwsRDSClusterInstance(),
add resource aws_rds_cluster_parameter_group
2016-02-23 11:52:07 +01:00
"aws_rds_cluster_parameter_group": resourceAwsRDSClusterParameterGroup(),
provider/aws: Add Elastic Beanstalk Application, Configuration Template, and Environment This adds support for Elastic Beanstalk Applications, Configuration Templates, and Environments. This is a combined work of @catsby, @dharrisio, @Bowbaq, and @jen20
2016-03-07 21:42:30 +01:00
"aws_redshift_cluster": resourceAwsRedshiftCluster(),
"aws_redshift_security_group": resourceAwsRedshiftSecurityGroup(),
"aws_redshift_parameter_group": resourceAwsRedshiftParameterGroup(),
"aws_redshift_subnet_group": resourceAwsRedshiftSubnetGroup(),
"aws_route53_delegation_set": resourceAwsRoute53DelegationSet(),
"aws_route53_record": resourceAwsRoute53Record(),
"aws_route53_zone_association": resourceAwsRoute53ZoneAssociation(),
"aws_route53_zone": resourceAwsRoute53Zone(),
"aws_route53_health_check": resourceAwsRoute53HealthCheck(),
"aws_route": resourceAwsRoute(),
"aws_route_table": resourceAwsRouteTable(),
"aws_route_table_association": resourceAwsRouteTableAssociation(),
Add SES resource (#5387) * Add SES resource * Detect ReceiptRule deletion outside of Terraform * Handle order of rule actions * Add position field to docs * Fix hashes, add log messages, and other small cleanup * Fix rebase issue * Fix formatting
2016-06-26 23:07:14 +02:00
"aws_ses_active_receipt_rule_set": resourceAwsSesActiveReceiptRuleSet(),
"aws_ses_receipt_filter": resourceAwsSesReceiptFilter(),
"aws_ses_receipt_rule": resourceAwsSesReceiptRule(),
"aws_ses_receipt_rule_set": resourceAwsSesReceiptRuleSet(),
provider/aws: Add Elastic Beanstalk Application, Configuration Template, and Environment This adds support for Elastic Beanstalk Applications, Configuration Templates, and Environments. This is a combined work of @catsby, @dharrisio, @Bowbaq, and @jen20
2016-03-07 21:42:30 +01:00
"aws_s3_bucket": resourceAwsS3Bucket(),
provider/aws: Add aws_s3_bucket_policy resource This commit adds a new "attachment" style resource for setting the policy of an AWS S3 bucket. This is desirable such that the ARN of the bucket can be referenced in an IAM Policy Document. In addition, we now suppress diffs on the (now-computed) policy in the S3 bucket for structurally equivalent policies, which prevents flapping because of whitespace and map ordering changes made by the S3 endpoint.
2016-09-02 00:34:45 +02:00
"aws_s3_bucket_policy": resourceAwsS3BucketPolicy(),
provider/aws: Add Elastic Beanstalk Application, Configuration Template, and Environment This adds support for Elastic Beanstalk Applications, Configuration Templates, and Environments. This is a combined work of @catsby, @dharrisio, @Bowbaq, and @jen20
2016-03-07 21:42:30 +01:00
"aws_s3_bucket_object": resourceAwsS3BucketObject(),
provider/aws: Support S3 bucket notification * Implement aws_s3_bucket_notification resource
2016-04-05 04:23:06 +02:00
"aws_s3_bucket_notification": resourceAwsS3BucketNotification(),
provider/aws: Add Default Security Group Resource (#8861) * Docs for default security group * overrides of default behavior * add special disclaimer * update to support classic environments
2016-09-15 20:59:20 +02:00
"aws_default_security_group": resourceAwsDefaultSecurityGroup(),
provider/aws: Add Elastic Beanstalk Application, Configuration Template, and Environment This adds support for Elastic Beanstalk Applications, Configuration Templates, and Environments. This is a combined work of @catsby, @dharrisio, @Bowbaq, and @jen20
2016-03-07 21:42:30 +01:00
"aws_security_group": resourceAwsSecurityGroup(),
"aws_security_group_rule": resourceAwsSecurityGroupRule(),
SimpleDB domain resource (#7600)
2016-07-12 13:55:58 +02:00
"aws_simpledb_domain": resourceAwsSimpleDBDomain(),
New AWS resource `ssm_activation` (#9111) Adding a new resource to support activation of managed instances for on-premise virtual-machines.
2016-10-28 11:59:12 +02:00
"aws_ssm_activation": resourceAwsSsmActivation(),
provider/aws: add aws_ssm_association resource
2016-09-02 09:43:03 +02:00
"aws_ssm_association": resourceAwsSsmAssociation(),
provider/aws: Adding `aws_ssm_document` resource (#8460) * provider/aws: add `aws_ssm_document` resource * provider/aws: Changes to `aws_ssm_document` post code review The changes are things like using d.Id rather than d.Get("name").(string) and errwrap.Wrapf rather than fmt.Errorf
2016-08-25 10:47:24 +02:00
"aws_ssm_document": resourceAwsSsmDocument(),
provider/aws: New resource `aws_spot_datafeed_subscription` Fixes: #4922 ``` % make testacc TEST=./builtin/providers/aws TESTARGS='-run=TestAccAWSSpotDatafeedSubscription_' ==> Checking that code complies with gofmt requirements... /Users/stacko/Code/go/bin/stringer go generate $(go list ./... | grep -v /terraform/vendor/) 2016/08/24 10:46:23 Generated command/internal_plugin_list.go TF_ACC=1 go test ./builtin/providers/aws -v -run=TestAccAWSSpotDatafeedSubscription_ -timeout 120m === RUN TestAccAWSSpotDatafeedSubscription_importBasic --- PASS: TestAccAWSSpotDatafeedSubscription_importBasic (56.31s) === RUN TestAccAWSSpotDatafeedSubscription_basic --- PASS: TestAccAWSSpotDatafeedSubscription_basic (56.77s) === RUN TestAccAWSSpotDatafeedSubscription_disappears --- PASS: TestAccAWSSpotDatafeedSubscription_disappears (56.79s) PASS ok github.com/hashicorp/terraform/builtin/providers/aws 169.893s ```
2016-08-24 11:51:57 +02:00
"aws_spot_datafeed_subscription": resourceAwsSpotDataFeedSubscription(),
provider/aws: Add Elastic Beanstalk Application, Configuration Template, and Environment This adds support for Elastic Beanstalk Applications, Configuration Templates, and Environments. This is a combined work of @catsby, @dharrisio, @Bowbaq, and @jen20
2016-03-07 21:42:30 +01:00
"aws_spot_instance_request": resourceAwsSpotInstanceRequest(),
Add an AWS Spot fleet resource
2016-06-22 02:16:02 +02:00
"aws_spot_fleet_request": resourceAwsSpotFleetRequest(),
provider/aws: Add Elastic Beanstalk Application, Configuration Template, and Environment This adds support for Elastic Beanstalk Applications, Configuration Templates, and Environments. This is a combined work of @catsby, @dharrisio, @Bowbaq, and @jen20
2016-03-07 21:42:30 +01:00
"aws_sqs_queue": resourceAwsSqsQueue(),
provider/aws: Add aws_sqs_queue_policy
2016-09-05 08:45:04 +02:00
"aws_sqs_queue_policy": resourceAwsSqsQueuePolicy(),
provider/aws: Add Elastic Beanstalk Application, Configuration Template, and Environment This adds support for Elastic Beanstalk Applications, Configuration Templates, and Environments. This is a combined work of @catsby, @dharrisio, @Bowbaq, and @jen20
2016-03-07 21:42:30 +01:00
"aws_sns_topic": resourceAwsSnsTopic(),
provider/aws: Add aws_sns_topic_policy
2016-09-04 09:30:10 +02:00
"aws_sns_topic_policy": resourceAwsSnsTopicPolicy(),
provider/aws: Add Elastic Beanstalk Application, Configuration Template, and Environment This adds support for Elastic Beanstalk Applications, Configuration Templates, and Environments. This is a combined work of @catsby, @dharrisio, @Bowbaq, and @jen20
2016-03-07 21:42:30 +01:00
"aws_sns_topic_subscription": resourceAwsSnsTopicSubscription(),
"aws_subnet": resourceAwsSubnet(),
"aws_volume_attachment": resourceAwsVolumeAttachment(),
"aws_vpc_dhcp_options_association": resourceAwsVpcDhcpOptionsAssociation(),
"aws_vpc_dhcp_options": resourceAwsVpcDhcpOptions(),
"aws_vpc_peering_connection": resourceAwsVpcPeeringConnection(),
"aws_vpc": resourceAwsVpc(),
"aws_vpc_endpoint": resourceAwsVpcEndpoint(),
"aws_vpn_connection": resourceAwsVpnConnection(),
"aws_vpn_connection_route": resourceAwsVpnConnectionRoute(),
"aws_vpn_gateway": resourceAwsVpnGateway(),
Add aws_vpn_gateway_attachment resource. (#7870) This commit adds VPN Gateway attachment resource, and also an initial tests and documentation stubs. Signed-off-by: Krzysztof Wilczynski <krzysztof.wilczynski@linux.com>
2016-08-07 01:29:51 +02:00
"aws_vpn_gateway_attachment": resourceAwsVpnGatewayAttachment(),
Added AWS Resource WAF ByteMatchSet (#9681)
2016-10-28 14:36:16 +02:00
"aws_waf_byte_match_set": resourceAwsWafByteMatchSet(),
Added WAF ACL Resource (#8852)
2016-10-27 13:54:36 +02:00
"aws_waf_ipset": resourceAwsWafIPSet(),
Added AWS Resource WAF SizeConstraintSet (#9689)
2016-10-29 00:58:37 +02:00
"aws_waf_rule": resourceAwsWafRule(),
"aws_waf_size_constraint_set": resourceAwsWafSizeConstraintSet(),
"aws_waf_web_acl": resourceAwsWafWebAcl(),
Added AWS Resource WAF XssMatchSet (#9710)
2016-10-31 09:51:08 +01:00
"aws_waf_xss_match_set": resourceAwsWafXssMatchSet(),
providers/aws: resource_aws_eip is in new framework
2014-08-20 01:56:23 +02:00
},
Refactored about 90% Still need to update 2 resources and check the acceptance tests, but overall we’re nearly there :smiley:
2014-11-21 17:58:34 +01:00
ConfigureFunc: providerConfigure,
providers/aws: proper DefaultFunc to return nil if no env
2014-09-10 06:46:50 +02:00
}
}
Add descriptions for AWS inputs
2014-09-29 22:30:28 +02:00
var descriptions map[string]string
func init() {
descriptions = map[string]string{
"region": "The region where AWS operations will take place. Examples\n" +
"are us-east-1, us-west-2, etc.",
"access_key": "The access key for API operations. You can retrieve this\n" +
"from the 'Security & Credentials' section of the AWS console.",
"secret_key": "The secret key for API operations. You can retrieve this\n" +
"from the 'Security & Credentials' section of the AWS console.",
Support session token in AWS credentials Session tokens are necessary to utilize temporary credentials. http://docs.aws.amazon.com/STS/latest/UsingSTS/Welcome.html
2015-04-20 20:26:59 +02:00
provider/aws: Add profile to provider config This allows specification of the profile for the shared credentials provider for AWS to be specified in Terraform configuration. This is useful if defining providers with aliases, or if you don't want to set environment variables. Example: $ aws configure --profile this_is_dog ... enter keys $ cat main.tf provider "aws" { profile = "this_is_dog" # Optionally also specify the path to the credentials file shared_credentials_file = "/tmp/credentials" } This is equivalent to specifying AWS_PROFILE or AWS_SHARED_CREDENTIALS_FILE in the environment.
2016-01-11 16:22:09 +01:00
"profile": "The profile for API operations. If not set, the default profile\n" +
"created with `aws configure` will be used.",
"shared_credentials_file": "The path to the shared credentials file. If not set\n" +
"this defaults to ~/.aws/credentials.",
Support session token in AWS credentials Session tokens are necessary to utilize temporary credentials. http://docs.aws.amazon.com/STS/latest/UsingSTS/Welcome.html
2015-04-20 20:26:59 +02:00
"token": "session token. A session token is only required if you are\n" +
"using temporary security credentials.",
aws: make MaxRetries for API calls configurable - Make it configurable in the AWS provider by add an option 'max_retries'. - Set the default from 3 to 11 retries.
2015-05-03 11:08:47 +02:00
"max_retries": "The maximum number of times an AWS API request is\n" +
"being executed. If the API request still fails, an error is\n" +
"thrown.",
dynamodb-local Add `dynamodb_endpoint` allowing to change the DynamoDB Endpoint for example to connect to dynamodb-local
2015-07-22 23:57:29 +02:00
dynamodb-local Use ` instead of : to refer region to keep the consistency with the provider docs
2015-07-29 18:36:02 +02:00
"dynamodb_endpoint": "Use this to override the default endpoint URL constructed from the `region`.\n" +
dynamodb-local Add `dynamodb_endpoint` allowing to change the DynamoDB Endpoint for example to connect to dynamodb-local
2015-07-22 23:57:29 +02:00
"It's typically used to connect to dynamodb-local.",
provider/aws: allow local kinesis
2015-09-16 18:58:46 +02:00
"kinesis_endpoint": "Use this to override the default endpoint URL constructed from the `region`.\n" +
"It's typically used to connect to kinesalite.",
support custom endpoints for AWS EC2 ELB and IAM
2015-12-11 16:27:49 +01:00
Move endpoint options into endpoints block
2016-02-07 22:40:51 +01:00
"iam_endpoint": "Use this to override the default endpoint URL constructed from the `region`.\n",
support custom endpoints for AWS EC2 ELB and IAM
2015-12-11 16:27:49 +01:00
Move endpoint options into endpoints block
2016-02-07 22:40:51 +01:00
"ec2_endpoint": "Use this to override the default endpoint URL constructed from the `region`.\n",
support custom endpoints for AWS EC2 ELB and IAM
2015-12-11 16:27:49 +01:00
Move endpoint options into endpoints block
2016-02-07 22:40:51 +01:00
"elb_endpoint": "Use this to override the default endpoint URL constructed from the `region`.\n",
support custom endpoints for AWS EC2 ELB and IAM
2015-12-11 16:27:49 +01:00
Add S3 endpoint override ability and expose S3 path style option (#7871) * Overriding S3 endpoint - Enable specifying your own S3 api endpoint to override the default one, under endpoints. * Force S3 path style - Expose this option from the aws-sdk-go configuration to the provider.
2016-08-12 18:52:12 +02:00
"s3_endpoint": "Use this to override the default endpoint URL constructed from the `region`.\n",
Move endpoint options into endpoints block
2016-02-07 22:40:51 +01:00
"insecure": "Explicitly allow the provider to perform \"insecure\" SSL requests. If omitted," +
"default value is `false`",
Skip IAM/STS validation and metadata check (#7874) * Skip IAM/STS validation and metadata check * Skip IAM/STS identity validation - For environments or other api implementations where there are no IAM/STS endpoints available, this option lets you opt out from that provider initialization step. * Skip metdata api check - For environments in which you know ahead of time there isn't going to be a metadta api endpoint, this option lets you opt out from that check to save time. * Allow iam/sts initialization even if skipping account/cred validation (#7874) * Split out skip of IAM validation into credentials and account id (#7874)
2016-08-10 16:10:34 +02:00
aws: Change field names + desc according to reality - skip_iam_creds_validation => skip_credentials_validation - skip_iam_account_id => skip_requesting_account_id
2016-08-10 17:46:02 +02:00
"skip_credentials_validation": "Skip the credentials validation via STS API. " +
"Used for AWS API implementations that do not have STS available/implemented.",
Skip IAM/STS validation and metadata check (#7874) * Skip IAM/STS validation and metadata check * Skip IAM/STS identity validation - For environments or other api implementations where there are no IAM/STS endpoints available, this option lets you opt out from that provider initialization step. * Skip metdata api check - For environments in which you know ahead of time there isn't going to be a metadta api endpoint, this option lets you opt out from that check to save time. * Allow iam/sts initialization even if skipping account/cred validation (#7874) * Split out skip of IAM validation into credentials and account id (#7874)
2016-08-10 16:10:34 +02:00
aws: Change field names + desc according to reality - skip_iam_creds_validation => skip_credentials_validation - skip_iam_account_id => skip_requesting_account_id
2016-08-10 17:46:02 +02:00
"skip_requesting_account_id": "Skip requesting the account ID. " +
"Used for AWS API implementations that do not have IAM/STS API and/or metadata API.",
Skip IAM/STS validation and metadata check (#7874) * Skip IAM/STS validation and metadata check * Skip IAM/STS identity validation - For environments or other api implementations where there are no IAM/STS endpoints available, this option lets you opt out from that provider initialization step. * Skip metdata api check - For environments in which you know ahead of time there isn't going to be a metadta api endpoint, this option lets you opt out from that check to save time. * Allow iam/sts initialization even if skipping account/cred validation (#7874) * Split out skip of IAM validation into credentials and account id (#7874)
2016-08-10 16:10:34 +02:00
"skip_medatadata_api_check": "Skip the AWS Metadata API check. " +
"Used for AWS API implementations that do not have a metadata api endpoint.",
Add S3 endpoint override ability and expose S3 path style option (#7871) * Overriding S3 endpoint - Enable specifying your own S3 api endpoint to override the default one, under endpoints. * Force S3 path style - Expose this option from the aws-sdk-go configuration to the provider.
2016-08-12 18:52:12 +02:00
"s3_force_path_style": "Set this to true to force the request to use path-style addressing,\n" +
"i.e., http://s3.amazonaws.com/BUCKET/KEY. By default, the S3 client will\n" +
"use virtual hosted bucket addressing when possible\n" +
"(http://BUCKET.s3.amazonaws.com/KEY). Specific to the Amazon S3 service.",
provider/aws: Add assume_role block to provider This replaces the previous `role_arn` with a block which looks like this: ``` provider "aws" { // secret key, access key etc assume_role { role_arn = "<Role ARN>" session_name = "<Session Name>" external_id = "<External ID>" } } ``` We also modify the configuration structure and read the values from the block if present into those values and adjust the call to AssumeRole to include the SessionName and ExternalID based on the values set in the configuration block. Finally we clean up the tests and add in missing error checks, and clean up the error handling logic in the Auth helper functions.
2016-09-02 19:36:01 +02:00
"assume_role_role_arn": "The ARN of an IAM role to assume prior to making API calls.",
provider/aws: Fix misspelled words
2016-09-12 08:14:24 +02:00
"assume_role_session_name": "The session name to use when assuming the role. If omitted," +
provider/aws: Add assume_role block to provider This replaces the previous `role_arn` with a block which looks like this: ``` provider "aws" { // secret key, access key etc assume_role { role_arn = "<Role ARN>" session_name = "<Session Name>" external_id = "<External ID>" } } ``` We also modify the configuration structure and read the values from the block if present into those values and adjust the call to AssumeRole to include the SessionName and ExternalID based on the values set in the configuration block. Finally we clean up the tests and add in missing error checks, and clean up the error handling logic in the Auth helper functions.
2016-09-02 19:36:01 +02:00
" no session name is passed to the AssumeRole call.",
provider/aws: Fix misspelled words
2016-09-12 08:14:24 +02:00
"assume_role_external_id": "The external ID to use when assuming the role. If omitted," +
provider/aws: Add assume_role block to provider This replaces the previous `role_arn` with a block which looks like this: ``` provider "aws" { // secret key, access key etc assume_role { role_arn = "<Role ARN>" session_name = "<Session Name>" external_id = "<External ID>" } } ``` We also modify the configuration structure and read the values from the block if present into those values and adjust the call to AssumeRole to include the SessionName and ExternalID based on the values set in the configuration block. Finally we clean up the tests and add in missing error checks, and clean up the error handling logic in the Auth helper functions.
2016-09-02 19:36:01 +02:00
" no external ID is passed to the AssumeRole call.",
Add descriptions for AWS inputs
2014-09-29 22:30:28 +02:00
}
}
Refactored about 90% Still need to update 2 resources and check the acceptance tests, but overall we’re nearly there :smiley:
2014-11-21 17:58:34 +01:00
func providerConfigure(d *schema.ResourceData) (interface{}, error) {
config := Config{
aws: Change field names + desc according to reality - skip_iam_creds_validation => skip_credentials_validation - skip_iam_account_id => skip_requesting_account_id
2016-08-10 17:46:02 +02:00
AccessKey: d.Get("access_key").(string),
SecretKey: d.Get("secret_key").(string),
Profile: d.Get("profile").(string),
CredsFilename: d.Get("shared_credentials_file").(string),
Token: d.Get("token").(string),
Region: d.Get("region").(string),
MaxRetries: d.Get("max_retries").(int),
DynamoDBEndpoint: d.Get("dynamodb_endpoint").(string),
KinesisEndpoint: d.Get("kinesis_endpoint").(string),
Insecure: d.Get("insecure").(bool),
SkipCredsValidation: d.Get("skip_credentials_validation").(bool),
SkipRequestingAccountId: d.Get("skip_requesting_account_id").(bool),
SkipMetadataApiCheck: d.Get("skip_metadata_api_check").(bool),
Add S3 endpoint override ability and expose S3 path style option (#7871) * Overriding S3 endpoint - Enable specifying your own S3 api endpoint to override the default one, under endpoints. * Force S3 path style - Expose this option from the aws-sdk-go configuration to the provider.
2016-08-12 18:52:12 +02:00
S3ForcePathStyle: d.Get("s3_force_path_style").(bool),
Move endpoint options into endpoints block
2016-02-07 22:40:51 +01:00
}
provider/aws: Add assume_role block to provider This replaces the previous `role_arn` with a block which looks like this: ``` provider "aws" { // secret key, access key etc assume_role { role_arn = "<Role ARN>" session_name = "<Session Name>" external_id = "<External ID>" } } ``` We also modify the configuration structure and read the values from the block if present into those values and adjust the call to AssumeRole to include the SessionName and ExternalID based on the values set in the configuration block. Finally we clean up the tests and add in missing error checks, and clean up the error handling logic in the Auth helper functions.
2016-09-02 19:36:01 +02:00
assumeRoleList := d.Get("assume_role").(*schema.Set).List()
if len(assumeRoleList) == 1 {
assumeRole := assumeRoleList[0].(map[string]interface{})
config.AssumeRoleARN = assumeRole["role_arn"].(string)
config.AssumeRoleSessionName = assumeRole["session_name"].(string)
config.AssumeRoleExternalID = assumeRole["external_id"].(string)
log.Printf("[INFO] assume_role configuration set: (ARN: %q, SessionID: %q, ExternalID: %q)",
config.AssumeRoleARN, config.AssumeRoleSessionName, config.AssumeRoleExternalID)
} else {
log.Printf("[INFO] No assume_role block read from configuration")
}
Move endpoint options into endpoints block
2016-02-07 22:40:51 +01:00
endpointsSet := d.Get("endpoints").(*schema.Set)
for _, endpointsSetI := range endpointsSet.List() {
endpoints := endpointsSetI.(map[string]interface{})
config.IamEndpoint = endpoints["iam"].(string)
config.Ec2Endpoint = endpoints["ec2"].(string)
config.ElbEndpoint = endpoints["elb"].(string)
Add S3 endpoint override ability and expose S3 path style option (#7871) * Overriding S3 endpoint - Enable specifying your own S3 api endpoint to override the default one, under endpoints. * Force S3 path style - Expose this option from the aws-sdk-go configuration to the provider.
2016-08-12 18:52:12 +02:00
config.S3Endpoint = endpoints["s3"].(string)
Refactored about 90% Still need to update 2 resources and check the acceptance tests, but overall we’re nearly there :smiley:
2014-11-21 17:58:34 +01:00
}
AWS account ID protection added
2015-04-20 00:54:42 +02:00
if v, ok := d.GetOk("allowed_account_ids"); ok {
config.AllowedAccountIds = v.(*schema.Set).List()
}
if v, ok := d.GetOk("forbidden_account_ids"); ok {
config.ForbiddenAccountIds = v.(*schema.Set).List()
}
Refactored about 90% Still need to update 2 resources and check the acceptance tests, but overall we’re nearly there :smiley:
2014-11-21 17:58:34 +01:00
return config.Client()
}
provider/aws: serialize SG rule access to fix race condition Because `aws_security_group_rule` resources are an abstraction on top of Security Groups, they must interact with the AWS Security Group APIs in a pattern that often results in lots of parallel requests interacting with the same security group. We've found that this pattern can trigger race conditions resulting in inconsistent behavior, including: * Rules that report as created but don't actually exist on AWS's side * Rules that show up in AWS but don't register as being created locally, resulting in follow up attempts to authorize the rule failing w/ Duplicate errors Here, we introduce a per-SG mutex that must be held by any security group before it is allowed to interact with AWS APIs. This protects the space between `DescribeSecurityGroup` and `Authorize*` / `Revoke*` calls, ensuring that no other rules interact with the SG during that span. The included test exposes the race by applying a security group with lots of rules, which based on the dependency graph can all be handled in parallel. This fails most of the time without the new locking behavior. I've omitted the mutex from `Read`, since it is only called during the Refresh walk when no changes are being made, meaning a bunch of parallel `DescribeSecurityGroup` API calls should be consistent in that case.
2015-08-24 15:59:54 +02:00
// This is a global MutexKV for use within this plugin.
var awsMutexKV = mutexkv.NewMutexKV()
Move endpoint options into endpoints block
2016-02-07 22:40:51 +01:00
provider/aws: Add assume_role block to provider This replaces the previous `role_arn` with a block which looks like this: ``` provider "aws" { // secret key, access key etc assume_role { role_arn = "<Role ARN>" session_name = "<Session Name>" external_id = "<External ID>" } } ``` We also modify the configuration structure and read the values from the block if present into those values and adjust the call to AssumeRole to include the SessionName and ExternalID based on the values set in the configuration block. Finally we clean up the tests and add in missing error checks, and clean up the error handling logic in the Auth helper functions.
2016-09-02 19:36:01 +02:00
func assumeRoleSchema() *schema.Schema {
return &schema.Schema{
Type: schema.TypeSet,
Optional: true,
MaxItems: 1,
Elem: &schema.Resource{
Schema: map[string]*schema.Schema{
"role_arn": {
Type: schema.TypeString,
Optional: true,
Description: descriptions["assume_role_role_arn"],
},
"session_name": {
Type: schema.TypeString,
Optional: true,
Description: descriptions["assume_role_session_name"],
},
"external_id": {
Type: schema.TypeString,
Optional: true,
Description: descriptions["assume_role_external_id"],
},
},
},
Set: assumeRoleToHash,
}
}
func assumeRoleToHash(v interface{}) int {
var buf bytes.Buffer
m := v.(map[string]interface{})
buf.WriteString(fmt.Sprintf("%s-", m["role_arn"].(string)))
buf.WriteString(fmt.Sprintf("%s-", m["session_name"].(string)))
buf.WriteString(fmt.Sprintf("%s-", m["external_id"].(string)))
return hashcode.String(buf.String())
}
Move endpoint options into endpoints block
2016-02-07 22:40:51 +01:00
func endpointsSchema() *schema.Schema {
return &schema.Schema{
Type: schema.TypeSet,
Optional: true,
Elem: &schema.Resource{
Schema: map[string]*schema.Schema{
provider/aws: Clean up AWS provider schema defns Remove unnecessary &schema.Schema from the AWS provider schema definition.
2016-09-02 19:29:59 +02:00
"iam": {
Move endpoint options into endpoints block
2016-02-07 22:40:51 +01:00
Type: schema.TypeString,
Optional: true,
Default: "",
Description: descriptions["iam_endpoint"],
},
provider/aws: Clean up AWS provider schema defns Remove unnecessary &schema.Schema from the AWS provider schema definition.
2016-09-02 19:29:59 +02:00
"ec2": {
Move endpoint options into endpoints block
2016-02-07 22:40:51 +01:00
Type: schema.TypeString,
Optional: true,
Default: "",
Description: descriptions["ec2_endpoint"],
},
provider/aws: Clean up AWS provider schema defns Remove unnecessary &schema.Schema from the AWS provider schema definition.
2016-09-02 19:29:59 +02:00
"elb": {
Move endpoint options into endpoints block
2016-02-07 22:40:51 +01:00
Type: schema.TypeString,
Optional: true,
Default: "",
Description: descriptions["elb_endpoint"],
},
provider/aws: Clean up AWS provider schema defns Remove unnecessary &schema.Schema from the AWS provider schema definition.
2016-09-02 19:29:59 +02:00
"s3": {
Add S3 endpoint override ability and expose S3 path style option (#7871) * Overriding S3 endpoint - Enable specifying your own S3 api endpoint to override the default one, under endpoints. * Force S3 path style - Expose this option from the aws-sdk-go configuration to the provider.
2016-08-12 18:52:12 +02:00
Type: schema.TypeString,
Optional: true,
Default: "",
Description: descriptions["s3_endpoint"],
},
Move endpoint options into endpoints block
2016-02-07 22:40:51 +01:00
},
},
Set: endpointsToHash,
}
}
func endpointsToHash(v interface{}) int {
var buf bytes.Buffer
m := v.(map[string]interface{})
buf.WriteString(fmt.Sprintf("%s-", m["iam"].(string)))
buf.WriteString(fmt.Sprintf("%s-", m["ec2"].(string)))
buf.WriteString(fmt.Sprintf("%s-", m["elb"].(string)))
Add S3 endpoint override ability and expose S3 path style option (#7871) * Overriding S3 endpoint - Enable specifying your own S3 api endpoint to override the default one, under endpoints. * Force S3 path style - Expose this option from the aws-sdk-go configuration to the provider.
2016-08-12 18:52:12 +02:00
buf.WriteString(fmt.Sprintf("%s-", m["s3"].(string)))
Move endpoint options into endpoints block
2016-02-07 22:40:51 +01:00
return hashcode.String(buf.String())
}