Property Does Not Exist: Concourse:Resource-Result

DandyDeveloper commented 5 years ago

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.

This is the file I used:


resource_types:
- name: concourse-pipeline
  type: docker-image
  source:
    repository: concourse/concourse-pipeline-resource
    tag: 2.1.1

resources:
- name: my-pipelines
  type: concourse-pipeline
  source:
    teams:
    - name: main

jobs:
- name: set-my-pipelines
  plan:
  - put: my-pipelines
    params:
      pipelines:
      - name: alertd
        team: main
        config_file: /pipelines/pipeline.yaml

DandyDeveloper commented 5 years ago

Further look into this, two things:

Need to ensure you have a user/password for basic auth. You cannot use this without basic auth.

Then ensure the user is a member of the team.

What's the best practice for this if you're using OAuth providers?

Do you just have a secret user/pass that only this pipeline would use?

vito commented 5 years ago

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.

concourse / concourse-pipeline-resource

Property Does Not Exist: Concourse:Resource-Result #61