Skip to content

fix: Fixed APPSYNC_JS resolvers for both kinds (UNIT and PIPELINE) #55

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

Merged
merged 2 commits into from
Aug 30, 2023
Merged

fix: Fixed APPSYNC_JS resolvers for both kinds (UNIT and PIPELINE) #55

merged 2 commits into from
Aug 30, 2023

Conversation

jagoodhand
Copy link
Contributor

@jagoodhand jagoodhand commented Aug 30, 2023

Description

Remove the requirement for the resolver 'kind' property to be 'PIPELINE'. Currently both 'UNIT' and 'PIPELINE' resolvers allow for code to be added when the runtime is APPSYNC_JS.

Motivation and Context

Fixes #54

Breaking Changes

No.

How Has This Been Tested?

  • I have updated at least one of the examples/* to demonstrate and validate my change(s)
  • I have tested and validated these changes using one or more of the provided examples/* projects
  • I have executed pre-commit run -a on my pull request

… for appsync_js

Request and response templates had default values if the kind wasn’t “PIPELINE”. This isn’t allowed when providing ‘code’ so needed to be removed.
@jagoodhand jagoodhand changed the title Fix unit appsync js resolvers (fixes issue #54) fix: allow appsync_js resolver of type 'unit' Aug 30, 2023
@antonbabenko antonbabenko changed the title fix: allow appsync_js resolver of type 'unit' fix: Fixed APPSYNC_JS resolvers for both kinds (UNIT and PIPELINE) Aug 30, 2023
@jagoodhand jagoodhand changed the title fix: Fixed APPSYNC_JS resolvers for both kinds (UNIT and PIPELINE) fix: Allow appsync_js resolver of type 'unit' Aug 30, 2023
@jagoodhand jagoodhand changed the title fix: Allow appsync_js resolver of type 'unit' fix: Fixed APPSYNC_JS resolvers for both kinds (UNIT and PIPELINE) Aug 30, 2023
@jagoodhand
Copy link
Contributor Author

@antonbabenko - let me know if this needs any other work doing before merging.

@antonbabenko antonbabenko merged commit 9d3e9b0 into terraform-aws-modules:master Aug 30, 2023
@antonbabenko
Copy link
Member

Looks good, thanks @jagoodhand !

antonbabenko pushed a commit that referenced this pull request Aug 30, 2023
### [2.2.1](v2.2.0...v2.2.1) (2023-08-30)

### Bug Fixes

* Fixed APPSYNC_JS resolvers for both kinds (UNIT and PIPELINE) ([#55](#55)) ([9d3e9b0](9d3e9b0))
@antonbabenko
Copy link
Member

This PR is included in version 2.2.1 🎉

@jagoodhand jagoodhand deleted the fix-unit-appsync-js-resolvers branch August 30, 2023 16:11
Copy link

github-actions bot commented Mar 8, 2024

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 8, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Current configuration prevents AppSync Resolvers of type 'UNIT' using 'APPSYNC_JS' resolvers
2 participants