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

Implement aws_db_subnet_group resource #164

Closed
wants to merge 1 commit into from

Conversation

alekstorm
Copy link
Contributor

Depends on mitchellh/goamz#74. Related to #28.

Also adds a db_subnet_group_name parameter to aws_db_instance.

I'm new to Go, and mostly fumbled my way through this PR by copying and adapting aws_db_security_group; sorry if I screwed up any idioms.


stateConf := &resource.StateChangeConf{
// TODO are there any other states?
Pending: []string{},
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I imagine this won't work as is, due to this. If we run the acceptance tests it should give us the various states. Are you familiar with how to run those?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, but they all pass - the DB subnet group is created so quickly that I can't issue a request fast enough to discover its intermediate state. The docs and a fair amount of googling have turned up no answers, but we have an AWS enterprise support account; I'll ask them. In the meantime, can this be merged, as the lack of intermediate states is fine in practice?

@alekstorm alekstorm force-pushed the aws-db-subnet-group branch from d28da4b to 0b9fd66 Compare August 21, 2014 21:41
@pearkes
Copy link
Contributor

pearkes commented Sep 16, 2014

Hey @alekstorm, before we got this in we saw #295 using the new schema API, which is preferable. Thanks for all your help!

@pearkes pearkes closed this Sep 16, 2014
@ghost ghost locked and limited conversation to collaborators May 5, 2020
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.

2 participants