aws-cloudformation / aws-cloudformation/cloudformation-coverage-roadmap
Condition reference inside RuleCondition in Rule block
- Dominant language
- No language data
- Stars
- 1.1k
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
### Resource Name
CloudFormation Rules Block
### Details
Rule-specific intrinsic function "Condition" cannot be used under Rules block of CloudFormation template.
**Expected Behavior:**
Can reference to a condition since it will return true or false in RuleCondition block for more flexible constraint validation
**Observed Behavior:**
Cannot reference to a condition
**Test case:**
```
Parameters:
Stream:
Type: String
Condition:
Testing: !Equals ['a', 'a']
Rules:
FirstRule:
RuleCondition: !Condition Testing
Assertions:
- AssertDescription: "Must have value"
Assert: !Not
- !Equals [ !Ref Stream, '' ]
```
Contributor guide
Research direction
Start with the CloudFormation Rules Block example in the issue and compare the documented behavior of RuleCondition with the Condition intrinsic function. There are no repository files, tests, or entry points named; done would require confirming whether condition references are supported and documenting or tracking the resulting coverage change.
Written by the indexing model from the issue text.
Assessment
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100