# Resource ownership + in-place updates for provisioned resources

> ZopNight now derives the owner of each resource from cloud activity logs (CloudTrail, GCP Audit Logs, and Azure Activity Logs), so 'who created this?' is answerable in showback without digging through logs by hand. ZopDay adds in-place updates and cross-VPC connections for provisioned databases and clusters, and discovery now survives pod failures.

Source: https://zop.dev/changelog/v1-4-0
Published: 2026-05-04 · Tags: zopnight, zopday, showback, provisioning

---

Know who created every resource.

## New

- ZopNight: resource ownership: the IAM principal that originally created each resource is derived from CloudTrail (AWS), Audit Logs (GCP), and Activity Logs (Azure), separating humans from service accounts and feeding owner / team accountability into showback
- ZopDay: change tier, storage, scaling, and backup retention on RDS, ElastiCache, EKS node groups, Cloud SQL, Memorystore, GKE node pools, Azure SQL / MySQL / Postgres, Azure Redis, and AKS in place, without recreating anything

## Improved

- ZopDay: connect a datastore to a cluster across VPCs: ZopDay auto-creates and accepts VPC peering, adds reciprocal routes, and opens a narrow port-scoped ingress rule; cross-region connections are rejected up front with a clear message
- ZopDay: the Provisioning Jobs list now distinguishes CREATE / UPDATE / DELETE / CONNECT / DISCONNECT with colored badges and a Type filter, with human-readable step labels
- ZopNight: discovery work now survives pod failures: orphaned tasks are reclaimed and retried, so a restart mid-run no longer drops resources