-
Notifications
You must be signed in to change notification settings - Fork 389
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
[Synthetics] Support SSL #279
[Synthetics] Support SSL #279
Conversation
btoueg
commented
Aug 7, 2019
•
edited
Loading
edited
- Add support for ssl tests
- Add acceptance test
- Update doc
- Have subtype defaults to http for api tests
- Make sure existing TF files won't diff
Hey @btoueg thanks for the PR! The golang client was released + bumped in this provider. Can you rebase from master and we can work on getting this reviewed? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall looks good, thanks for the PR 🎉. Left a couple of small comments inline.
I did notice that with the example config, two successive plans
cause an un-empty diff with:
options.accept_self_signed: "false" => "1"
Can you look into that? Thanks!
@@ -316,6 +359,9 @@ func newSyntheticsTestFromLocalState(d *schema.ResourceData) *datadog.Synthetics | |||
minLocationFailed, _ := strconv.Atoi(attr.(string)) | |||
options.SetMinLocationFailed(minLocationFailed) | |||
} | |||
if attr, ok := d.GetOk("options.accept_self_signed"); ok { | |||
options.SetAcceptSelfSigned(attr.(string) == "true") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any reason not to just assign this to attr.(string)
Should we also safely type assert this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure, can't wrap my head around it. It's value is "1" or "0" in TF 0.11, even though is never set to such value
Indeed, that's the case in TF 0.11. I've handled it, let me know |
Thanks for the iterations here! Looks good to me, I'll go ahead and merge. Thanks for this 🎉🚀 |