#84 Fix issue with checking ecs exec when aws guardduty is enabled, when it is enabled by default there is no managedAgents key, so array is null, and it results in jq: error (at <stdin>:175): Cannot iterate over null (null) #85
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… is enabled, when it is enabled by default there is no managedAgents key, so array is null, and it results in jq: error (at <stdin>:175): Cannot iterate over null (null)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #84, if available:
Description of changes:
Added default empty array return for managedAgents when checking for agensStatus array, since error occurs when you have enabled AWS Guard Duty agent being attached to ECS.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.