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

CKV_AWS_361 get_evaluated_keys() returns a string instead of list #6932

Open
nb-sf opened this issue Jan 3, 2025 · 0 comments · May be fixed by #6929
Open

CKV_AWS_361 get_evaluated_keys() returns a string instead of list #6932

nb-sf opened this issue Jan 3, 2025 · 0 comments · May be fixed by #6929
Assignees
Labels
checks Check additions or changes

Comments

@nb-sf
Copy link

nb-sf commented Jan 3, 2025

Describe the issue

  • CKV_AWS_361 get_evaluated_keys returns a single string

Examples

...
                "check_id": "CKV_AWS_361",
                "bc_check_id": null,
                "check_name": "Ensure that Neptune DB cluster has automated backups enabled with adequate retention",
                "check_result": {
                    "result": "FAILED",
                    "evaluated_keys": "backup_retention_period"
                },
                ...

-vs-

...
                "check_id": "CKV_AWS_101",
               "bc_check_id": null,
               "check_name": "Ensure Neptune logging is enabled",
               "check_result": {
                   "result": "FAILED",
                   "evaluated_keys": [
                       "enable_cloudwatch_logs_exports"
                   ]
               },
....

Version (please complete the following information):

Additional context

  • This policy currently returns a string for get_evaluated_keys(), where the convention in the base_check is to return a list.
@nb-sf nb-sf added the checks Check additions or changes label Jan 3, 2025
@tsmithv11 tsmithv11 linked a pull request Jan 3, 2025 that will close this issue
5 tasks
@tsmithv11 tsmithv11 self-assigned this Jan 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
checks Check additions or changes
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants