Hi all,

the AWS::CloudFormation::WaitCondition resource in Heat allows to update
the 'count' property, although in real AWS this is prohibited (

My question is does TripleO still depends on this behavior of AWS
WaitCondition in any way? I want to be sure that fixing the mentioned bug
will not break TripleO.

Best regards,
Pavlo Shchelokovskyy.
OpenStack-dev mailing list

Reply via email to