Skip to content

add Monitoring actions functionality #109

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

Open
dcompane opened this issue Dec 14, 2024 · 2 comments
Open

add Monitoring actions functionality #109

dcompane opened this issue Dec 14, 2024 · 2 comments
Labels

Comments

@dcompane
Copy link

Is your feature request related to a problem? Please describe.
I am working on a python script to add an event to trigger a job, and I do not see a way to do it in the documentation.

Describe the solution you'd like
workflow.run.add_event(event, odate, server)
, or alike.

Describe alternatives you've considered
triggering the ctm cli from the script
using the swagger code gen to create my own client

Additional context
Other functions that would support DevOps and Platform Engineering activities would be great. Hold, rerun, manage nodegroups, etc.

@slancer50 slancer50 added the enhancement New feature or request label Feb 26, 2025
@nathanw9722
Copy link
Collaborator

@dcompane a Workflow represents a collection of Folders and Jobs at the Server level, so I don't think it's the right class to use here. The Workflow python class also does not have a run method. Events are deployed at the Server level, so this should be Server class method. Please open a separate issue for runtime actions (Hold, Rerun, Bypass, etc.).

@dcompane
Copy link
Author

dcompane commented Mar 25, 2025

Thanks @nathanw9722!

OK. so where can we add that? The idea is not to augment or make more complicated the Workflow model, but to provide a complete client that can support DevOps operations, CI/CD pipelines, and alike.

Otherwise, some actions need to be done on powershell or bash because the ctm cli is needed, and when others can be done in python. Seems difficult to standardize.

Edit: I just noticed that you asked for a separate issue. This issue is about runtime (Monitoring) actions, so I am not sure why a new issue is needed.

I keep compiling my own (https://github.com/dcompane/controlm_py) for my own use, but I much work with one that is fully supported.

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

No branches or pull requests

3 participants