Skip to content
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.

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

Propose new event, "Artifact.flagged" #163

Open
dan-han-101 opened this issue Sep 11, 2023 · 2 comments
Open

Propose new event, "Artifact.flagged" #163

dan-han-101 opened this issue Sep 11, 2023 · 2 comments

Comments

@dan-han-101
Copy link
Contributor

Currently, an "artifact" has the following predicates: packaged, published, and signed.

In #143 - there is a discussion on adding

  • artifact.pulled
  • deleted
  • scanned

And in #144 - there is a discussion for adding

  • artifact.pushed

In this Issue, I'd like to propose adding another event, artifact.flagged.

Our use case

We run tests that create messages like testSuiteRun.finished and testSuiteRun.finished. These tests ultimately are intended to validate whether some other system-under-test is in a healthy state. When a test completes, we would like to post a message, saying that a given "artifact" has been "flagged" with a passing or failing test.

Alternatives

While, internally, we have been using the rather generic name of "flagged", for our purposes, it would be fine with us to go to a more granular level and have the message instead be "Artifact.tested".

Message details

Roughly, we envision something that has identifers for the artifact, and identifiers for the test with its associated status (failed/passed/etc...)

@e-backmark-ericsson
Copy link
Contributor

@dan-han-101 , this artifact.flagged event, do you think it is the same use case as the confidence label or maturity level terms I mentioned in my comment on this issue: #143 (comment) ?

@dan-han-101
Copy link
Contributor Author

@e-backmark-ericsson - Yes, I think this issue is similar to a confidence label or maturity level .

I also saw someone mention artifact.quarantined - I think is close to what I was looking for.

I'm Ok to close this issue if existing issues already overlap. And I can just follow and add comments to the other ones.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants