You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 13, 2021. It is now read-only.
Deployed via concourse helm chart, added a pipeline to set a pipeline from a yaml in a mount point, but the worker is throwing the following for the job:
{"timestamp":"2019-06-04T06:44:52.891945787Z","level":"error","source":"guardian","message":"guardian.api.garden-server.get-property.failed","data":{"error":"property does not exist: concourse:resource-result","handle":"8af14252-4e9a-4264-7cb9-d916ee0f59ff","session":"3.1.236"}}
Pipeline after pulling states the following:
Logging to /tmp/concourse-pipeline-resource-out.log25509096
I can't see any other details on this. Can't find the log in the worker either.
The error log you're seeing is actually innocuous and is logged all the time - unfortunately it's logged by a dependency so we can't easily silence it (without a PR upstream anyway).
At the moment you have to configure a local user - oAuth doesn't work. It's kind of a pain in the butt. I would recommend just configuring a generated username/password for the resource to use.
Deployed via concourse helm chart, added a pipeline to set a pipeline from a yaml in a mount point, but the worker is throwing the following for the job:
Pipeline after pulling states the following:
I can't see any other details on this. Can't find the log in the worker either.
This is the file I used:
The text was updated successfully, but these errors were encountered: