Change impact analysis
Conera connects what changed to what actually runs, so teams see the break before it ships.
Get a demoCode meets cloud
A change can wire into a cloud service without the context that decides whether it holds up: your real traffic and that service's limits. Conera connects the two, so it flags when a change will exceed a rate limit, exhaust a connection pool, or miss an access rule.
Adds mutual-TLS to payment-service outbound calls, loading the client cert from Azure Key Vault at startup.
Remove deprecated legacyOrderId field from order-status API
response.
High risk: breaking API contract change on order-status.
Why it matters
checkout-service and refunds-service depend on this contract. They will break as soon as this ships.
- checkout-service depends on order-status.
- refunds-service depends on order-status.
- The change looks local; the dependency graph spans other repos.
Before you merge
- Confirm checkout-service and refunds-service are ready for the contract change
- Coordinate rollout with the owning teams
Based on 2 downstream services across 2 repos.
Across your services
A change to one API can look self-contained in its own repo. Conera knows which services depend on every contract, so it catches changes that would break checkout-service, refunds-service, and others before they ship.
GitOps and delivery
A config or GitOps change is a small diff, but its real effect happens at sync and reshapes what's actually running. Conera reasons about what the change does when it deploys, not just the lines that changed.
Enable auto-prune on the production payments Argo CD application.
High risk: auto-prune enabled on production payments app.
Why it matters
At the next sync, Argo CD will delete any live resource not tracked in Git. Three ConfigMaps and one CronJob exist in the cluster but aren't in the repo, likely from manual hotfixes during the March incident.
- payment-fallback ConfigMap was applied manually and never committed.
- reconciliation-cron was added as an emergency fix and is still running.
- Prune is irreversible: deleted resources won't come back without re-applying them.
Before you merge
- Audit live vs Git drift in the payments namespace
- Commit or remove untracked resources before enabling prune
- Run sync in dry-run mode first
Based on 4 untracked live resources and 1 prior incident from unexpected prune.
Update Key Vault authorization for payments-prod vault in Azure.
High risk: Key Vault authorization change affecting cross-cloud consumers.
Why it matters
payment-service runs on AWS EKS and retrieves its TLS certificate from this Azure Key Vault using Microsoft Entra workload identity federation. If the existing authorization is removed before the replacement authorization is effective, the service may lose access to the secret during the next authentication, secret retrieval, or pod restart.
- Ensure the AWS federated workload identity has the required Get permission (via the new access policy or Azure RBAC role assignment).
- Two Azure-hosted services also depend on this Key Vault.
- A previous authorization change caused a 12-minute outage due to the authorization update order.
Before you merge
- Confirm the AWS federated workload identity is included in the new authorization (access policy or RBAC role assignment)
- Apply the new authorization before removing the existing one
- Verify secret retrieval from the AWS EKS non-production environment after deployment
Based on 1 cross-cloud dependency, 2 Azure consumers, and 1 prior authorization incident.
Across clouds
A resource lives in one cloud; the service that depends on it runs in another. Conera models Azure, AWS, and Google Cloud as one system, so a change to a resource in one cloud surfaces every service that depends on it, even across the boundary.
Medium risk: mutual-TLS on payment-service outbound calls via Azure Key Vault at startup.
Why it matters
payment-service peaks at ~10,000 requests/second, and Key Vault throttles at ~2,000 calls per 10 seconds. If the certificate is read per request instead of cached at startup, Key Vault will throttle and outbound calls will fail.
Before you merge
Based on 5 recorded facts, 1 incident, and 2 clean deploys of this same change pattern.