This resource will not work with concourse 6.1.0

[jansepke]

As already mentioned in #65 this resource uses a pinnend fly version of 5.3.0 which is outdated but was somehow compatible until concourse 6.0.0. With the latest release of concourse 6.1.0 which introduced a breaking change in the authentication this resource will now stop working.

@vito will there be support for this resource in the future? if not it would maybe be helpful to add a disclaimer to the readme.

[chbiel]

@vito and if it's not supported anymore, can you provide a solution on how to achieve the same result?

[SchmitzChristian]

The latest docker image is not updated since one year, this could help also, after updating fly to 6.1.
The dev images has got fly version 6.0.0, but still not working with this concourse version.

[vito]

Sorry for the lack of updates here y'all. With the advent of the set_pipeline step we've been aiming to deprecate this resource, but it's a total oversight that we didn't see the issues reported on it and see that so many people still rely on it and are waiting for new versions.

I've just shipped v3.0 which has Fly v6.1, but I would strongly recommend you try out the set_pipeline step instead. We switched to it a long while back for our own pipeline automation and it's nice to not have to worry about auth or keeping the version in sync with the Concourse cluster.

If there are limitations to the set_pipeline step that don't let you switch to it right now, please let us know in concourse/rfcs#31 - we don't intend to continue supporting this resource forever. 🙂

[jansepke]

thank you, we were not aware of the set_pipeline step. We integrated it into our pipeline and it works as expected 👍 maybe you want to link it in the readme of this resource.