Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

merge #5

Merged
merged 24 commits into from
Oct 26, 2019
Merged

merge #5

merged 24 commits into from
Oct 26, 2019

Conversation

DrFaust92
Copy link
Owner

Community Note

  • Please vote on this pull request by adding a 👍 reaction to the original pull request comment to help the community and maintainers prioritize this request
  • Please do not leave "+1" comments, they generate extra noise for pull request followers and do not help prioritize the request

Relates OR Closes #0000

Release note for CHANGELOG:


Output from acceptance testing:

$ make testacc TESTARGS='-run=TestAccXXX'

...

mudlark and others added 24 commits August 12, 2019 17:17
Reference: #9871

Output from acceptance testing:

```
--- PASS: TestAccAWSCloudHsm2Cluster_Tags (281.94s)
--- PASS: TestAccAWSCloudHsm2Cluster_basic (286.25s)
```
Includes information how to work with the new `internal/keyvaluetags` generators.
…o use keyvaluetags library

Reference: #7052
Reference: #7926

Output from acceptance testing:

```
--- PASS: TestAccAWSLicenseManagerLicenseConfiguration_basic (12.91s)
--- PASS: TestAccAWSLicenseManagerLicenseConfiguration_update (20.57s)
```
Reference: #7926

Output from acceptance testing:

```
--- PASS: TestAccAWSEcrDataSource_ecrImage (13.77s)
--- PASS: TestAccAWSEcrRepository_basic (14.42s)
--- PASS: TestAccAWSEcrRepository_immutability (14.53s)
--- PASS: TestAccAWSEcrDataSource_ecrRepository (16.21s)
--- PASS: TestAccAWSEcrRepository_tags (20.90s)
```
… show tagging on creation versus not, fix typo

Reference: #10313
Reference: #7926

In preparation for provider-wide ignore and default tag logic, here we refactor this resource to use the consistent `keyvaluetags` handling.

Output from acceptance testing:

```
--- PASS: TestAccDataSourceAwsVpc_basic (27.54s)
--- PASS: TestAccDataSourceAwsVpc_ipv6Associated (27.56s)
--- PASS: TestAccDataSourceAwsVpc_multipleCidr (51.12s)
```
This makes things consistent with
#10401
and the AWS documentation.
Examples refer to aws_ses_identity_policy.test. However, the actual
resource is called aws_ses_identity_policy.example.
…ad after Create (#10411)

Reference: #7926
Similar in nature to: #10315

In preparation for provider-wide ignore and default tag logic, here we refactor this resource to use the consistent `keyvaluetags` handling. The previous `setTags()` logic was always performing retries only necessary for resource creation and the resource itself was not following recommended practices to call the Read function after Create.

Ouput from acceptance testing:

```
--- PASS: TestAccAWSSubnet_availabilityZoneId (25.22s)
--- PASS: TestAccAWSSubnet_basic (25.66s)
--- PASS: TestAccAWSSubnet_enableIpv6 (41.83s)
--- PASS: TestAccAWSSubnet_ipv6 (66.62s)
```
Reference: #7926

In preparation for provider-wide ignore and default tag logic, here we refactor this resource to use the consistent `keyvaluetags` handling.

Output from acceptance testing:

```
--- PASS: TestAccDataSourceAwsSubnet_basic (28.82s)
--- PASS: TestAccDataSourceAwsSubnet_ipv6ByIpv6CidrBlock (46.06s)
--- PASS: TestAccDataSourceAwsSubnet_ipv6ByIpv6Filter (46.30s)
```
Reference: #7926

In preparation for provider-wide ignore and default tag logic, here we refactor this resource to use the consistent `keyvaluetags` handling.

Output from acceptance testing:

```
--- PASS: TestAccDataSourceAwsVpc_basic (27.54s)
--- PASS: TestAccDataSourceAwsVpc_ipv6Associated (27.56s)
--- PASS: TestAccDataSourceAwsVpc_multipleCidr (51.12s)
```
docs/provider: Add Adding Resource Tagging Support section
…m-hashicorp-terraform-plugin-sdk-1.x

Update module hashicorp/terraform-plugin-sdk to v1.2.0
@DrFaust92 DrFaust92 merged commit c0f6d5e into DrFaust92:master Oct 26, 2019
@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 10, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants