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

[Enhancement]: add ARN attribute to CodeDeploy config #35281

Closed
sterliakov opened this issue Jan 12, 2024 · 3 comments · Fixed by #35888
Closed

[Enhancement]: add ARN attribute to CodeDeploy config #35281

sterliakov opened this issue Jan 12, 2024 · 3 comments · Fixed by #35888
Labels
enhancement Requests to existing resources that expand the functionality or scope. good first issue Call to action for new contributors looking for a place to start. Smaller or straightforward issues. service/deploy Issues and PRs that pertain to the deploy service.
Milestone

Comments

@sterliakov
Copy link

sterliakov commented Jan 12, 2024

Description

An ARN of CodeDeploy deployment config is necessary to build a correct IAM policy. My CodePipeline needs a codedeploy:GetDeploymentConfig permission which is resource-based, so currently it looks like arn:aws:codedeploy:${var.region}:${var.account_id}:deploymentconfig:${aws_codedeploy_deployment_config.main.id} - not very tasty.

Affected Resource(s) and/or Data Source(s)

  • aws_codedeploy_deployment_config

Potential Terraform Configuration

# No resource config changes

References

Permissions reference

Would you like to implement a fix?

No (sorry, I hardly speak Golang)

@sterliakov sterliakov added the enhancement Requests to existing resources that expand the functionality or scope. label Jan 12, 2024
Copy link

Community Note

Voting for Prioritization

  • Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
  • Please see our prioritization guide for information on how we prioritize.
  • 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.

Volunteering to Work on This Issue

  • If you are interested in working on this issue, please leave a comment.
  • If this would be your first contribution, please review the contribution guide.

@github-actions github-actions bot added the service/deploy Issues and PRs that pertain to the deploy service. label Jan 12, 2024
@terraform-aws-provider terraform-aws-provider bot added the needs-triage Waiting for first response or review from a maintainer. label Jan 12, 2024
@justinretzolk justinretzolk added good first issue Call to action for new contributors looking for a place to start. Smaller or straightforward issues. and removed needs-triage Waiting for first response or review from a maintainer. labels Jan 16, 2024
@github-actions github-actions bot added this to the v5.38.0 milestone Feb 20, 2024
Copy link

This functionality has been released in v5.38.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

Copy link

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 25, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement Requests to existing resources that expand the functionality or scope. good first issue Call to action for new contributors looking for a place to start. Smaller or straightforward issues. service/deploy Issues and PRs that pertain to the deploy service.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants