Skip to main content

Policy exists

typehttps://docs.frem.sh/reference/api/errors/policy-exists
HTTP status409 Conflict

What it means

You asked fremforge to apply the default risk policy (POST /orgs/{org}/risk-tier/template/apply), and the policy repository already has a .fremforge/risk.yaml on its default branch that differs from the template. That file is your organisation’s own policy. fremforge never overwrites it, so nothing was changed: not the file, and not the risk tier settings.

Example detail messages returned with this error:

  • acme/.rules already has .fremforge/risk.yaml on main, and it is not the template. It is the org’s own policy and is left as it is.

What to do

Compare your file with the template: GET /orgs/{org}/risk-tier/template returns the template’s text as source. To take over parts of it, change your own file through a pull request in the policy repository. To try the template on its own, apply it again with another policy_repo; the settings then name that repository as the org policy repository.

Response shape

All fremforge API errors are RFC 9457 problem+json:

{
  "type": "https://docs.frem.sh/reference/api/errors/policy-exists",
  "title": "Conflict",
  "status": 409,
  "detail": "..."
}

Branch on type, not on title or detail - those are human-readable and may be reworded.