configuration-as-code

Currently the developer docs are spread through files in https://github.com/jenkinsci/configuration-as-code-plugin/tree/master/docs

It would be good to:

• put them in their own folder
• name them the same as the rest of the files
• review them and ensure they aren't overlapping and are up to date
• have a README in the developer folder that guides you through developer changes
• ensure t

Details of the scenario you try and problem that is occurring:
For a large search topology I'm missing a few things. One is that all the databases are created in the same sql instance. The name cannot be configured individually and there is only one property for the sql server. And I need to create multiple crawl store databases which is not possible with the current version. The multiple cra

Scenario:

1. Created a new detector along with a Dashboard.
2. Changed that detector to a different one and ran a dashboard update.

User expectation: New detector will be created and the old one will be deleted as it happens with our dashboards and charts.
Actual result: The new detector is created but the old one still stays.

We need to change this behavior to mirro

Feature request from @amarza-rh

Add a way to test changes using Stage Tower (pre-merge) when post-merge we apply changes to Prod Tower would require two sets of credentials