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

provider/aws: Change Route 53 record to allow resource updates #1396

Merged
merged 2 commits into from
Apr 8, 2015

Conversation

catsby
Copy link
Contributor

@catsby catsby commented Apr 6, 2015

This removes ForceNew from records and ttl, and introduces a
resourceAwsRoute53RecordUpdate function. The resourceAwsRoute53RecordUpdate
falls through to the resourceAwsRoute53RecordCreate function, which utilizes
AWS UPSERT behavior and diffs for us.

Name and Type are used by AWS in the UPSERT, so only records with matching
name and type can be updated. Others are created as new, so we leave the
ForceNew behavior here.

This removes `ForceNew` from `records` and `ttl`, and introduces a
`resourceAwsRoute53RecordUpdate` function. The `resourceAwsRoute53RecordUpdate`
falls through to the `resourceAwsRoute53RecordCreate` function, which utilizes
AWS `UPSERT` behavior and diffs for us.

`Name` and `Type` are used by AWS in the `UPSERT`, so only records with matching
`name` and `type` can be updated. Others are created as new, so we leave the
`ForceNew` behavior here.
@catsby
Copy link
Contributor Author

catsby commented Apr 6, 2015

This should address #1122

@phinze
Copy link
Contributor

phinze commented Apr 6, 2015

LGTM 👍 Feel free to squash my comment typo fix commit or leave it. Either way works for me. 🐍

catsby added a commit that referenced this pull request Apr 8, 2015
provider/aws: Change Route 53 record to allow resource updates
@catsby catsby merged commit 28f8dab into master Apr 8, 2015
@mitchellh mitchellh deleted the f-aws-route53record-add-update branch June 26, 2015 22:50
@ghost
Copy link

ghost commented May 1, 2020

I'm going to lock this issue 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 similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators May 1, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants