Goran StankovskiGoran Stankovski··4 min read

Identity as Code: Governing PingOne Advanced Identity Cloud

Identity platforms carry the most consequential configuration in an enterprise and the least governed change process. A journey edited in a console, a client secret rotated by hand, a script changed in production because the test tenant had drifted: each is a change to the front door of every application, and most organisations could not say who approved it or reproduce the state before it.

The PingOne Advanced Identity Cloud content pack (packs:ping-aic) applies OpsChain's posture to that configuration. The tenant's state lives in YAML your repository commits; a governed change reconciles it; every operation on the tenant is a typed action under approval; and the evidence is the platform's, not the console's.

The tenant as a document

Every action targets a ping_tenant document: the tenant's hostname, its environment tier (development, staging or production), the realms it manages, and the environment variables the service account arrives in. The document is per OpsChain environment, so a promotion from staging to production is a change against two documents, not a copy-paste between two browser tabs.

Ten resources, three verbs

The pack declares ten resource kinds as YAML: journeys (the tree and its nodes as one promotable document), scripts, OAuth2 clients, services, managed objects, connectors, sync mappings, environment secrets and variables, email templates and themes. Three verbs reconcile them.

  • ping_aic:plan reads the tenant, compares it with the committed state, and prints a deterministic diff: canonical JSON, one unified diff per change. Nothing is written.
  • ping_aic:apply applies the plan in dependency order and is idempotent; a second apply against an unchanged tenant is a no-op. Pruning what the repository no longer declares is opt-in, per kind.
  • ping_aic:export writes the tenant's current state back as YAML that round-trips to a no-op plan, so adopting an existing tenant is an export, a commit and a review.

Per-environment values flow through placeholders, and secrets only ever arrive from vault-resolved environment: the YAML carries the reference, never the value.

The operations a change composes

Beside the declarative surface, the pack ships the imperative verbs a governed change strings together: environment promotion between tiers, environment secrets and variables, identities (create, update, search), service accounts, and pulling tenant logs for the evidence record. Each is an action with typed inputs and published outputs, so a workflow can promote a configuration, rotate a secret and capture the log of the result as one approved, audited run.

No SDK, no CLI, no interpreter

There is no vendor SDK for this platform, and the pack does not bundle a vendor CLI or an interpreter-hosted tool. It is hand-typed Go over the tenant's REST APIs, executed by the runner from the signed bundle. The only wire is outbound HTTPS from the runner to the tenant. Every step ensures its own tool when the runner it lands on lacks it, so a fleet needs no shared cache.

Where approval and evidence sit

Because the pack's actions are OpsChain steps, the governance is the estate's, not the pack's. A production tenant sits under a production path with its approval policy: quorum, self-approval excluded, change windows. A ping_aic:apply against it is held until the approvers act, and the plan it will apply is in the change record for them to read. The apply's output, the tenant log pulled after it and the masked inputs land in the same tamper-evident lane as a cloud deployment or a database change. When a regulator asks who changed the login journey and under which approval, the answer is one record.

What this looks like in practice

An identity engineer edits a registration journey in the staging tenant's YAML, commits, and raises a change that runs plan against staging. The diff is reviewed in the change. apply runs. A second change promotes the same document to production: plan shows the production diff, the production approvers act, apply runs, and logs_pull captures the tenant's audit of the apply. The journey in production is the journey in git, and the path from edit to production is four records in the evidence lane.

Getting the pack

The pack ships as a signed bundle beside OpsChain v5 and installs with opschain admin packs install -f <bundle> on an estate licensed for packs:ping-aic. OpsChain is available by invitation: request access, or book a demo and bring a tenant you would like to see under version control.


Key takeaway

A PingOne Advanced Identity Cloud tenant becomes code: YAML in your repository, a deterministic plan, an idempotent apply, an export that round-trips, and every tenant operation a typed action under the same approval and evidence as the rest of your estate.

Ready to see OpsChain in action?

Book a personalised demo and see how OpsChain can transform your operations.

Book a Demo
Goran Stankovski
Goran Stankovski

Founder & CEO, LimePoint

Goran is the founder of LimePoint and the creator of OpsChain. He is passionate about helping enterprises automate and govern their operations at scale.