Follow-up: keep getAddOnPurchase endpoint support in Duo Usage page
What does this MR do and why?
This MR is a follow-up of Support multiple Duo add-on tiers in Duo manage... (!160561 - merged), which swaps usage of the getAddOnPurchase
endpoint for the newer getAddOnPurchases
. Here, we re-introduce getAddOnPurchase
in parallel to getAddonPurchases
, in order to gracefully degrade due, so we can keep multi-version compatibility.
Context: !160561 (comment 2025278675)
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
No visual changes expected.
How to set up and validate locally
CI pipeline should continue to pass.
Manual verification can be done by altering the query variables - for example, by setting namespaceId
to 99999
here.
Edited by Mohamed Moustafa