Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Linting Rule: Invalid EngineVersion on ElastiCache cluster #3820

Closed
2 tasks
DeflateAwning opened this issue Nov 11, 2024 · 0 comments · Fixed by #3824
Closed
2 tasks

Linting Rule: Invalid EngineVersion on ElastiCache cluster #3820

DeflateAwning opened this issue Nov 11, 2024 · 0 comments · Fixed by #3824

Comments

@DeflateAwning
Copy link

DeflateAwning commented Nov 11, 2024

Is this feature request related to a new rule or cfn-lint capabilities?

rules

Describe the feature you'd like to request

I want the invalid redis version (i.e., the patch version is specified) to be added as a rule:

  RedisCluster:
    Type: AWS::ElastiCache::CacheCluster
    # Deletion is the default policy.
    DeletionPolicy: Delete
    UpdateReplacePolicy: Delete
    Properties:
      Engine: redis
      CacheNodeType: cache.t4g.micro
      # RELATED TO ISSUE: Do not include patch versions in the EngineVersion (because it's invalid).
      EngineVersion: 7.1 # 7.1.0 is invalid.
      NumCacheNodes: 1
      ClusterName: "cluster-name"
      VpcSecurityGroupIds:
        - !Ref RedisSecurityGroup
      CacheSubnetGroupName: !Ref RedisSubnetGroup

Describe the solution you'd like

The code snippet above should induce a linting error.

Additional context

Just wasted 10 minutes on a deployment because of this.

Is this something that you'd be interested in working on?

  • 👋 I may be able to implement this feature request

Would this feature include a breaking change?

  • ⚠️ This feature might incur a breaking change
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant