Rabi Mishra eb8bfd530b 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 (cherry picked from commit d0e44ded0a)		2020-06-25 11:46:04 +05:30
..
aws	Use never expiring alarm_url for resource attributes	2020-06-25 11:46:04 +05:30
openstack	Use never expiring alarm_url for resource attributes	2020-06-25 11:46:04 +05:30
__init__.py	Log missing clients as WARNING instead of ERROR	2016-08-16 16:27:55 -05:00
alarm_base.py	Update incorrect timezone description	2017-09-19 13:46:32 +08:00
scheduler_hints.py	Fix path_in_stack for scheduler hints	2016-08-05 10:21:10 +00:00
server_base.py	Add dedicated auth endpoint config for servers	2019-07-12 13:50:38 +00:00
signal_responder.py	Use never expiring alarm_url for resource attributes	2020-06-25 11:46:04 +05:30
stack_resource.py	Revert "Use OutputDefinition to generate attributes schema"	2018-11-28 12:13:58 -05:00
stack_user.py	Remove log translations	2017-03-25 17:11:50 +08:00
template_resource.py	Revert "Use OutputDefinition to generate attributes schema"	2018-11-28 12:13:58 -05:00
volume_base.py	Check for server in attachements when checking for detach complete	2018-09-24 17:28:52 +05:30
wait_condition.py	Don't store signal_url for ec2 signaling of deployments	2020-06-25 11:45:49 +05:30