New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Support metadata map for infrastructure to support arbitrary run contexts (e.g. application/pipeline/execution) #29

Open

ericdriggs opened this issue Jun 27, 2023 · 0 comments

ericdriggs commented Jun 27, 2023 •

edited

Loading

Recommended implementation

add optional flat (single level) map for infrastructure metadata as string key/value

Potential use case:

When running spinnaker/kubernetes jobs, a project may be deployed to many applications/pipelines/executions. The cardinality is project <- application <- pipeline <- execution.
There may be many different cardinalities for other cloud implementations
would also allow specifying aws-region, environment, values for ENV variables, etc.. as needed

see: https://github.com/ota4j-team/open-test-reporting/blob/main/schema/src/main/resources/org/opentest4j/reporting/schema/core.xsd#L6C25-L6C39

ericdriggs mentioned this issue

investigate openreporting hierarchical format ericdriggs/reportcard#28

Closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment