[MENFORCER-399] requireVariable = requireProperty or requireEnvironmentVariable

**[Hüseyin Kartal](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=hsyn)** opened **[MENFORCER-399](https://issues.apache.org/jira/browse/MENFORCER-399?redirect=false)** and commented

As far a i know maven doesn't care where a value for ${variable} comes from. In a pom you can access a env.variable or a property by ${variable}.

Also in some system the value is provided by an environment variable like CICD or by a property maybe a dev environment.

I would suggest a new standard rule "requireVariable"  which just look like maven for a value for this variable by property or environment.

---

**Affects:** 3.0.0

**Attachments:**
- [pom.xml](https://issues.apache.org/jira/secure/attachment/13037396/pom.xml) (_2.02 kB_)

Start by reviewing the issue description and the attached pom.xml to understand the proposed requireVariable behavior. Determine how a value should be resolved from a Maven property or environment variable, and define the expected rule behavior and tests before implementation.

Written by the indexing model from the issue text.