Rule-based fix: the IaC check has no rule-based fix
type | https://docs.frem.sh/reference/api/errors/rule-fix-check-not-supported |
| HTTP status | 422 Unprocessable Content |
What it means
Returned by POST /orgs/{org}/code-security/secrets/findings/{id}/fix and POST /orgs/{org}/code-security/iac/findings/{id}/fix (rule-based fixes). No fix was requested and no pull request was opened.
A rule-based IaC fix sets one property to its secure value. It is offered only for the checks listed under rule-based fixes.
Example detail message returned with this error:
- This IaC check is not on the list of checks with a one-property fix, so no fix is proposed for it.
The response also carries "reason": "check_not_supported".
What to do
Fix the resource by hand. The finding’s remediation text says what to change.
Response shape
All fremforge API errors are RFC 9457 problem+json:
{
"type": "https://docs.frem.sh/reference/api/errors/rule-fix-check-not-supported",
"title": "Unprocessable Content",
"status": 422,
"detail": "...",
"reason": "check_not_supported"
}Branch on type, not on title or detail - those are human-readable and may be reworded.