Ahson Khan

Here's the gist with the design of a solution for this: https://gist.github.com/ahsonkhan/d6c4d3a9780bb058a729b76844923ef1

If we are to have install instructions within our release notes, they need to be actionable. Re-opening.

We still want to do this. Currently this is a manual process: https://github.com/Azure/azure-sdk-for-cpp/pull/5405

Office hour discussion conclusion across languages: https://github.com/Azure/azure-sdk-for-cpp/issues/5116#issuecomment-1832731537

This change is addressed in C++, and similar changes can be made in other languages. **The gist is:** - We want to parse and use the new `expires_on` field if...

C++ issue for tracking: https://github.com/Azure/azure-sdk-for-cpp/issues/5279

Related issues: https://github.com/actions/runner-images/issues/6376 https://github.com/microsoft/vcpkg-tool/commit/0cba610af71441e734ec8a13ac29670fdbc092ed

Reading it from a file within cmake is doable (https://cmake.org/cmake/help/latest/command/file.html), but the issue is with updating that same string within the "builtin-baseline" property within the `vcpkg.json` file. As an aside,...

> we'll have to add our own retry policy. Where are you planning to use it and hook it up to the HTTP pipeline? I don't see this new `StorageRetryPolicy`...

That's a great catch! I am curious, how did you discover this? Did you actually hit the endless loop, in your use case?