Context
Requested by the floci maintainer on the upstream PR (floci-io/floci#2079):
Could you include compatibility-tests for this new addition. Tests will ensure future changes don't break any functionality.
This is also the one unticked task on #32.
floci keeps these in compatibility-tests/, separate from the Maven test suite: sdk-test-{awscli,go,java,node,python} run bats inside a container against a live floci, plus compat-cdk, compat-terraform and compat-opentofu. CONTRIBUTING.md lists them as a first-class way to contribute.
What to write
The lifecycle is already verified by hand against the published image, so the content is known — create an image, poll to SUCCESSFUL, run a MicroVM, suspend, resume, mint an auth token, tag it. sdk-test-awscli is the natural home: the AWS CLI covers the whole surface and needs no SDK-specific harness.
A CFN case in compat-cdk or compat-terraform would cover the provisioners for AWS::Lambda::MicrovmImage and AWS::Lambda::NetworkConnector, which is the half of the PR the Maven integration test already exercises but nothing external does.
Tasks
Not gated — the branch is already pushed and the PR is open, so this is adding commits to work in flight rather than a new outward-facing step.
Related
Context
Requested by the floci maintainer on the upstream PR (floci-io/floci#2079):
This is also the one unticked task on #32.
floci keeps these in
compatibility-tests/, separate from the Maven test suite:sdk-test-{awscli,go,java,node,python}run bats inside a container against a live floci, pluscompat-cdk,compat-terraformandcompat-opentofu.CONTRIBUTING.mdlists them as a first-class way to contribute.What to write
The lifecycle is already verified by hand against the published image, so the content is known — create an image, poll to
SUCCESSFUL, run a MicroVM, suspend, resume, mint an auth token, tag it.sdk-test-awscliis the natural home: the AWS CLI covers the whole surface and needs no SDK-specific harness.A CFN case in
compat-cdkorcompat-terraformwould cover the provisioners forAWS::Lambda::MicrovmImageandAWS::Lambda::NetworkConnector, which is the half of the PR the Maven integration test already exercises but nothing external does.Tasks
sdk-test-awsclicases for the image, MicroVM and connector lifecyclesNot gated — the branch is already pushed and the PR is open, so this is adding commits to work in flight rather than a new outward-facing step.
Related