Trying to create a Heat/Newton stack that uses OS::Monasca::Notification, I receive the error message:
{
"code": 400,
"error": {
"message": "Address \"\" doesn't have required URL scheme",
"traceback": null,
"type": "StackValidationFailed"
},
"explanation": "The server could not comply with the request since it is either malformed or otherwise incorrect.",
"title": "Bad Request"
}
This used to work on Heat/Mitaka.
I could track where the Heat server is making this validation, and it complains that the address string passed to OS::Monasca::Notification is empty. Well, this will be the case when you define the notification as an OS::Heat::ScalingPolicy, if you're trying to use Monasca alarms to autoscale! On Validation scope this string will be empty.
This commit introduced the problematic validation:
https://github.com/openstack/heat/commit/e3cc29c4e20bcbfc5597ace7b17fce924b6c6801
Here is an excerpt of how we're using OS::Monasca::Notification:
...
scale_up_policy:
type: OS::Heat::ScalingPolicy
properties:
adjustment_type: change_in_capacity
auto_scaling_group_id: { get_resource: group }
cooldown: 60
scaling_adjustment: 1
scale_down_policy:
type: OS::Heat::ScalingPolicy
properties:
adjustment_type: change_in_capacity
auto_scaling_group_id: { get_resource: group }
cooldown: 60
scaling_adjustment: -1
# -- Monasca --
up_notification:
type: OS::Monasca::Notification
properties:
type: webhook
address: {get_attr: [scale_up_policy, alarm_url]}
down_notification:
type: OS::Monasca::Notification
properties:
type: webhook
address: {get_attr: [scale_down_policy, alarm_url]}
...
A complete Heat template example that would display the problems with this validation method can be found here:
https:/