Using service containers

I tried out the harden-runner action (based on this repo) and

with:
  egress-policy: audit

and it worked, until I added a PostgreSQL service container to run a few tests. It looks like traffic to that container is blocked? I tried to add

allowed-endpoints: >
  localhost:5432  # `postgres:5432` doesn’t work either

but neither of these two worked. It’s a private organization and I don’t have the privileges to install the app to check the egress audit log.

I disabled the step, and all tests pass just fine. How do you recommend to proceed?

Much thanks!

[jenstroeger]

You should not need any workaround for this to work.

Confirming that the change works.

[varunsh-coder]

This is fixed in the latest release v1.4.5 with tag dd2c410b088af7c0dc8046f3ac9a8f4148492a95. You should not need any workaround for this to work. We have also added an integration test for it. Here is an example workflow run:https://github.com/harden-runner-canary/postgres-testing/runs/7810960312?check_suite_focus=true#step:9:10 and insights URL: https://app.stepsecurity.io/github/harden-runner-canary/postgres-testing/actions/runs/2848365031