Improve Disruption status #438
Replies: 2 comments 4 replies
-
Hi @Devatoria @ptnapoleon 👋 |
Beta Was this translation helpful? Give feedback.
-
Hi @nikos912000, sorry about the delay. I'll let others on the team give their opinions as well, but I think this is more state than we want to calculate or track. We are planning on making targeting and injecting no longer a one-time operation, so the concept of stages would be restricted to "has it been deleted yet and thus is trying to clean up". That's easy enough to know and communicate to the user. Would adding "Cleaning" and "FailedInjecting" states be sufficient for your needs? |
Beta Was this translation helpful? Give feedback.
-
Is your feature request related to a problem? Please describe.
Right now the Disruption status is one of the following:
The Injected status indicates a successful injection. However, there is no state that reflects a disruption that was not injected successfully.
Especially when integrating with CI/CD platforms it is critical to know the exact state of the experiments:
Describe the solution you'd like
A possible implementation can use stages and states for each stage.
This way, CI/CD platforms can expose these 2 stages to users and accurately reflect the status of each stage.
Beta Was this translation helpful? Give feedback.
All reactions