Skip to content

#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

Open
tskorupka wants to merge 1 commit into
aws-containers:mainfrom
tskorupka:bugfix/fix-issue-with-checking-ecs-exec-when-aws-guardduty-is-enabled
Open

#84 Fix issue with checking ecs exec when aws guardduty is enabled, w…

88a6c1a
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Nov 13, 2025 in 1s

1 potential rule

Rule: Merge on CI success and review approval (merge)

  • #approved-reviews-by>=1
  • any of: [🛡 GitHub branch protection]
    • check-neutral = shellcheck
    • check-skipped = shellcheck
    • check-success = shellcheck
  • #changes-requested-reviews-by=0
  • #commits-behind = 0 [🛡 GitHub branch protection]
  • -closed
  • -closed [📌 merge requirement]
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • -merged
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed

Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com