You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After packaging, gradle does the upload of the lambda zips/jars to s3. I guess we need unique ids for these s3 buckets, perhaps based on the test run.
When invoking the test phase, gradle injects some env variables with the name of the s3 bucket where the lambda zips/jars are
Using the AWS Java SDK we deploy lambdas during RestateDeployer.deploy(), using the s3 bucket as source code location
Execute the test
On RestateDeployer.undeploy() we remove the lambdas
After gradle test we remove the zips/jars from s3
We also probably need to tag the lambdas/s3 buckets with some well known tag like "e2e-tests", such that we can have a periodic cleanup of lambdas/s3 buckets on aws in case the test suite leaves some of them hanging around.
The text was updated successfully, but these errors were encountered:
It would be nice to reuse this test suite as it is to run tests on lambda. So far the idea is:
gradle build
will generate jars/zips for lambdagradle test
we remove the zips/jars from s3We also probably need to tag the lambdas/s3 buckets with some well known tag like "e2e-tests", such that we can have a periodic cleanup of lambdas/s3 buckets on aws in case the test suite leaves some of them hanging around.
The text was updated successfully, but these errors were encountered: