cisco-meraki

Use the meraki_config.py script, which snapshots current state, renders a positional diff, and requires confirmation before any PUT. Meraki collection endpoints are full-replacement, so sending a partial rule list deletes everything else — the script makes that accident structurally impossible.

Query the organization configuration change log at /organizations/{id}/configurationChanges, which records admin name, network, old and new values. It retains up to 365 days of history, much longer than the 31-day ceiling on most other timespan endpoints.

Combined networks require an explicit productType parameter on the event log endpoint; omitting it returns a 404 that looks like the network does not exist. The client catches this and reports which product types the network actually has.

No. Scope is limited to MX security appliances, MS/Catalyst switches, and MR wireless access points. MV cameras, MT sensors, and Systems Manager endpoints are explicitly out of scope.

The API allows 10 requests per second per organization and returns 429 with a Retry-After header. The HTTP layer honors Retry-After and backs off exponentially with jitter; running parallel invocations is discouraged because the limit is server-side per org.

Yes. Every apply writes a snapshot of the prior state to the gitignored .meraki-snapshots directory, and the rollback command re-PUTs that payload through the same diff-and-confirm gate. Snapshots retain secrets like VPN PSKs so rollback restores working state.