Refactor Policy Enforcer Configuration

- Updated the Policy Enforcer configuration across multiple YAML files to use a unified `policyDir` instead of individual policy sources.
- Changed the step name from `enforcePolicy` to `policyEnforcer` for consistency.
- Enhanced the documentation to clarify the use of `policyUrls`, `policyDir`, and `policyFile` for policy sources.
- Adjusted related code and tests to accommodate the new configuration structure.
- Added documentation for using YAML folded scalar (>-) to keep long comma-separated policyUrls values readable across multiple lines.
This commit is contained in:
Ayush Rawat
2026-03-03 10:04:22 +05:30
parent 3617c9b4a6
commit e22b79e137
9 changed files with 123 additions and 41 deletions

View File

@@ -48,6 +48,10 @@ modules:
id: schemavalidator
config:
schemaDir: /mnt/gcs/configs/schemas
policyEnforcer:
id: policyenforcer
config:
policyDir: "./policies"
signValidator:
id: signvalidator
publisher:
@@ -66,6 +70,7 @@ modules:
role: bap
steps:
- validateSign
- policyEnforcer
- addRoute
- validateSchema
- name: bapTxnCaller
@@ -98,6 +103,10 @@ modules:
id: schemavalidator
config:
schemaDir: /mnt/gcs/configs/schemas
policyEnforcer:
id: policyenforcer
config:
policyDir: "./policies"
signer:
id: signer
publisher:
@@ -116,6 +125,7 @@ modules:
role: bap
steps:
- validateSchema
- policyEnforcer
- addRoute
- sign
- name: bppTxnReciever
@@ -149,6 +159,10 @@ modules:
id: schemavalidator
config:
schemaDir: /mnt/gcs/configs/schemas
policyEnforcer:
id: policyenforcer
config:
policyDir: "./policies"
signValidator:
id: signvalidator
publisher:
@@ -167,6 +181,7 @@ modules:
role: bpp
steps:
- validateSign
- policyEnforcer
- addRoute
- validateSchema
- name: bppTxnCaller
@@ -199,6 +214,10 @@ modules:
id: schemavalidator
config:
schemaDir: /mnt/gcs/configs/schemas
policyEnforcer:
id: policyenforcer
config:
policyDir: "./policies"
signer:
id: signer
publisher:
@@ -217,5 +236,6 @@ modules:
role: bpp
steps:
- validateSchema
- policyEnforcer
- addRoute
- sign