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: Fix aws_route53_record 0-2 migration #7907

Merged
merged 1 commit into from
Aug 1, 2016

Conversation

jen20
Copy link
Contributor

@jen20 jen20 commented Aug 1, 2016

When migrating the state of an aws_route53_record, a v0 state was never upgraded to v2, and a typo in a unit test masked this. This commit fixes the migration by chaining the invocation of the migration function, and corrects the test.

@jen20
Copy link
Contributor Author

jen20 commented Aug 1, 2016

cc @phinze

When migrating the state of an `aws_route53_record`, a v0 state was
never upgraded to v2, and a typo in a unit test masked this. This commit
fixes the migration by chaining the invocation of the migration
function, and corrects the test.
@jen20 jen20 force-pushed the b-route53-record-migration branch from 021019f to fa8160c Compare August 1, 2016 23:17
@stack72
Copy link
Contributor

stack72 commented Aug 1, 2016

LGTM! Will merge when travis goes green

@stack72 stack72 merged commit f76c1ec into master Aug 1, 2016
@stack72 stack72 deleted the b-route53-record-migration branch August 1, 2016 23:54
kwilczynski pushed a commit to kwilczynski/terraform that referenced this pull request Aug 4, 2016
When migrating the state of an `aws_route53_record`, a v0 state was
never upgraded to v2, and a typo in a unit test masked this. This commit
fixes the migration by chaining the invocation of the migration
function, and corrects the test.
@ghost
Copy link

ghost commented Apr 23, 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 Apr 23, 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