Mike Lohmeier

PR ready to be made. Waiting on issue #2 to be merged first.

It looks like this utility will have the same issue with some of the other parameter types as well. @apiHeader, etc

Thanks, makes sense that this would be from write to 1st send attempt. Also, makes sense why tenantId and subscription are not dimensions since there's no differing infrastructure or code...

Actually, I'm going to wait until the result of https://github.com/awslabs/fhir-works-on-aws-deployment/issues/676 before starting a PR for this one because there is control flow changes in the https://github.com/awslabs/fhir-works-on-aws-deployment/issues/676 that are working with...

This PR doesn't change the behavior of bad endpoint sends other than ordering them most likely behind good endpoints in a single batch. However, with enough bad subscription notifications in...

Not sure why this PR isn't linking btw, https://github.com/awslabs/fhir-works-on-aws-deployment/pull/677

You can include the lib with the following and then the behavior should be the same. ``` import pkg from 'adm-zip'; const AdmZip = pkg; ```

@Bingjiling Apologies on how long it took to get this wrapped up. I was able to create a generic convention for building synthetics and having them uploaded via a new...

Not sure why github is flagging the feature/synthetics_pr as having conflicts in package.json & serverless.yaml when the conflicts have been resolved in the branch already. I tried using the github...

Pushed an update to the latest puppeteer runtime and it resolved the conflicts. Not sure why github got tripped up but it looks to be resolved now.