Proposal of new API field: metadata about yield-server

[vrtnd]

Hi, thanks for pointing to the issues.
@slasher125, wdyt?

[0xngmi]

sorry about this, working on a new endpoint but in the meantime you can use https://yields.llama.fi/distinctID for a mapping of old ids to new ids

[0xngmi]

New endpoint: https://yields.llama.fi/poolsOld

[slasher125]

had a chat with @joaoavf on discord. will think how to best address the metadata idea, its very related to the receiptToken ting we were discussing. coming back to this early next week :)

[joaoavf]

Just to give an update on my side. Thanks for the quick response @0xngmi, @slasher125 and @vrtnd 🙏

Issue is solved on my end, currently using https://yields.llama.fi/distinctID

Let me know if I can be helpful. Happy to give details on our use case and contribute with code.

[Amurmurmur]

New endpoint: https://yields.llama.fi/poolsOld

This endpoint, gets redirected to https://defillama-datasets.s3.eu-central-1.amazonaws.com/temp/yields-poolsOld.json
It breaks when fetching in the JS client it throws CORS error

When quering from the browser the https://yields.llama.fi/pools doesnt do it.

[0xngmi]

@Amurmurmur ty for letting us know. I've updated the endpoint to attach appropriate CORS headers and also improved caching, so now requests should be significantly faster.

Please let me know if anything else needs to be changed

[Amurmurmur]

@0xngmi Thank you for a quick respond.
Still redirecting to:
https://defillama-datasets.s3.eu-central-1.amazonaws.com/temp/yields-poolsOld.json

[0xngmi]

the redirect is working as intended, lambdas cant return more than 6MB of data so instead we store the response in s3 and return a redirect to it

[0xngmi]

with the recent changes in our infra now we improved this and we no longer have a redirect, you should get the data right away from the response

closing this issue too since the problem got solved a while ago