Skip to content

Initial tests for alta_open_lambda#7

Draft
camdroid wants to merge 1 commit into
mainfrom
test_lambda_legacy_format
Draft

Initial tests for alta_open_lambda#7
camdroid wants to merge 1 commit into
mainfrom
test_lambda_legacy_format

Conversation

@camdroid

Copy link
Copy Markdown
Owner

With the upcoming Neon webhook deprecation, we need for the
alta-open-update lambda to be able to handle both the legacy and the new
webhook format. Roughly, this is what the deprecation strategy looks
like:

  • Enable new Neon webhooks (already done)
  • Update lambda to work on both styles of payload (new or legacy)
  • Monitor results, ensure that there are no errors and that the new
    webhooks have the correct behavior.
  • Disable legacy webhooks (one at a time) in Neon.
  • Monitor results, ensure that operations are happening as expected
    (accounts are actually being created, etc.)
  • Update lambda to throw an error for legacy webhook calls, without
    updating Alta.
  • (Eventually) Remove code for handling legacy Neon webhooks.

To help with the first step of updating the lambda, I want to write a
test suite to capture the current behavior. The point of this isn't to
catch any new bugs, just to verify what's already happening in the
lambda.

Once we can show what behavior is currently happening under the legacy
webhooks, we can start adding in the new webhook formats and ensuring
that the tests work with those, too, using the legacy flag if needed.


Stack created with GitHub Stacks CLIGive Feedback 💬

With the upcoming Neon webhook deprecation, we need for the
alta-open-update lambda to be able to handle both the legacy and the new
webhook format. Roughly, this is what the deprecation strategy looks
like:
* Enable new Neon webhooks (already done)
* Update lambda to work on both styles of payload (new or legacy)
* Monitor results, ensure that there are no errors and that the new
  webhooks have the correct behavior.
* Disable legacy webhooks (one at a time) in Neon.
* Monitor results, ensure that operations are happening as expected
  (accounts are actually being created, etc.)
* Update lambda to throw an error for legacy webhook calls, without
  updating Alta.
* (Eventually) Remove code for handling legacy Neon webhooks.

To help with the first step of updating the lambda, I want to write a
test suite to capture the current behavior. The point of this isn't to
catch any new bugs, just to verify what's already happening in the
lambda.

Once we can show what behavior is currently happening under the legacy
webhooks, we can start adding in the new webhook formats and ensuring
that the tests work with those, too, using the `legacy` flag if needed.
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.

1 participant