Open NBIX-Matt-DeWall opened 11 months ago
This sounds like an issue with rundeck, not the cli
Agree. Wasn't sure if this gets kicked upstream to the main project. Should I close and report in the main project?
I transferred it already -- GregOn Oct 9, 2023, at 3:54 PM, NBIX-Matt-DeWall @.***> wrote: Agree. Wasn't sure if this gets kicked upstream to the main project. Should I close and report in the main project?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>
Thanks!
I was originally trying to use the rundeck terraform provider, but when it failed I discovered the cli. I believe the CLI is running into the same issue and I'm better able to provide feedback.
I have a project where I want the default runner to be winrm so I can dispatch jobs to windows hosts.
The following project config (exported from the cli) works just fine if I delete the project and re-create:
With this config, this command is successful:
rd projects create -f ./it_help_desk.proj -p it_help_desk
However, simply re-running this as an update results in a 500 error:
This is the command I ran:
rd projects configure update -f ./it_help_desk.proj -p it_help_desk
While it may seem silly to do updates, I'm trying to fully automate this deployment and if there are changes I don't want to delete and recreate the project, which I image would impact running jobs. It seems the server is unhappy about the winrm plugin not being fully initialized on the backed while attributes are being added to it. Not sure.
Output from service.log
For now, my workaround is just to not touch this project once it's created, but seems like something that should be addressed. I moved away from the terraform provider as it couldn't even create a project. I think terraform was failing for the same reasons, as I was trying to pass in the WinRM plugin params. At least with the CLI, I can do a one-time create so I'm unblocked.
Thank you for all your efforts!