Why should I continue to use Rundeck?

45 views
Skip to first unread message

Brad Turnbough

unread,
Jan 25, 2023, 4:20:55 PM1/25/23
to rundeck-discuss
I started using rundeck about a year ago in hopes that it could make my life easier.  I have 23 years of IT experience, so I know the value of automating something and centrally managing said 'thing'.

Some observations / complaints:
Why, in this day in age can I not *easily* rename a project?
Why is it so incredibly complex to set up and utilize LDAP authentication?
Why can't I skip steps?
Why can't I *easily* move jobs from one project to another?
Why is this system file based, and not database based instead?

I had super high hopes with rundeck, but it just isn't on the level that I think it should be.  I think it has a lot of potential, though.  I might just migrate back to using shell scripts and cron jobs.  

Thoughts?  Attempts to persuade me not to jump off of the bridge?  

Thanks for any input you have.

rac...@rundeck.com

unread,
Jan 26, 2023, 7:25:53 AM1/26/23
to rundeck-discuss
Hi Brad,

Let me answer your questions as best I can :-)


Why, in this day in age can I not *easily* rename a project?

You're right, that was requested here. But now you can set a label in your project and this label is displayed instead of the "real project name". Of course, if you really need to change the name, another "alternative" is to create a script that creates a new project and imports the config and jobs using RD-CLI or API.


Why is it so incredibly complex to set up and utilize LDAP authentication?

Right, by design Rundeck uses some external modules and libraries to access network/auth protocols, and we're still working on a way of avoiding that complexity using the GUI Config Manager (Process Automation) or the Docker image environment variables (check the last answer).


Why can't I skip steps?

This functionality is available on Process Automation (formerly "Rundeck Enterprise") take a look at this.


Why can't I *easily* move jobs from one project to another?

Sounds good for an enhancement, currently, you can copy the same job to another project. Similar to the first answer, you can use an RD-CLI / API script that copies and then delete the job from the first project.


Why is this system file based, and not database based instead?

Similar to the second answer, some features and configurations are now managed via GUI on the Process Automation product avoiding the text file-based configs. Check this.

Please feel free to suggest any enhancement and, of course, any contribution is welcome (documentation, code enhancement, plugins, scripts, workarounds, features, articles in your blog/gist space, etc...).

Greetings!
Reply all
Reply to author
Forward
0 new messages