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

Update service definitions for cloudwatch-events #544

Merged
merged 1 commit into from Aug 23, 2019

Conversation

MichaelXavier
Copy link
Collaborator

This add some paginators and some networking features that appear to
be required for using this service with Fargate.

I tried to follow the advice of gen/README.md and only committed the changes to the service files. LMK if this wasn't right. We're due for a dozen or two other service updates but I wanted to make my MR minimal.

This add some paginators and some networking features that appear to
be required for using this service with Fargate.
MichaelXavier added a commit to Soostone/amazonka that referenced this pull request Aug 23, 2019
This branch can be removed when/if PR brendanhay#544 is merged. It includes
generated code, which is discouraged from going in PRs. Still, to
depend on our fork we need the generated code, hence this branch.
Copy link
Owner

@brendanhay brendanhay left a comment

Choose a reason for hiding this comment

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

LGTM :shipit:

@MichaelXavier MichaelXavier merged commit 4e25f15 into brendanhay:develop Aug 23, 2019
@MichaelXavier MichaelXavier deleted the cloudwatch-events-update branch August 23, 2019 23:00
@MichaelXavier
Copy link
Collaborator Author

Tested this out today and it looks like it works. @brendanhay I've got my own fork with the codegen applied. How should we go about doing the codegen for this project? Given that releases are kind of painful, we'd probably want to do an across-the-board update of service definition files.

brendanhay pushed a commit that referenced this pull request Jul 27, 2020
This branch can be removed when/if PR #544 is merged. It includes
generated code, which is discouraged from going in PRs. Still, to
depend on our fork we need the generated code, hence this branch.
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.

None yet

2 participants