Rabi Mishra d0e44ded0a Use never expiring alarm_url for resource attributes ... Don't use timestamp when generating ec2 signed url for alarm url attributes of resource. This will resolve the issue for new resources even if they are cached in attributes or resource_data. However, for existing stacks containing these resources the current best option is to not cache these attributes and allow alarm resources to be able to get a new never expiring urls in the next forced update. Change-Id: If2ebc3deacb770294004ae023500367af603b59e Task: 39985 Related-Bug: #1872737		2020-06-06 14:02:09 +05:30
..
__init__.py	Move TestInstanceGroup to test_instance_group.py	2014-10-07 12:01:30 +10:00
inline_templates.py	Move all scaling policy tests to autoscaling/	2015-02-04 16:48:59 +10:00
test_heat_scaling_group.py	Use unittest.mock instead of third party mock	2020-05-05 08:42:11 -05:00
test_heat_scaling_policy.py	Use never expiring alarm_url for resource attributes	2020-06-06 14:02:09 +05:30
test_launch_config.py	Use unittest.mock instead of third party mock	2020-05-05 08:42:11 -05:00
test_lbutils.py	Use unittest.mock instead of third party mock	2020-05-05 08:42:11 -05:00
test_new_capacity.py	Move new capacity calculation to scaling library	2015-09-10 21:01:24 +05:30
test_rolling_update.py	Fix scenario names in rolling update test	2015-09-10 10:43:21 -04:00
test_scaling_group.py	Use unittest.mock instead of third party mock	2020-05-05 08:42:11 -05:00
test_scaling_policy.py	Use unittest.mock instead of third party mock	2020-05-05 08:42:11 -05:00
test_scaling_template.py	Fix [H405] pep rule in heat/tests	2015-10-12 14:08:16 +03:00