Skip to content
This repository has been archived by the owner on Apr 30, 2021. It is now read-only.

concourse-operator: updates for concourse v6.6.0 #1200

Merged
merged 6 commits into from
Oct 14, 2020
Merged

Conversation

chrisfarms
Copy link
Contributor

What

Resolves authentication issues between the concourse-operator and concourse API for v6.6.0

  • Updates concourse libraries
  • Updates go version used (required by lib upgrade)
  • Tweaks some functions, tests and unmarshalling inline with new lib version
  • Changes the authentication to use the correct token

Notes

  • Validation of pipelines appears to be stricter (better) than previously, it caught a few causes where it hadden before ... including pipelines in sandbox

chrisfarms added 6 commits October 14, 2020 17:07
we updated the concourse version and need to keep the library version
used by the operator in sync
some of the latest versions of dependencies require go1.13+ (as they
rely on additions to the errors packages).
adds an environment variable that can be used to turn on the verbose
http client logging from the concourse client lib. this can be useful to
see more details about where a request is failing to concourse
the way pipeline validation is performed has changed in recent version
of the concourse libraries ... this makes it compatible

the new validation also appears to be better at catching issues and
raised a couple of problems with our tests which are resolved here by
fixing the pipeline inputs to be valid when they should be

manually using yaml.Unmarshal also no longer appears to produce a valid
atc.Config struct ... so we switch to the built in unmarshaller
the function signature for CreateOrUpdatePipeline has changed ... update
it for compatibility with latest libs
it appears we were pulling the id-token from the JWT token response and
using it as the bearer token for the client. I'm not sure why we were
doing this, but it appears to have been introduced shortly after the
concourse authentication changes in v6.2. I suspect whatever the
original problem was has not been fixed, and so we ended up using the
wrong token after the upgrade to 6.6.

using the standard AuthToken response resolves our current issues with
the password authenticate for the operator not working against v6.6

this change likely makes the operator no-longer compatible with versions
prior to 6.6
Copy link
Contributor

@szd55gds szd55gds left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks ok and I paired on some of it.

@chrisfarms chrisfarms merged commit 83219bb into master Oct 14, 2020
@chrisfarms chrisfarms deleted the update-conc-op-6-6 branch October 14, 2020 16:34
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants