Unplaced units show up in changelog and make the "Commit" button active

[Huw Wilkins]

To reproduce:
- add a service
- deploy your changes
- the changelog will read "1 mysql unit has been added." and the "Commit" button is active, even though there is nothing to commit

[Kyle Adams (kadams54)]

I think this is working as intended. If the user does not place a unit, or select "Automatically place" in the deploy summary, it will remain unplaced. Hence, "1 mysql unit has been added" and the active commit button. I can't reproduce if I select "Automatically place" - the unit is put on a new machine and nothing is left over after the deploy.

[Kyle Adams (kadams54)]

After talking over with Rick, we're going to seek more feedback on the UX and see if there's any way we can improve the workflow and make it more obvious what's happening here.

[Huw Wilkins (huwshimi)]

I think at the very least the commit button should not be active as there is nothing to commit.

[Huw Wilkins (huwshimi)]

Oh, I am wrong, as rick pointed out, once you hit commit you can choose to auto-deploy unplaced units onto new machines.

[Richard Harding (rharding)]

Going to run with the current interaction and get feedback from users. Closing as invalid for now.