We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently, a playbook can be triggered from the Container Watcher as well as the Playbooks view
There is a degree of duplication in this logic that should not be necessary and will make updates to the playbook execution logic easier.
The text was updated successfully, but these errors were encountered:
Ideally, we'd re-use the same logic for getting a Container ID at every interaction that does this.
Sorry, something went wrong.
No branches or pull requests
Currently, a playbook can be triggered from the Container Watcher as well as the Playbooks view
There is a degree of duplication in this logic that should not be necessary and will make updates to the playbook execution logic easier.
The text was updated successfully, but these errors were encountered: