6ca0ee146d
Instead of dealing with some decidated functions in Update/upgrade classes for manipulating the plan and the env files, inherit the update class from the DeployCommand class will allow the update && upgrade to take benefit from the plan management code and all the tips and tricks that the deploy class does for handling the corner cases of the plan (access rights, path of user files) Also it avoid to rewrite/duplicate some code to solve the issue where the --templates option is ignored by the update workflow (and upgrade for Queens btw). Related tripleo-common review: https://review.openstack.org/540816 Depends-On: Ica4bb404cd3a38a97300b8af36af41c35f09825c Change-Id: Ib96f4f5078ec1c45981d051e546bf931d2885ae2 |
||
|---|---|---|
| .. | ||
| tests | ||
| v1 | ||
| workflows | ||
| __init__.py | ||
| command.py | ||
| constants.py | ||
| exceptions.py | ||
| heat_launcher.py | ||
| noauth_policy.json | ||
| plugin.py | ||
| utils.py | ||