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.

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

TASK: track CR workload status on a per-compose basis #152

Open
davide125 opened this issue Jul 18, 2023 · 1 comment
Open

TASK: track CR workload status on a per-compose basis #152

davide125 opened this issue Jul 18, 2023 · 1 comment
Assignees
@bookwar @sgallagher

Comments

@davide125
Copy link
Member

Right now it's hard to tell whether a given CR workload was skipped or not as part of a compose. It would be useful to have a machine-readable WORKLOAD_STATUS or akin tracking which workloads were part of the compose and if any failed. @sgallagher suggested one way to implement this could be record compose IDs in CR, so it'd be explicit what the results refer to.
@yselkowitz
Copy link
Member

Could you clarify the problem please?

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

@bookwar bookwar

@sgallagher sgallagher

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@davide125 @bookwar @sgallagher @yselkowitz