Plan for 'upgrade' of installed content

[chouseknecht]

Based on plan for Namespacing of content (#104), document the plan for implementing an update command, including the following:

• How will installed content be tracked, and specifically what info about the installed content will be tracked?
• What will be the user experience for performing an update (e.g. command line options, output, etc.)?
• How will dependencies be handled during the update?
• Can all installed content be updated, or only Galaxy installed content?
• Are all forms of dependencies updated, or only Galaxy dependencies?

We can close this issue when:

• [ ] Plan has been approved by Ansible core, @thaumos, @tima
• [ ] Plan is documented and presented to the team
• [ ] Plan is organized into sprints and issues

[alikins]

@chouseknecht any preferences for where these docs should live?

[alikins]

@chouseknecht "Are all forms of dependencies updated, or only Galaxy dependencies?"

Does 'all forms for dependencies updated' mean things like python package deps or other external deps?

[chouseknecht]

Let's start with a Google doc, and get it to a point where we can present it as a cohesive proposal to the community.

I think 'all forms of dependencies' means Galaxy dependencies, which at the moment is limited to role dependencies. Let's solve that first. Maybe in the future it could encompass Python dependencies, but I think we can address that further into the future.

[alikins]

@chouseknecht See https://docs.google.com/document/d/18k-6uF9nyeaZb91bJoW1BghvL4Zhkz3VImzBNw38Q94/edit?usp=sharing