-
Notifications
You must be signed in to change notification settings - Fork 5
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
Enable tagging API gateway #148
Conversation
@@ -485,111 +485,6 @@ export interface DeploymentArgs { | |||
stageDescription?: pulumi.Input<string>; | |||
} | |||
|
|||
export class API extends pulumi.ComponentResource { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Surprising it was hanging around, but good to remove if unused!
sdk/nodejs/restAPI.ts
Outdated
@@ -148,4 +149,9 @@ export interface RestAPIArgs { | |||
* Either `swaggerString` or `routes` must be specified. | |||
*/ | |||
swaggerString?: pulumi.Input<string>; | |||
/** | |||
* 'Map of tags to assign to the resource. If configured with a provider `default_tags` configuration block present, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Prefer to inflect defaultTags? There is no one good answer here since default_tags is how it works in Python, but defaultTags is how it works in Node, but Node is more commonly used.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I actually copied this from the docs of the underlying API gateway resource.
I wanted to stay in line with what we have on AWS classic, but I'm open to changing it if you think that'll be clearer
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Slight preference for defaultTags but no blocker.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changed it!
This adds the ability to tag the underlying resources of the API gateway component.
Closes #139
I cleaned up some dead code that was a leftover from extracting the API gateway component out of awsx. The resource
aws:apigateway:x:API
was not exposed in this provider and thus not included in the SDKs.Note, the automated test is not working right now because of bug #111.

For verification I deployed an API gateway with tags and verified that they exist: