-
Notifications
You must be signed in to change notification settings - Fork 24
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
Add pagination to the hdi and ups commands for environments with hundreds of service instances 😮 #40
Comments
@draschke - tagged as requestor. But please note it might be a few days before I have the bandwidth to look into this item |
I've upped the call page size to 5000 on the hdi and ups command. Should work for you now, although I don't have any environment that has that many services instances to test in. Fix will be in version 2.202105.5 |
Would check for it as soon npm for hana-cli is updated. hana-cli hdi |
New version is available in npm now |
hana-cli status & hana-cli status -a are working. any idea? Connection Problems: Error: Connection Problems: {}
|
Are you logged in with the xs command from the command line? That's the only way I can reproduce that message is if I don't login first with the xs. |
What do you mean by that? No you aren't logged in via xs login?
No that's intentional. I created both the cf and xs utility libraries with the same interface. That way I can have one check and load the specific implementation but keep all the other code working with the libraries the same. |
I'm not logged in via xs login. |
Thank you! It works if I'm logged in via xs. (Works only via xs/cf because Its an xs/cf application construct.) If I create a hdi-container via HANA-Cli there wont be a hdi-service instance created. Right? |
In this instance I'm just reusing the underlying xs/cf client. I didn't want to duplicate the login/credentials handling/storing that xs/cf client is already doing. Therefore I'm just using a child process to launch xs/cf and using the curl command to make requests to the xs/cf API. So this does mean I'm basically just scripting calls through the xs/cf client and that you must already be logged in via the client before this command will work. However I wasn't happy with the error message in this situation. The true error details were getting lost in the call stack. I've made an improvement to make sure those details will now surface up to the user: |
No they won't be there in the hana-cli hdi command. Because this command calls to the xs/cf APIs and only sees the service instances known there. Only the hana-cli containers command would show you the HDI containers created directly via SQL APIs as well. |
Funny, when I was debugging it in the morning and saw this error msg, I thought the same. 😁 Thanks! Makes it much more easier! |
No description provided.
The text was updated successfully, but these errors were encountered: