Feature Request for Puritan Heroes — Manage snapshot schedules directly in Pure1

An opportunity to shine 

Summary / problem

Today, snapshot scheduling and edits are performed per-array (e.g., via Purity protection policies / groups). At fleet scale this is manual, slow for change control, and hard to audit centrally. We’d like first-class, Pure1-native capabilities to create, modify, and bulk-apply snapshot schedules—without logging into each array.

Impact / why this matters

• Fleet operations: one place to set/adjust RPO/retention across many FlashArrays/FlashBlades.
• Change management & compliance: audited, role-scoped changes with approver workflow.
• Risk & capacity: pre-change impact analysis (capacity, performance) using Pure1 telemetry.
• Consistency: policy templates and guardrails reduce configuration drift.

Scope (initial ask)

1. Pure1 UI

• “Snapshot Policies” workspace to create/edit/delete schedules and retentions (minute/hour/day/week/month), including SafeMode/immutability options where supported.
• Bulk Apply/Override to multiple arrays, volume groups, file systems/shares.
• What-if capacity forecast prior to save (based on Pure1 analytics).
• Change review & approvals (optional), with rationale and ticket ID fields.
• Maintenance/blackout windows and exceptions.
• Full audit trail (who, what changed, before/after, when, target objects).
• RBAC: granular rights (view vs. edit vs. approve), and per-array or per-group scoping.

1. Pure1 Public API

• New endpoints to programmatically create/read/update/delete snapshot policies, bind/unbind them to objects, run an on-demand snapshot from a policy, and pull audit events—so we can integrate with CI/CD and ITSM. (We rely on Pure1 API today for telemetry; adding write ops for policies would unlock safe automation.)

1. Edge / connectivity

• Use Pure1 Edge Service for secure, two-way execution on arrays. Include graceful handling for dark/offline assets (queue and notify).

Acceptance criteria (examples)

• From Pure1, I can create a policy “gold-daily-35d” and attach it to 100+ arrays / 1,000+ objects in a single operation.
• A non-admin can propose a policy change; an approver must OK it before it takes effect.
• Audit page shows a human-readable diff (before/after crontab-style schedule and retention) plus API payloads.
• Capacity impact estimator shows expected snapshot object growth over 30/90 days based on historical change rates.
• API: POST /snapshot-policies, PATCH /snapshot-policies/{id}, POST /snapshot-policy-attachments, GET /audit-events?type=snapshot_policy.

Nice-to-haves

• Prebuilt policy templates (e.g., 15-min RPO for 24h + daily 35d + monthly 12m).
• Guardrails (“warn/deny if estimated growth > X TB or RPO < Y min”).
• Service-now/Jira webhook on approval/change.

Environment
Mixed FA/FB fleet; Pure1 connected, Edge Service available. SafeMode enabled on arrays requiring immutability.

Thanks in advance - Garry Ohanian