hashicorp/terraform-provider-aws

[Docs]: Import existing trail using ARN doesn't work, but it does if the trail name is used

Open

#37,179 opened on Apr 30, 2024

View on GitHub
 (5 comments) (0 reactions) (0 assignees)Go (10,310 forks)github user discovery
documentationgood first issueservice/cloudtrail

Repository metrics

Stars
 (11,045 stars)
PR merge metrics
 (PR metrics pending)

Description

Documentation Link

https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/cloudtrail#import

Description

The documentation states to use the CloudTrail ARN when doing a terraform import however this results in an error that the resource does not exist

Using the trail name however does result in a successful import.

For context, my trail is in a different AWS account to my state file, and the configuration block I am importing the existing trail to is set with an assume role provider - not sure if that makes any difference

This looks to be a mistake in the docs to me.

References

No response

Would you like to implement a fix?

No

Contributor guide

Research direction
Investigate the CloudTrail import documentation and the import implementation in the AWS provider source code. Reproduce the issue with both ARN and trail name to verify the correct usage, then update the documentation to match the working method.
Tech stack
go
Domain
documentation
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitTerraform
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75