CloudBees-community/sbt-cloudbees-play-plugin — pull request #1 by eboto (2012-10-12 10:42:34+00:00)
Title: Introduced deployment based on Play application configurations.

Hello!

Thanks for the sweet plug-in. One of our needs at [Egraphs](https://www.egraphs.com) was to be able to specify deployment targets in our Play! config files rather than on the `Project` itself. Basically we have a bunch of different cloudbees app ids that run different configurations of the same app, and we wanted to encode the relationships between the two right there in the Play! config file.

So that's basically what this pull request does. It refactors things a bunch, but the only real change to functionality should be the addition of a project-level `InputTask` invokable as `cloudbees-deploy-config`.

For usage, Imagine a play project that contains `conf/application.conf`, `conf/live.conf`, and `conf/staging.conf` Inside of each of those files you could specify a different cloudbees application id: so, live.conf could have `cloudbees.applicationId=live-app`, where the value corresponds to an existing cloudbees application at `egraphs/live-app.`

Then you would use the tool like:
`> cloudbees-deploy-config live`, which deploys the live.conf configuration
`> cloudbees-deploy-config`, which deploys the default `application.conf` to its configured app id
`> cloudbees-deploy-config live new-live-app`, which deploys the `live` config to the `new-live-app` Run@cloud app id, overriding the value in the config file.

I hope this contribution makes sense in the direction you were taking the plug-in!