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

LogGroup: incorrect resource schema #34

Closed
miparnisari opened this issue May 4, 2020 · 1 comment
Closed

LogGroup: incorrect resource schema #34

miparnisari opened this issue May 4, 2020 · 1 comment

Comments

@miparnisari
Copy link
Contributor

Current properties according to the schema:

"LogGroupName": {
"description": "The name of the log group. If you don't specify a name, AWS CloudFormation generates a unique ID for the log group. ",
"type": "string",
"minLength": 1,
"maxLength": 512,
"pattern": "^[.\\-_/#A-Za-z0-9]{1,512}\\Z"
},
"RetentionInDays": {
"description": "The number of days to retain the log events in the specified log group. Possible values are: 1, 3, 5, 7, 14, 30, 60, 90, 120, 150, 180, 365, 400, 545, 731, 1827, and 3653.",
"type": "integer",
"enum": [
1,
3,
5,
7,
14,
30,
60,
90,
120,
150,
180,
365,
400,
545,
731,
1827,
3653
]
},
"Arn": {
"description": "The CloudWatch log group ARN.",
"type": "string"
}

But according to the service API, CreateLogGroup also accepts:

  • kmsKeyId
  • tags
@PatMyron
Copy link

PatMyron commented May 6, 2020

more accurately genuine CloudFormation coverage gaps than an incorrect resource schema:
aws-cloudformation/cloudformation-coverage-roadmap#77
aws-cloudformation/cloudformation-coverage-roadmap#128

@PatMyron PatMyron closed this as completed May 6, 2020
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

No branches or pull requests

2 participants