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

aws.apigateway.RestApi does not have an id Output, looks like it's on api.id now #6370

Open
notbrain opened this issue Jan 8, 2025 · 1 comment
Labels
awaiting-feedback Blocked on input from the author

Comments

@notbrain
Copy link

notbrain commented Jan 8, 2025

File: themes/default/content//registry/packages/aws/api-docs/apigateway/restapi

Per the source for 6.66.2 of @pulumi/aws, there is no id property on a RestApi resource. Looks like it's now restApiResource.api.id. Which is kind of confusing, since it's not at the top level like many other resources.

@pulumi-bot pulumi-bot added the needs-triage Needs attention from the triage team label Jan 8, 2025
@mjeffryes
Copy link
Member

I'm sorry I don't quite see what you're saying. All pulumi-aws resources do have an id property that's returned by the provider. The RestApi resource also has a rootResourceId that's returned from ApiGgateway

Image

I don't however see any api output on that resource. I wonder if you might be using https://www.pulumi.com/registry/packages/aws-apigateway/api-docs/restapi/ instead? That's a component resource that assists with creating the underlying AWS resources. It doesn't have an id field because an id of the component resource is not meaningful, but it returns an instance of a pulumi-aws RestApi resource in it's api field (which as discussed above, does have an id field).

I hope that helps?

@mjeffryes mjeffryes added awaiting-feedback Blocked on input from the author and removed needs-triage Needs attention from the triage team labels Jan 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting-feedback Blocked on input from the author
Projects
None yet
Development

No branches or pull requests

3 participants