-
Notifications
You must be signed in to change notification settings - Fork 393
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
Feature/update go datadog api #118
Feature/update go datadog api #118
Conversation
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.
Unfortunately current states of the provider and the client don't align and we need to fix both sides, I'm currently working on a fix for the Precision
issue.
Please limit this PR to address the screenboard width
and height
issue.
@@ -175,7 +175,7 @@ func resourceDatadogScreenboard() *schema.Resource { | |||
Default: true, | |||
}, | |||
"precision": &schema.Schema{ | |||
Type: schema.TypeString, | |||
Type: schema.TypeFloat, |
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.
Precision can be "*"
so this won't work
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.
do you have a timeline for the fix for Precision
? I hate that it can be a number sometimes and a string other times.... :shakefistatserver:
Height: datadog.String(d.Get("height").(string)), | ||
Width: datadog.String(d.Get("width").(string)), | ||
Height: datadog.Int(d.Get("height").(int)), | ||
Width: datadog.Int(d.Get("width").(int)), |
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.
Width can be "100%"
so this won't work
@masci |
Fixes #105
Fixes #117