You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Writing to seek clarification regarding the expected behavior of the capture.js and generate.js scripts provided for managing Azure API Management Developer Portals.
From our testing, we observed that during the restore process:
Items from the backup (snapshot) are restored to the target developer portal.
If a key from the backup matches an existing key in the destination, the corresponding item is overridden.
Items present in the destination but not in the backup are left untouched.
This behavior aligns with our understanding that the scripts are designed to copy or override items as specified by their keys, without removing unmatched items in the destination.
Could you confirm if this is the intended behavior, or if there is an option to ensure that the destination mirrors the backup entirely, including removing items not present in the backup? We want to ensure our use of the scripts aligns with their design and purpose.
Thank you for your assistance.
Best regards,
Alejandro
The text was updated successfully, but these errors were encountered:
Writing to seek clarification regarding the expected behavior of the capture.js and generate.js scripts provided for managing Azure API Management Developer Portals.
From our testing, we observed that during the restore process:
This behavior aligns with our understanding that the scripts are designed to copy or override items as specified by their keys, without removing unmatched items in the destination.
Could you confirm if this is the intended behavior, or if there is an option to ensure that the destination mirrors the backup entirely, including removing items not present in the backup? We want to ensure our use of the scripts aligns with their design and purpose.
Thank you for your assistance.
Best regards,
Alejandro
The text was updated successfully, but these errors were encountered: