I’m trying to use the CommVault powershell module to work with the API and integrate our backups with monitoring, so that our users will be able to see monitori ng and backup stats at a glance. Should be easy enough to show jobs, but the powershell Get-CVJob function is broken.
I had some help previously in the forum, and the broken bit was verified and posted to the gitHub powershell for CommVault projects, but I haven’t seen any movement since. Does anybody know how to fix this issue or what kind of timeframe I am working with to get this module fixed?
Best answer by Damian Andre
My guess is the “unexpected output” is that is still shows all the other jobs correct? If so ill hunt this down; since it throws an “info” cant use much PS to halt at that point.
Is there any kind of timeframe for how long it takes to turn around a GitHub issue? I did see the code alteration was suggested. Is there a way for me to edit the module and correct it to run this module and have the right output?
Hey @JMH_ML - Confirming we have lodged a defect for this issue (MR 309834). So it is being worked on but I don’t know an ETA currently.
My guess is the “unexpected output” is that is still shows all the other jobs correct? If so ill hunt this down; since it throws an “info” cant use much PS to halt at that point.
My guess is the “unexpected output” is that is still shows all the other jobs correct? If so ill hunt this down; since it throws an “info” cant use much PS to halt at that point.
My guess is the “unexpected output” is that is still shows all the other jobs correct? If so ill hunt this down; since it throws an “info” cant use much PS to halt at that point.
Is there any kind of timeframe for how long it takes to turn around a GitHub issue? I did see the code alteration was suggested. Is there a way for me to edit the module and correct it to run this module and have the right output?
My guess is the “unexpected output” is that is still shows all the other jobs correct? If so ill hunt this down; since it throws an “info” cant use much PS to halt at that point.
Is there any kind of timeframe for how long it takes to turn around a GitHub issue? I did see the code alteration was suggested. Is there a way for me to edit the module and correct it to run this module and have the right output?
Hey @JMH_ML - Confirming we have lodged a defect for this issue (MR 309834). So it is being worked on but I don’t know an ETA currently.
