Comments (11)
any progress on this?
from terraform-provider-datadog.
I haven't been able to reproduce this (tried going from 0.10.2 to 0.10.3, as well as from 0.9.0 to 0.10.3). I'm not sure which datadog plugin version you were using, but I suspect this issue has been fixed. @RodrigoBerto, can you confirm and close or provide more info on the problem?
from terraform-provider-datadog.
I've run across this myself…and discovered it stems from the the yaxis config block generating different JSON than the Datadog UI does.
The following blip in the JSON will cause the import to fail.
"yaxis": {
"max": "100",
"min": "0"
}
The above is generated by the Datadog UI whereas Terraform is generating the following:
"yaxis": {
"max": 100,
"min": 0
}
This breaks the import as well as continued use of a Terraform plan. I.e. if I alter a time board from the Datadog UI, setting the y-axis values, the JSON will now have strings instead of floats resulting in the following output on a plan run:
datadog_timeboard.system_status: datadog_timeboard.system_status: json: cannot unmarshal string into Go struct field Yaxis.max of type float64
The Terraform docs still state these should be strings and strings are in fact what the HCL expects, but for some reason it would appear that a float is being used internally.
min - (Optional) Minimum bound for the graph's yaxis, a string.
max - (Optional) Maximum bound for the graph's yaxis, a string.
This is on Terraform v0.10.8 with terraform-provider-datadog_v1.0.0.
from terraform-provider-datadog.
I have also been running into this issue, has there been any progress on resolving this or any workarounds?
EDIT: Okay, well it seems the obvious workaround of removing the yaxis block from within the UI (I had to go into the JSON tab and delete that manually) works.
Would still be swell to be compatible with whatever remote state the datadog API generates.
from terraform-provider-datadog.
This is being tracked on the vendored SDK here: zorkian/go-datadog-api#103
from terraform-provider-datadog.
This looks similar to https://github.com/terraform-providers/terraform-provider-datadog/issues/10 which was fixed upstream, ie. Datadog fixed their API frontend to send int not string. Do they need to do the same here?
from terraform-provider-datadog.
This issue still remains in Datadog provider version 1.2.
from terraform-provider-datadog.
Raised #92 to fix this issue by bumping go-datadog-api library version number.
from terraform-provider-datadog.
Closing since fix was implemented in #91 and released in 1.3.0
from terraform-provider-datadog.
Reproduced in 1.6.0
from terraform-provider-datadog.
Hi!
I still have this problem in datadog v2.0.2
terraform providers -v
Terraform v0.12.3
+ provider.datadog v2.0.2
How I can reproduce this is:
- Create a simple screenboard
- Go to https://app.datadoghq.com/monitors/manage and check out your new dashboard.
- Click Edit
- Make no changes at all
- Press Save
- Run Terraform and receive this message.
Is there a workaround available?
from terraform-provider-datadog.
Related Issues (20)
- datadog_logs_index - allow changing Flex log settings
- Support querying incident analytics for dashboard widget overlays
- Add datadog_integration_snowflake resource
- Synthetic Test In-Place Update Removes config_variable valuable even when `example` value set HOT 3
- Automatically handle built-in pipelines in datadog_logs_pipeline_order
- Error creating `datadog_integration_aws_log_collection` fixed on rerun HOT 2
- Add new downtime resource HOT 2
- Document `assert_page_lacks` API HOT 1
- heredocs don't work in datadog_monitor querries
- No argument named "value" is in datadog_synthetics_test -> api_step, should be there according to doc
- `delegate_account_email` does not get set on `datadog_integration_gcp_sts` during import HOT 2
- Submit signing key to OpenTofu registry
- Dashboard: add `slo_summary` widget type support
- Erroneous update-in-place on datadog_monitor_json with restriction policy
- "object contains unparsed element" Error when using datadog_security_monitoring_default_rule HOT 1
- Support for monitors in resource datadog_restriction_policy
- Expose service_account field on users datasource
- API Multi-step Synthetics test creation failed with `extracted_value` HOT 4
- Inconsistent `start` times for `datadog_downtime_schedule` resource after apply
- Support restricted users and service accounts (not just roles)
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from terraform-provider-datadog.