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

eventbridge_api_destination_arns output is wrong #78

Closed
1 task done
Rukeith opened this issue Jan 18, 2023 · 2 comments
Closed
1 task done

eventbridge_api_destination_arns output is wrong #78

Rukeith opened this issue Jan 18, 2023 · 2 comments

Comments

@Rukeith
Copy link

Rukeith commented Jan 18, 2023

Description

Please provide a clear and concise description of the issue you are encountering, and a reproduction of your configuration (see the examples/* directory for references that you can copy+paste and tailor to match your configs if you are unable to copy your exact configuration). The reproduction MUST be executable by running terraform init && terraform apply without any further changes.

If your request is for a new feature, please use the Feature request template.

  • ✋ I have searched the open/closed issues and my issue is not listed.

⚠️ Note

Before you submit an issue, please perform the following first:

  1. Remove the local .terraform directory (! ONLY if state is stored remotely, which hopefully you are following that best practice!): rm -rf .terraform/
  2. Re-initialize the project root to pull down modules: terraform init
  3. Re-attempt your terraform plan or apply and check if the issue still persists

Versions

  • Module version [Required]:
    1.17.0
  • Terraform version:
    1.3
  • Provider version(s):
    4.49

Reproduction Code [Required]

output eventbridge_api_destination_arns is return id not arn

Steps to reproduce the behavior:

Expected behavior

Return arn

Actual behavior

Return id

Terminal Output Screenshot(s)

Additional context

@antonbabenko
Copy link
Member

Fixed in #79

Copy link

github-actions bot commented Mar 9, 2024

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 9, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants