You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This concerns the resource datadog_integration_aws_account. When setting the attribute metrics_config.namespace_filters.exclude_only to a list of namespaces, Terraform accept the input on the first apply. However, after that the resources are shuffled and not sorted alphabetically either. Thus create and update are not idempotent on the attribute.
Observed behaviour
On runnign a plan again (after the first apply) the it shows a re-ordered list.
Expected behaviour
The ordering does not change.
It would be nice if the resource stick to an alphabetic sorting of list items every time instead of using the slightly weird ordering returned by the raw API.
At very least a documenting the order would be helpful.
Datadog Terraform Provider Version
v3.57.0
Terraform Version
1.6.6
What resources or data sources are affected?
This concerns the resource
datadog_integration_aws_account
. When setting the attributemetrics_config.namespace_filters.exclude_only
to a list of namespaces, Terraform accept the input on the first apply. However, after that the resources are shuffled and not sorted alphabetically either. Thus create and update are not idempotent on the attribute.Observed behaviour
On runnign a plan again (after the first apply) the it shows a re-ordered list.
Expected behaviour
The ordering does not change.
It would be nice if the resource stick to an alphabetic sorting of list items every time instead of using the slightly weird ordering returned by the raw API.
At very least a documenting the order would be helpful.
Example .tf file's
metrics_config
block:Example diff after first apply:
Terraform Configuration Files
Relevant debug or panic output
No response
Expected Behavior
No response
Actual Behavior
No response
Steps to Reproduce
No response
Important Factoids
No response
References
No response
The text was updated successfully, but these errors were encountered: