Graphqa api changes

[kirillbilchenko]

After today github release the id field is now changing the format, so resource is returning error running command: illegal base64 data at input byte 2
https://docs.github.com/en/graphql/reference/objects#release

[xtremerui]

Hi could you add a link to the github graphql change log please? Thx!

[qvistgaard]

@xtremerui it's not included in the changelog. the databaseId was added here:

https://docs.github.com/en/graphql/overview/changelog#schema-changes-for-2021-06-07

But if you look at the graphql api documentation the id field is not even mentioned: https://docs.github.com/en/graphql/reference/objects#release

it is wierd though because it is mentioned in the scalars, and described as a base64 encoded string, but if you look at the api it's no longer that.

[kirillbilchenko]

@xtremerui I'm not sure how helpful will be this, but github_communtiy there is an answer about the id, and it was working for some time, until today when I was working on this graphql client the databaseId field was not yet available. Github release new enterprise server version yesterday, so most probably prod were also updated the link on release notes https://docs.github.com/en/enterprise-server@3.1/admin/release-notes

[kirillbilchenko]

@xtremerui one more small note, we already build the image of updated resource and replaced the build in github-release resource inside worker, and now it's working fine on our side.

[xtremerui]

I am wondering the circumstance of using databaseId or ID.

The changes here shows it should use databaseId when it is available, if not it will try to fall back to ID. So I am looking for the offical doc about the relationship between these two fields.

Also, the way we decodes the ID field hasn't changed. So I am a bit confused on the id field is now changing the format part.

[kirillbilchenko]

I am wondering the circumstance of using databaseId or ID.

The changes here shows it should use databaseId when it is available, if not it will try to fall back to ID. So I am looking for the offical doc about the relationship between these two fields.

Also, the way we decodes the ID field hasn't changed. So I am a bit confused on the id field is now changing the format part.

This one I left so self-hosted installation, not sure when the databaseId field was introduced, so before today old id was working just fine, I kept it as a fallback in case of someone is using the old version where there is no datatabaseId field.

[techgaun]

any chance we are going to get this pushed out to docker hub? I only saw dev and dev-ubuntu tag from today.

[xtremerui]

@techgaun just cut a new release. it should be up now.

[adamdossa]

Apologies for the noob question - our concourse pipeline is failing with:

check failed
run check step: run check step: check: resource script '/opt/resource/check []' failed: exit status 1

stderr:
�[31merror running command: illegal base64 data at input byte 2
�[0m

I can see a fix has been pushed for the github-release resource, but wondering how to force our concourse instance to pick up the new version?

[xtremerui]

@adamdossa add the following custom resource type to your resource_types: section so it can overwrite the default one that is failing

- name: github-release
  type: registry-image
  source: {repository: concourse/github-release-resource}