aws-cloudformation / aws-cloudformation/cloudformation-coverage-roadmap
[AWS::Events::EventBus] - [BUG] - Policy not recognized by drift detection
- Dominant language
- No language data
- Stars
- 1.1k
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
### Name of the resource
AWS::Events::EventBus
### Resource Name
_No response_
### Issue Description
When running drift detection on an AWS::Events::EventBus resource, the Policy applied to the ‘’actual‘’ configuration should be taken into consideration by drift detection.
Currently, the Policy is not correctly taken by the drift detection, resulting in what appears to be a false-positive drift.
### Expected Behavior
The resource should be in the IN_SYNC state when there is no change.
### Observed Behavior
The resource shows MODIFIED and the 'Policy' property is marked as removed while it exists
### Test Cases
1- Create a resource type AWS::Events::EventBus with 'Policy' property:
```
SampleCustomEventBus:
Type: AWS::Events::EventBus
Properties:
Name: "MyCustomEventBus"
Policy:
Version: '2012-10-17'
Statement:
Sid: Test
Effect: Allow
Principal:
AWS: 'AWS'
Action: events:PutEvents
Resource: 'RESOURCE'
```
2- Perform Drift Detection operation
3- The drift results will show the resource as DRIFTED while there is no change.
### Other Details
_No response_
Contributor guide
Research direction
Start by creating the AWS::Events::EventBus example from the issue and running drift detection. Trace how the Policy property is compared with the actual resource configuration; done means an unchanged policy produces IN_SYNC instead of marking Policy as removed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100