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: aws_db_option_group #4401

Merged
merged 2 commits into from
May 8, 2016

Conversation

stack72
Copy link
Contributor

@stack72 stack72 commented Dec 21, 2015

Scaffold the AWS DB Option Group resource

  • Schema
  • CRUD
  • Documentation
  • Acceptance Tests
  • Integrate with AWS RB Instance

@stack72 stack72 force-pushed the aws-rds-option-groups branch 2 times, most recently from 716fd4d to 85613a4 Compare December 21, 2015 09:45
@stack72 stack72 force-pushed the aws-rds-option-groups branch 3 times, most recently from edcf744 to 1ddf9de Compare December 22, 2015 15:10
@stack72 stack72 changed the title [WIP] provider/aws: aws_db_option_group provider/aws: aws_db_option_group Dec 22, 2015
@@ -362,8 +372,8 @@ func resourceAwsDbInstanceCreate(d *schema.ResourceData, meta interface{}) error
opts.TdeCredentialArn = aws.String(attr.(string))
}

if attr, ok := d.GetOk("storage_type"); ok {
opts.StorageType = aws.String(attr.(string))
if attr, ok := d.GetOk("option_group_name"); ok {
Copy link
Member

Choose a reason for hiding this comment

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

was it intentional to remove storage_type here?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

You are correct - this is now fixed

Copy link
Contributor

Choose a reason for hiding this comment

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

Looks like this section now has two option_group_name clauses (L362 & L382).

@catsby
Copy link
Member

catsby commented Jan 13, 2016

Looks like a promising start! I have some comments/asks that I've made, let me know what you think

@catsby catsby added the waiting-response An issue/pull request is waiting for a response from the community label Jan 13, 2016
@stack72 stack72 force-pushed the aws-rds-option-groups branch 4 times, most recently from 790a568 to 9c7d0dc Compare January 18, 2016 13:43
@jen20 jen20 removed the waiting-response An issue/pull request is waiting for a response from the community label Jan 19, 2016
@ocxo
Copy link

ocxo commented Jan 28, 2016

This is looking good. Anything else needed to get this into the next release?

@stack72
Copy link
Contributor Author

stack72 commented Jan 28, 2016

@fromonesrc this just needs another check to make sure everyone is happy - I only finished up the enhancements in the past week. As soon as someone from the core team is happy, then we can merge :)

@ocxo
Copy link

ocxo commented Jan 28, 2016

Thanks for your work on this!

@arthurschreiber
Copy link

@phinze @catsby Can you guys take another look at this?

parameter_group_name = "default.mysql5.6"
option_group_name = "${aws_db_option_group.bar.option_group_name}"
}`, rand.New(rand.NewSource(time.Now().UnixNano())).Int())

Copy link
Contributor

Choose a reason for hiding this comment

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

Is this full config necessary for the option group test? Seems like we could trim it down to just what that test needs to assert its stuff.

Copy link
Contributor

Choose a reason for hiding this comment

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

We could probably use the new acctest.RandInt() here for ensuring the names are unique?

@bigkraig
Copy link
Contributor

bigkraig commented Mar 2, 2016

I got the last problem fixed. I needed to serialize the option_settings as part of resourceAwsDbOptionHash.

@ocxo
Copy link

ocxo commented Mar 8, 2016

@stack72 is this something you're working on or looking for help with?

@arthurschreiber
Copy link

Can we also have option_name -> name and option_settings -> settings? Resource properties being prefixed with the resource type is really weird and not DRY.

@bigkraig
Copy link
Contributor

@stack72 I can update my pull request to your branch with the option_name & option_settings if that will help move things along

stack72 added a commit to stack72/terraform that referenced this pull request Apr 11, 2016
stack72 added a commit to stack72/terraform that referenced this pull request Apr 11, 2016
stack72 added a commit to stack72/terraform that referenced this pull request Apr 11, 2016
@stack72 stack72 force-pushed the aws-rds-option-groups branch 4 times, most recently from ec19802 to 15befd0 Compare April 27, 2016 19:00
@stack72
Copy link
Contributor Author

stack72 commented Apr 27, 2016

FYI, I am just working on getting the tests working here and then it will be ready to go

@stack72
Copy link
Contributor Author

stack72 commented Apr 27, 2016

ok this is now pending final review. I fixed up the comments @phinze gave (except the building of IAM - I have a follow up task for this once #5030 settles)

make testacc TEST=./builtin/providers/aws TESTARGS='-run=TestAccAWSDBOptionGroup' 2>~/tf.log
==> Checking that code complies with gofmt requirements...
go generate $(go list ./... | grep -v /vendor/)
TF_ACC=1 go test ./builtin/providers/aws -v -run=TestAccAWSDBOptionGroup -timeout 120m
=== RUN   TestAccAWSDBOptionGroup_basic
--- PASS: TestAccAWSDBOptionGroup_basic (16.05s)
=== RUN   TestAccAWSDBOptionGroup_sqlServerOptionsUpdate
--- PASS: TestAccAWSDBOptionGroup_sqlServerOptionsUpdate (27.36s)
=== RUN   TestAccAWSDBOptionGroup_multipleOptions
--- PASS: TestAccAWSDBOptionGroup_multipleOptions (16.46s)
PASS
ok      github.com/hashicorp/terraform/builtin/providers/aws    59.886s

@stack72 stack72 force-pushed the aws-rds-option-groups branch 3 times, most recently from 088c973 to 0844013 Compare April 27, 2016 22:58
Change the AWS DB Instance to now include the DB Option Group param. Adds a test to prove that it works

Add acceptance tests for the AWS DB Option Group work. This ensures that Options can be added and updated

Documentation for the AWS DB Option resource
@jen20
Copy link
Contributor

jen20 commented May 8, 2016

Looks good now!

@jen20 jen20 merged commit 5366fab into hashicorp:master May 8, 2016
@stack72 stack72 deleted the aws-rds-option-groups branch May 8, 2016 23:34
@catsby
Copy link
Member

catsby commented May 9, 2016

Looks like the test added to DB Instance was not updated, I patched it in #6558

@stack72
Copy link
Contributor Author

stack72 commented May 9, 2016

Sorry!

On Mon, May 9, 2016 at 6:33 PM, Clint notifications@github.com wrote:

Looks like the test added to DB Instance was not updated, I patched it in
#6558 #6558


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#4401 (comment)

@ghost
Copy link

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

None yet

8 participants