agentdrew

I had this same request. As a workaround to push the results of the container healthcheck to my container logs I use this container health check command. `"curl -sf "http://127.0.0.1:8080/actuator/health/"...

Another problem with this approach we discovered is we don't get a single log message for the healthchecks, rather it's prepended on the next log message as mentioned by @justas200....

I'm seeing this same behavior when pulling an output from a previous step through `needs` "Context access might be invalid". Is this being triggered by the value not being available...

We started out trying to use this module along with the tf resources to define methods and integrations. The hard requirement to provide the open api spec prevents us from...

Same situation with these config settings. Seems to be any value that expects a boolean. ```branch_deployments: { "env": "ENABLE_BRANCH_DEPLOYMENTS" }``` and ``` code_server_metrics: enabled: { "env": "CODE_SERVER_METRICS_ENABLED" } agent_metrics: enabled:...

I can confirm the issue is still alive and well in `62.13.0`.