Feature req: Data source for aws_api_gateway_stage

[bishtawi]

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

It would be very helpful to have a data source for aws_api_gateway_stage.

It looks like there was already a Pull Request (#8890) opened to add this exact feature but was closed and locked due to inactivity.

New or Affected Resource(s)

• aws_api_gateway_stage

References

• Feature/add api gateway stage data source #8890

[RomainBillot]

Would be great to have this..

Actually, we have no way to get a stage invoke_uri from another terraform project (need it for application code)

[brent-moffit]

In our deployment we have a single REST API in API Gateway that distributes the individual resource paths to different microservices via HTTP_PROXY integrations. Each microservice has its own terraform scripts that manage their individual infrastructure, including the methods/integrations on API Gateway.

The problem is that no single microservice owns the REST API and stage in API Gateway, so while they can use terraform to add endpoints they cannot automatically deploy those endpoints without being able to get a data source reference to the stage as you hit the warning described in the aws_api_gateway_deployment docs. Having a data reference to the stage would presumably be helpful.

[github-actions]

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!