aws-cloudformation / aws-cloudformation/cloudformation-coverage-roadmap

[AWS::Scheduler::Schedule] - [BUG] - False-positive drift for the CFN Resource

Open
#1,725 6 comments 11 reactions 0 assignees View on GitHub
bug
Dominant language
No language data
Stars
1.1k
Forks
62
PR merge metrics
No merged PRs in 30d

Description

### Name of the resource

AWS::Scheduler::Schedule

### Issue Description

When creating a `AWS::Scheduler::Schedule` in `eu-central-1` using

```yaml
Schedule:
Type: AWS::Scheduler::Schedule
Properties:
ScheduleExpression: "rate(5 minutes)"
ScheduleExpressionTimezone: "Europe/Berlin"
FlexibleTimeWindow:
Mode: "OFF"
State: "ENABLED"
Target:
Arn: !GetAtt LambdaFunction.Arn
RoleArn: !GetAtt ScheduleRole.Arn
```

it will cause a drift:

Logical ID | Physical ID | Type | Drift status | Timestamp | Module
-- | -- | -- | -- | -- | --
Schedule | Schedule-4R77P4CM01UD | AWS::Scheduler::Schedule | DELETED | 2023-06-26 07:40:05 UTC+0200 | -

### Expected Behavior

Drift is recognizing the AWS Resource.

### Observed Behavior

Is it showing up as a false positive drift in CloudFormation.

### Test Cases

```yaml
Schedule:
Type: AWS::Scheduler::Schedule
Properties:
ScheduleExpression: "rate(5 minutes)"
ScheduleExpressionTimezone: "Europe/Berlin"
FlexibleTimeWindow:
Mode: "OFF"
State: "ENABLED"
Target:
Arn: !GetAtt LambdaFunction.Arn
RoleArn: !GetAtt ScheduleRole.Arn
```

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the YAML AWS::Scheduler::Schedule example in eu-central-1 and run CloudFormation drift detection. Compare the deployed schedule with the stack resource, focusing on the DELETED result; done means the existing resource is recognized without a false-positive drift.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
cloud, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.