d1b30e4be0
Current change addresses several problems - - It was impossible to re-stage already commited resources. For example re-run openstack actions without doing any artificial updates in solar inputs. - Also there was no way to execute actions that are not related to state in solar (run/update/remove). An example would be - restart of services. - And following changes addresses isolation problem in staging procedure. By design solar is isolated using tags semantics, but previous implemention of *process* was building a graph unconditionally for all staged resources. It was reworked and now we can support partial processing of resources, based on tags. Implicit staging will be done when resource is update/created/removed. Additionally actions can be staged using solar ch stage command, to support this additional flags were added: --action, -a - action that should be staged --tag, -t - tags to select group of resources --name, -n - resource that will be staged Only one from name or tag will be used, if user will provide both - name will be of higher priority Reverts and discard are working as previously for creation/update/removal of resources, but Exception will be raised if revert will be attempted for custom action, such as *restart*. Processing staged items can be achieved with - solar ch process -t tag1 -t tag2 History and staged log items will be stored in different buckets. Custom siblings resolved for LogItem will ensure that there is only one resource action is staged. implements blueprint refactor-process-of-staging-changes Change-Id: I9e634803a38d80213b87518cd2c8fdc022237aa0 |
||
---|---|---|
.. | ||
__init__.py | ||
api.py | ||
controls.py |