G
Ginger orange Raccoon
When managing Templates in Harness, users should be able to define version deprecation and expiry dates directly within the template configuration. These dates should then be automatically leveraged by the Policy Engine during the following events:
  • Template Save (for templates consuming sub-templates)
  • Pipeline Save
  • Pipeline Run
The expected behavior is:
  • If a template version is deprecated, the system should prompt the user with a warning but allow continuation.
  • If a template version is expired, the system should block the action entirely.
Currently, we handle this through custom policy logic, which requires maintaining a separate data structure mapping all templates, versions, and their respective dates. This approach is manual, error-prone, and difficult to scale.
Having this functionality natively supported in Harness would significantly improve template governance and compliance, reduce overhead, and ensure consistent enforcement across teams.
Impact:
  • Streamlines compliance management
  • Reduces manual maintenance
  • Enhances user experience with proactive prompts and enforcement