Clarification on Developer Portal Backup and Restore Behavior with capture.js and generate.js

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:

1. Items from the backup (snapshot) are restored to the target developer portal.
2. If a key from the backup matches an existing key in the destination, the corresponding item is overridden.
3. 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

Start by reading the capture.js and generate.js scripts and any documentation describing Developer Portal backup and restore behavior. Confirm whether unmatched destination items are intentionally retained and whether an option exists to remove them; document the answer and the expected restore semantics if the project maintains relevant guidance.

Written by the indexing model from the issue text.