Creating data block which can access all resources using certain tag

[krishnaduttPanchagnula]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

lets say that we have different resources like RDS, some EC2 an EKS in a single account with one of two tags, Dev or Prod. I Would like to get the arns and names of all resources with Dev tag.

New or Affected Resource(s)

• aws_XXXXX

Potential Terraform Configuration

# Copy-paste your Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file. For
# security, you can also encrypt the files using our GPG public key.

References

• 0000

[justinretzolk]

Hey @krishnaduttPanchagnula 👋 Thank you for taking the time to raise this! So that we have all of the necessary information in order to look into this, can you add a bit more details in the description? For example, are you looking to just get a list of all resources that are using the specified tag, or are you looking for more detail, such as ARNs, etc.?

[krishnaduttPanchagnula]

@justinretzolk lets say that we have different resources like RDS, some EC2 an EKS in a single account with one of two tags, Dev or Prod. I Would like to get the arns and names of all resources with Dev tag.

[github-actions[bot]]

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!