On 10/31/2012 08:36 PM, Richard Su wrote:
2. Once created, most deployment fields become read-only. The only
two
that can be changed are name and state. For state, we will display an
available_states field indicating the possible transitions from the
current state. Users can PUT the entire xml deployment representation.
Changes to read-only fields will be ignored if it is something trivial
like a create_at, or will result in an error message if say a change was
made to associate with a different pool.
https://redmine.aeolusproject.org/redmine/projects/aeolus/wiki/Deployments
I'm not sure if deployment/instance actions should be done through
update action. This was discussed in an older thread here:
https://lists.fedorahosted.org/pipermail/aeolus-devel/2012-July/011475.html
What do you think about creating separate resource(s) for actions?
Otherwise it looks great.
Jan