-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Get Shopify connector on Cloud #8633
Comments
waiting for New OSS Release
|
@bazarnov do you need something from me to update the version available in airbyte-cloud to get the oauth application approved from shopify? |
For now we're good to go without you involved in this.
All the rest: python, java parts are ready and merged into master already. |
@bazarnov thanks for the context! Just FYI make sure not to merge the full connector to Cloud master branch or it will become available in prod before it's ready :) so you should deploy from a branch to allow the shopify team to review |
@sherifnada I'm stuck on the testing, waiting for new Release of OSS, current one |
There is an error with Airbyte-Cloud deploy on The error while OSS Version works good, both OAuth2.0 & API Keys (any connector).
Need advice, where to look at to find the problem? Possible PR causes the issue: |
Issue is fixed with UPDATE: |
@bazarnov opening this issue since it covers the scope of in progress work as well |
Yes, thanks. We are ready to be tested on https://dev.airbyte.ga/ BTW. |
@sherifnada @bazarnov Currently we have some problems on getting our app on marketplace.Here is an answer from Shopify: _Our records show that on multiple occasions you’ve submitted an app that doesn’t meet Shopify’s public app requirements. As a result, you’ve been temporarily suspended from submitting new apps until March 01, 2022. You can re-submit your app when the suspension period is over. Please be sure that you have updated it to meet all the requirements for public apps before doing so. Required changes |
@ycherniaiev does not being in the marketplace prevent us from having a public app? The latter is important, the former is not |
@ycherniaiev what is the status of getting shopify into cloud? This is blocking for Beta certification |
@bazarnov any insight on the above? |
@sherifnada Marketplace does not prevent from having public app.But asa far as our competitors do not have app on marketplace we decided that in perspective it will be a good point. |
@bazarnov I'm seeing shopify in cloud, does that mean it's fully ready for production use by customers? |
had offline discussion: the issue is that we currently allow API key signin via cloud. This caused shopify to reject/suspend our oauth application. Instead, they want us to allow only oauth. @ycherniaiev, I will reach out once we disable API key signin on cloud. once we do that, could you let change the URL we use to submit the App to them to use only cloud.airbyte.io ? |
@sherifnada Nice! 1 March suspension is over but before that i will prepare all links and descriptions for Shopify |
@ycherniaiev pleaae hold off on submitting for verification as we first need to disable API key auth for Shopify in cloud |
Do we have to do something with this, like remove this option from the spec? |
no we will do this in a custom way for cloud via this ticket #10381 |
FYI disabling shopify in cloud via this PR #10783 for now |
Hi! We want to connect to Shopify data, and I see there haven't been many updates for a while on this ticket. Is there a rough estimate of when this will become available in the Clou version? |
Duplicates: #11241 |
think the issue is that we need to redirect the user to {shop_id}.shopify.com for consent instead of whatever we do now, this was recently added as part of https://github.com/airbytehq/airbyte-internal-issues/issues/322. So there will be a java component here as well and a python/connector component to modify the spec to use the new oauth spec
Based on priorities here, key targets are Google Sheets and Shopify. Other connectors will be benched for now.
The text was updated successfully, but these errors were encountered: