Skip to content
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

When using the CLI flow for an existing application, you can only select from the first five pages of apps in your partner dashboard #317

Closed
greenlemur opened this issue Aug 18, 2022 · 5 comments · Fixed by #762
Assignees

Comments

@greenlemur
Copy link

Problem:

When using the CLI flow for an existing application, you can only select from the first five pages of apps in your partner dashboard

Screen Shot 2022-08-18 at 1 26 46 PM

^ You can only go as far down as the first five pages of apps in your partner dashboard. Anything beyond that will not show up in the terminal as an option to choose from. We have 11 pages of apps in our partner account (partner ID: 1362879).

@alvaro-shopify
Copy link
Contributor

alvaro-shopify commented Aug 22, 2022

Hi!. Thank you for opening this question. Now, when a select prompt is shown and there are more than 10 options to select from, the list allows pagination to show more items. When you reach the last item of the list it is going to scroll down. Besides you could also use the autocomplete feature to search for the correct app typing the first characters of its name.
Please let me know if these tips solve your problem and any suggestions to improve will be welcome.

@alvaro-shopify alvaro-shopify self-assigned this Aug 22, 2022
@amcaplan
Copy link
Contributor

@alvaro-shopify I think this is a legit issue. We only retrieve the first 100 apps for the organization, there's no pagination beyond that.

@amcaplan
Copy link
Contributor

@greenlemur thanks for bringing this case to our attention. Until it's solved, I believe there is a workaround, at least for dev. If you open your app's page in the admin, you'll see the API key. Copy that key, and pass it to the command using the flag --api-key=YOURAPIKEY.

There is no such flag for deploy but we've considered adding once, here's another reason to push in that direction. /cc @isaacroldan

@isaacroldan
Copy link
Contributor

Yes, using the --api-key flag is the best (or only) workaround for this. @amcaplan not sure why we don't have this flag for deploy but I think we should!
Maybe create a ticket for the next cycle?

@amcaplan
Copy link
Contributor

amcaplan commented Sep 6, 2022

@greenlemur I know it isn't the best solution, but for now note that support for the --api-key flag in deploy has been merged and released in the latest version, 3.10.0. So you have a solid workaround for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants