Describe the feature
Today, AppSync Unit resolvers support hotswap, but Pipeline resolvers explicitly do not https://github.com/aws/aws-cdk/blob/main/packages/aws-cdk/lib/api/hotswap/appsync-mapping-templates.ts#L16-L24
I'd like to understand a bit more about the limitations here, if we're not changing the functions within a pipeline, and just update the templates or code are we able to resolve the existing function ids when performing the swap (we're able to resolve the apiId today, so I'd think this is basically equivalent).
Use Case
I'd love to have a more fluid iteration experience while working on the business logic for my AppSync APIs.
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
Support hotswapping templates and code in pipeline appsync resolvers.
Other Information
No response
Acknowledgements
CDK version used
2.64.0
Environment details (OS name and version, etc.)
osx 13.2
Describe the feature
Today, AppSync Unit resolvers support hotswap, but Pipeline resolvers explicitly do not https://github.com/aws/aws-cdk/blob/main/packages/aws-cdk/lib/api/hotswap/appsync-mapping-templates.ts#L16-L24
I'd like to understand a bit more about the limitations here, if we're not changing the functions within a pipeline, and just update the templates or code are we able to resolve the existing function ids when performing the swap (we're able to resolve the apiId today, so I'd think this is basically equivalent).
Use Case
I'd love to have a more fluid iteration experience while working on the business logic for my AppSync APIs.
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
Support hotswapping templates and code in pipeline appsync resolvers.
Other Information
No response
Acknowledgements
CDK version used
2.64.0
Environment details (OS name and version, etc.)
osx 13.2