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

datadog_aws_integration resource should support "import" block #2257

Open
take-five opened this issue Jan 23, 2024 · 0 comments · May be fixed by #2788
Open

datadog_aws_integration resource should support "import" block #2257

take-five opened this issue Jan 23, 2024 · 0 comments · May be fixed by #2788

Comments

@take-five
Copy link

take-five commented Jan 23, 2024

What resources or data sources are affected?

resource_datadog_aws_integration

Feature Request

At the moment, datadog_aws_integration resource cannot be imported from configuration using import block, because of requirement of providing external_id attribute as environment variable.

Such semantics is not common for Terraform providers and breaks in configuration-driven imports, where it's not possible to specify environment variables per import block.

The workaround is, obviously, to run terraform import manually, but it may be difficult or even impossible in Terraform Cloud (Enterprise) remote runs, when the configuration depends on variables provided by Terraform Cloud. That is because terraform import always runs locally, so if some sensitive input variables are provided by TFC, you'd have to somehow extract them from TFC and provide for a local terraform import via -var command-line argument.

The desired outcome would be ability to import datadog_aws_integration resource without all this hassle, like this:

import {
  id = "111111111111:DatadogIntegrationRole/477dc7a8-6daa-4be4-b5e3-6a2c39c5d56b"
  to = datadog_aws_integration.this
}

References

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant