Shopify api versioning


The latest release of shopify’s API (2022-10) requires that the shopify app you are using meets certain requirements as explained here:

If your app doesn’t meet these requirements, you will see an error such as:

    "errors": "[API] This app is not approved to access REST endpoints with protected customer data"

As per the docs, all apps must meet the requirements by July 1, 2023.
I can see in source-shopify that the api version gets hardcoded to 2022-10.
I’m curious what airbyte’s stance is on making this a variable that defaults to the latest version (2022-10) but also allows an override to be passed in (via the config maybe?).

This would allow the latest version of the shopify source to work in the meantime while apps are in the process of being updated to meet the requirements set out in the docs linked above. We are currently going through the process to update our app at the moment but would also like to use the latest version of the airbyte connector.

As it currently stands, this PR is a breaking change I believe for this reason? Should the semantic versioning have been different here?

I’m happy to open a PR to make the api version configurable but wanted to check first that i’m not missing something.

Hello there! You are receiving this message because none of your fellow community members has stepped in to respond to your topic post. (If you are a community member and you are reading this response, feel free to jump in if you have the answer!) As a result, the Community Assistance Team has been made aware of this topic and will be investigating and responding as quickly as possible.
Some important considerations that will help your to get your issue solved faster:

  • It is best to use our topic creation template; if you haven’t yet, we recommend posting a followup with the requested information. With that information the team will be able to more quickly search for similar issues with connectors and the platform and troubleshoot more quickly your specific question or problem.
  • Make sure to upload the complete log file; a common investigation roadblock is that sometimes the error for the issue happens well before the problem is surfaced to the user, and so having the tail of the log is less useful than having the whole log to scan through.
  • Be as descriptive and specific as possible; when investigating it is extremely valuable to know what steps were taken to encounter the issue, what version of connector / platform / Java / Python / docker / k8s was used, etc. The more context supplied, the quicker the investigation can start on your topic and the faster we can drive towards an answer.
  • We in the Community Assistance Team are glad you’ve made yourself part of our community, and we’ll do our best to answer your questions and resolve the problems as quickly as possible. Expect to hear from a specific team member as soon as possible.

Thank you for your time and attention.
The Community Assistance Team

Hello Philip, sorry the delay to reply. Usually Airbyte tries to not make the API version configurable because it can add backwards compability (removing/adding new streams, changing endpoints or requests). I would be nice to create a Github issue to better discuss with the engineer the best path to improve the experience here.

Hi Marcosmarxm, I’ve created the issue here. Thanks!