concourse / concourse-pipeline-resource

!!! use the `set_pipeline` step instead !!!
https://concourse-ci.org/jobs.html#schema.step.set-pipeline-step.set_pipeline
MIT License
76 stars 41 forks source link

fly sync issue #69

Closed nshrest closed 4 years ago

nshrest commented 4 years ago

After the changes introduced to use fly cli 6.1.0, concourse-pipeline resource fails during put operation with error


Logging to /tmp/concourse-pipeline-resource-out.log411759429
2020/05/14 18:26:48 exit status 1 - WARNING:

fly version (6.1.0) is out of sync with the target (5.8.1). to sync up, run the following:

    /opt/resource/fly -t PE sync

error: oauth2: cannot fetch token: 401 Unauthorized
Response: {"error":"invalid_client","error_description":"Invalid client credentials."}```
lukaszzalewski commented 4 years ago

I was able to get around this issue with tag 2.1.1, 2.0.1 also worked when i tested it.

resource_types:
- name: concourse-pipeline
  type: docker-image
  source:
    repository: concourse/concourse-pipeline-resource
    tag: 2.1.1
nshrest commented 4 years ago

I was able to get around this issue with tag 2.1.1, 2.0.1 also worked when i tested it.

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

This totally works ... i was trying that foreever .. but wt i missed earlier is to refly manually to update this change before hand .... Thanks again!