Set a provider's version lifecycle rule
One step with Harness. We can help you get access.
Get something done
Set a provider's version lifecycle rule
with Harness
Works with AI assistants
Use Harness: its Harness Provider Registry API lets you set a provider's version lifecycle rule in a single step (PUT /iacm/api/providers/{id}/lifecycle). Harness also has an MCP server, so an AI assistant like Claude or ChatGPT can do it for you. capabilities.work can help you get signed up and connected.
- How do I define how many provider versions stay supported before they are flagged as warning?
- Can I set what action happens when a team uses a deprecated provider version?
- Does saving a lifecycle rule replace all the existing per-version overrides?
Say it to your AI assistant
- Set provider {id} to keep {supported} versions supported and {warning} in warning.
- Make deprecated versions of provider {id} trigger the {action} action.
For your developer
PUT /iacm/api/providers/{id}/lifecycle in Harness Provider Registry API. Full spec on APIs.io.