Plugin uses deprecated v2 api

[carlonnheim]

Hi,

I am not able to get the plugin to use the v3 api. The v2 api is since a while back rate-limited on SAP BTP to move usage away from it. I have installed the most recent cf-cli and plugin.

cf de myapp -v | grep GET gives this output when it is not hitting the rate limit (so it seems to be the usage of the plugin framework itself that visits the v2 api, not the explicitly formed url to fetch the environment)

GET /v2/spaces/<space-guid>/apps?q=name%3A<myapp>&inline-relations-depth=1 HTTP/1.1
GET /v2/apps/<app-guid>/summary HTTP/1.1
GET /v2/apps/<app-guid>/instances HTTP/1.1
GET /v2/apps/<app-guid>/stats HTTP/1.1
GET /v2/stacks/<app-guid> HTTP/1.1
GET /v3/apps/<app-guid>/env HTTP/1.1

Can this be addressed (or if I am doing something wrong please clarify what I need to do to make it switch to v2)? The rate limit on SAP BTP is now down to 50, so it is barely possible to work with the v2 API anymore.

Thanks in advance!
//Carl

[carlonnheim]

Hi, found this discussion and copied parts of the mentioned solution here

I do not have much experience with go, so it probably needs improvement, but at least it made the plugin work again. Hope it helps, thanks!

[davidconvista]

Hello @carlonnheim, how did you manage to modify the code of the plugin? I am trying to do the same in BAS and I can't find the plugin anywhere. Could you please share how you made it work a little bit more on detail?

Thanks a lot!

[carlonnheim]

Hi @davidconvista I pushed the code changes I made to the fork referenced above. Clone that and run go build, that should produce the DefaultEnv binary in the same folder. Install that using cf install-plugin /path/to/DefaultEnv and it should work.

[darmiel]

Thanks, we will take a look!

[darmiel]

Hi @carlonnheim, we have addressed this issue in #8. Would you mind trying the version from that PR to see if it resolves the problem for you and everything is still working as expected? 🙂

[davidconvista]

I just tested the version from the PR and it works as expected and fix the V2 issue. Let's see if @carlonnheim can confirm.

[carlonnheim]

Nice, thanks for the speedy resolution @darmiel , works great when I try it!