Route 53 ALIAS Target Support

[jwaldrip]

@mitchellh I was hoping I could sneak this into 0.4.0 as well. Any chance we could make that happen?

[jwaldrip]

Running the acceptance tests locally right now.

[phinze]

Sorry @jwaldrip - the 0.4.0 train is already on its way. The release cycle for 0.4.1 and 0.5.0 will be much faster, so this shouldn't have to hang out too long.

[jwaldrip]

Great. I was worried It was going to be another 6 months :-).

[jwaldrip]

@phinze any idea how I can reference another variable as the default if its not provided?

[jwaldrip]

@phinze how does this implementation look?

[jwaldrip]

@catsby I know you have been thinking out this... But do you have any followup comments, or is this something you want to move forward with?

[catsby]

Sorry for the lag there. Can we review why this is a separate resource, instead of along side a normal Route 53 Record resource? What are the hurdles to maintaining them as a single resource?

[jwaldrip]

Not so much a hurdle. Just some additional conditional logic. AWS handles this kind of strange, as ALIAS targets are somewhat of a sub resource of a record and invalidates many fields if enabled. Mainly, Alias targets conflict with the fields "TTL" and "records". We could make it work, but they were "different enough" in my mind to separate them.

[catsby]

Sorry for the pain here @jwaldrip – we've actually since migrated back to https://github.com/awslabs/aws-sdk-go from our fork for the AWS library, can you swap that library out? It's preventing the tests from passing 😦

Let me know if you have questions on that or can't get to it, I can try and get to it this week

[radeksimko]

@catsby see #1775

[mitchellh]

Lets go with #1775 due to the refactor. Sorry for the delay @jwaldrip but this will get into 0.5! :)

[jwaldrip]

Good news!

[ghost]

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.