-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Hotswap + AppSync: Support for Hotswapping AppSync Schemas #24113
Labels
@aws-cdk/aws-appsync
Related to AWS AppSync
feature-request
A feature should be added or improved.
p3
Comments
alharris-at
added
feature-request
A feature should be added or improved.
needs-triage
This issue or PR still needs to be triaged.
labels
Feb 10, 2023
Thank you for your feature request. I am making them as p2 and will raise the awareness to the team. |
pahud
added
p2
and removed
needs-triage
This issue or PR still needs to be triaged.
labels
Feb 16, 2023
mergify bot
pushed a commit
that referenced
this issue
Sep 28, 2023
…appable (#27197) 1. Add GraphQLSchema as another AppSync resource that can be hotswapped 2. For all AppSync resources, accept the change in S3 assets/files instead of just inline code as a candidate for hotswap 3. Make pipeline resolvers hotswappable by resolving the functionId of AppSync functions. Closes #2659, #24112, #24113. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
@aws-cdk/aws-appsync
Related to AWS AppSync
feature-request
A feature should be added or improved.
p3
Describe the feature
Today, AppSync users have some limited hotswap capabilities in terms of updating Resolver and Function code, but they cannot update their GraphQL Schema, which I'd contend is the other most commonly iterated on part of an API.
I'd like to propose adding a new Hotswap for GraphQL Schema which will leverage the
StartSchemaCreationCommand
, and add a poller for theGetSchemaCreationStatusCommand
with some upper-bound timeout (e.g. 30s).This should allow iteration on more happy-case changes without needing to fallback to a full deploy, and hopefully take trivial schema changes (e.g. adding a field to a type) from ~100 seconds today to ~10 seconds as is seen w/ other hotswapped resources.
Use Case
I've written up a series of feature requests which I think will add to a faster, more fluid experience for AppSync users:
Proposed Solution
Add Hotswap for AppSyncGraphQLSchema resources.
Other Information
No response
Acknowledgements
CDK version used
2.64.0
Environment details (OS name and version, etc.)
osx 13.2
The text was updated successfully, but these errors were encountered: