Closed r-heimann closed 3 months ago
What rain command is causing this?
We are using
rain deploy <Template> <Stackname> --config <Parameters> --termination-protection --yes
This is a weird one. There is no difference, as far as YAML is concerned, between those two.
This commit might be what broke it. I had to change that to fix a different bug in the formatter, to keep the styling consistent.
The problem is that the schema uses what is essentially a reserved word in YAML, OFF means the node is a boolean, not a string.
"FlexibleTimeWindowMode": {
"type": "string",
"description": "Determines whether the schedule is executed within a flexible time window.",
"enum": [
"OFF",
"FLEXIBLE"
]
},
It should have been modeled as "DISABLED" or something like that to avoid clashing with the boolean aliases.
I will likely need to hack the formatter so that in this one case, we output "OFF" instead of OFF.
Hi,
updated
rain
from v1.7.5 to v1.8.1, it now causesAffected CloudFormation Resource:
AWS::Scheduler::Schedule
Example:rain 1.8.1 artifact:
rain 1.7.5 artifact:
The Documentation is also unclear what exacly they want for values: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-scheduler-schedule-flexibletimewindow.html