Paweł Rein

For me this error was happening due to `packages` permission missing from the job

Should it be possible to use `credential_source` to get the cred from env vars instead of `source_profile`? Is it related to https://github.com/aws/aws-cli/issues/3875 ?

@gdenn Did you find any good way to workaround the lack of that feature? I would be interested to learn about it as I'm dealing with the same problem.

I run into the same issue. I would help perhaps if I could pass the version to install to the action

@mubarak-j shared a more sophisticated healthcheck workaround in the [comment here](https://github.com/argoproj/argo-cd/discussions/7936#discussioncomment-2267954), pasting below: ``` resource.customizations.health.autoscaling_HorizontalPodAutoscaler: | hs = {} if obj.status ~= nil then if obj.status.conditions ~= nil then for...

@mubarak-j thanks for answering! Looking into the blog post, I'm not sure what "In the upcoming release, the resource.customizations key has been deprecated in favor of a separate ConfigMap key...

> 2\. If a user provides a `_TOKEN`, why would we want to try ssh verification first? In CircleCI, for example, environment variables can be shared across projects using contexts....

Thanks @janisz. I understand and agree with your concern about backward compatibility. Perhaps adding additional label and making the code ignore the "old" one when the "new" one is found...

without diving too deep in the thread, is there a recommended workaround?

Consider also yaml anchors (if you didn't already) Example: ``` name: Test on: push jobs: test1: runs-on: ubuntu-latest steps: - &run_action name: Run my-action uses: my-organization/my-action@main test2: runs-on: ubuntu-latest steps:...