Summary

The current test plan for FaaS metadata collection only validates that the presence of expected environment variables does not interfere with handshake logic.  To better validate the data collection, it should have tests that spin up environments in the relevant cloud providers to check that the actual variables in practice are being correctly collected.

Motivation

Who is the affected end user?

Data analysts using the collected data.

How does this affect the end user?

If the metadata is incorrectly parsed or not collected at all, the information will not be useful for analysis.

How likely is it that this problem or use case will occur?

Unlikely; the variables are well documented and of simple format.

If the problem does occur, what are the consequences and how severe are they?

Mild; the data will not be valid for analysis.

Is this issue urgent?

No.

Is this ticket required by a downstream team?

No.

Is this ticket only for tests?

Yes, this is only for improving the tests.

Acceptance Criteria

A design that covers:

• spinning up the cloud provider environments
• executing a test hello from those environments
• validating that the handshake sent includes the expected metadata