Native Harness Module Registry support to enforce version constraints (N/N-1/N-2) at the registry level
long-term
R
Ready Ostrich
Native Harness Module Registry support to enforce version constraints (N/N-1/N-2) at the registry level
We are implementing a module lifecycle management policy for our Terraform modules in the Harness IACM Module Registry. As part of this, we need to control how users reference module versions during pipeline runs.
Our internal policy requirements are
Only Latest (N), N‑1, and optionally N‑2 versions should be allowed
Any version older than N‑2 must be restricted from usage
Older versions may also be hidden/marked as deprecated in the UI (if supported)
Enforcement should ideally prevent users from selecting or referencing disallowed versions
Log In
Rohit Reddy
marked this post as
long-term
Rohit Reddy
Hey Satej, Thank you for reaching out. We are tracking this as a long-term enhancement to our module registry. We will reach out to you with a tentative design and align on the use case coverage shortly. We are working towards a version delete functionality as a tactical feature as we build teh lifecycle management functionality long term.