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!