jfrog-reconcile-manifest

To reconcile JFrog Platform state, you provide a manifest path and loaded credentials so the skill can compute a diff against live APIs and apply only the user-approved delta. It reads current configuration, presents changes for approval, and updates projects, repositories, members, OIDC, and Xray settings.

A 3-way diff compares a baseline, manifest, and live state for safer planning, while a 2-way diff compares only the manifest against live state when no baseline exists. Both identify deltas across projects, repositories, members, OIDC, and Xray settings before applying changes.

You apply manifest changes by providing the manifest path to trigger a diff against the live JFrog Platform. The skill generates a structured taxonomy of changes (CREATE, UPDATE, FLAG) and requires explicit user confirmation before applying the delta to projects and repositories.

Yes, JFrog reconciliation integrates with Artifactory or git state backends to retrieve baseline manifests and persist the resulting current state after reconciliation. This enables 3-way diff computation when a baseline is available.

JFrog manifest reconciliation flags certain changes instead of deleting them automatically to ensure explicit user confirmation for destructive actions. The skill uses a structured change taxonomy including CREATE, UPDATE, and FLAG, requiring user approval where deletion isn't automatic.

Yes, you can update JFrog Xray and OIDC settings by including them in your desired-state manifest. The reconciliation skill computes deltas for these settings alongside projects, repositories, and members, then applies the approved changes to the live JFrog Platform.