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

Enable tagging API gateway #148

Merged
merged 5 commits into from
May 17, 2024
Merged

Enable tagging API gateway #148

merged 5 commits into from
May 17, 2024

Conversation

flostadler
Copy link
Contributor

@flostadler flostadler commented May 17, 2024

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:
Screenshot 2024-05-17 at 21 59 02

@flostadler flostadler self-assigned this May 17, 2024
@flostadler flostadler requested a review from a team May 17, 2024 20:04
@@ -485,111 +485,6 @@ export interface DeploymentArgs {
stageDescription?: pulumi.Input<string>;
}

export class API extends pulumi.ComponentResource {
Copy link
Member

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!

@@ -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,
Copy link
Member

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.

Copy link
Contributor Author

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

Copy link
Member

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.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changed it!

@flostadler flostadler merged commit f5417b2 into main May 17, 2024
1 check passed
@flostadler flostadler deleted the 139-tags branch May 17, 2024 21:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add the possibility to Tag ApiGateway
2 participants