Zane Bitter 37033936bf Add separate policy for updates with no changes ... Allow operators to set a different (presumably looser) policy on PATCH updates that don't make any changes to the stack, but just retrigger a new update traversal (that will result in e.g. replacing any unhealthy resources). Change-Id: Id29e7ec7f6cf127177ea7ab29127b0568afaa18b Task: 37305		2019-10-26 00:29:19 -04:00
..
__init__.py	Remove CloudWatch API	2018-01-28 09:11:17 +05:30
actions.py	Split 'action' policy into more granular controls	2019-10-25 00:30:56 -04:00
base.py	[policy in code] Part 1 Base framework	2017-11-21 16:23:11 +08:00
build_info.py	[policy in code] part 4	2017-12-01 01:34:59 +08:00
cloudformation.py	[policy in code] part 6(cfn, cloudwatch)	2017-12-13 10:58:47 +08:00
events.py	[policy in code] part 4	2017-12-01 01:34:59 +08:00
resource.py	[policy in code] part 4	2017-12-01 01:34:59 +08:00
resource_types.py	Add a Blazar Host resource	2019-02-18 06:41:23 +00:00
service.py	[policy in code] part 4	2017-12-01 01:34:59 +08:00
software_configs.py	[policy in code] part 5 (software-*)	2017-12-07 01:11:49 +00:00
software_deployments.py	[policy in code] part 5 (software-*)	2017-12-07 01:11:49 +00:00
stacks.py	Add separate policy for updates with no changes	2019-10-26 00:29:19 -04:00