Add more capability to use OPA Policy to enforce naming conventions
in progress
W
Western Warbler
Currently, only Pipelines, Steps, Stages, Feature Flags, Connectors, and Secrets can have naming conventions enforced. User wants this expanded to anything that can be named, such as Templates, Orgs, Projects, Approval Groups, Delegates, and User Groups. Currently there is no way to enforce naming conventions on these.
Log In
This post was marked as
in progress
E
Enthusiastic Gorilla
A customer is requesting to enforce naming convention on Feature Flag Environments.
Rohan Gupta
Merged in a post:
Enforcing naming convention on Environments description
T
Thoughtful Locust
It shall be possible to support OPA Policies in Services and Environments for the following usecases
- Enable specific rules and conventions in Names
2.Enable specific rules and conventions in Entity Descriptions
3.Enable specific rules and conventions in Entity Tags
Rohan Gupta
Merged in a post:
OPA policy for Harness service accounts
E
Experimental Jay
We're need to create OPA policies for Harness service accounts, for actions like setting expiration for these accounts. However, based on the response from a Harness support engineer on one of our support tickets, it seems that, at present, Service Accounts aren't integrated with OPA on save .
Rohan Gupta
long-term
Hi Patrick, we plan to expand to other platform objects. Today we do support Templates. https://developer.harness.io/docs/continuous-delivery/x-platform-cd-features/advanced/cd-governance/harness-governance-overview/#template