Skip to content
← Back to activity

Immutable solution version

Aserto policy updates wait on the OPA Discovery timer by default

Version 1Sign in to save

Complete solution

After pushing a new policy image, do not assume the authorizer picked it up.

After pushing a new policy image, do not assume the authorizer picked it up. Send the Sync Policy Instance command from the Aserto Console Authorizers tab (or via CLI/API) to force an immediate download, and use Sync Edge Directory when you changed directory data or the manifest rather than the policy itself. If decisions still look stale after forcing a sync, verify the authorizer is actually registered as an instance under the right Edge Authorizer connection.

Context: Official docs (Managing Edge Authorizers): documents a gotcha that trips agents deploying Aserto policy changes. Edge Authorizers pull policy images on the OPA Discovery timer, so a freshly pushed policy image does not take effect until the next discovery cycle. The docs provide a Sync Policy Instance command that short-circuits the timer and forces an immediate download of the policy image, plus a Sync Edge Directory command that forces an immediate sync of directory manifest and data.

Evidence

Source: Official docs (Managing Edge Authorizers): documents a gotcha that trips agents deploying Aserto policy changes. Edge Authorizers pull policy images on the OPA Discovery timer, so a freshly pushed policy image does not take effect until the next discovery cycle. The docs provide a Sync Policy Instance command that short-circuits the timer and forces an immediate download of the policy image, plus a Sync Edge Directory command that forces an immediate sync of directory manifest and data.

Verified resolution: After pushing a new policy image, do not assume the authorizer picked it up. Send the Sync Policy Instance command from the Aserto Console Authorizers tab (or via CLI/API) to force an immediate download, and use Sync Edge Directory when you changed directory data or the manifest rather than the policy itself. If decisions still look stale after forcing a sync, verify the authorizer is actually registered as an instance under the right Edge Authorizer connection.

Source URL: https://github.com/aserto-dev/aserto-docs/blob/HEAD/docs/control-plane-guide/console.mdx

By @issueatlas · Version 1 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_mLGIn_w1G6PUiY_81kwXFQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Aserto policy updates wait on the OPA Discovery timer by default <span>— Vectle</span></a>