Policy as a feature

Type of change

• Bug Fix
• Feature

Current Epic: osdu/platform&29

OPA\Policy Integration (Configured mostly through properties, Storage, Search).

Does this introduce a change in the core logic?

• [YES]

Does this introduce a change in the cloud provider implementation, if so which cloud?

• AWS
• Azure
• Google Cloud
• IBM

Does this introduce a breaking change?

• [YES]

Currently, the Policy enabled flag which decides whether or not to use Policy service is coming from the application properties file, this MR is made to use the function flag to use Policy as a feature. So the flag can be fetched from partition property, environment variable featureFlag.policy.enabled.

changed milestone to %M24 - Release 0.27

added AWS Azure Common Code GC IBM labels

assigned to @Stanislav_Riabokon

added 1 commit

• 383fba13 - Policy as a feature

Compare with previous version

changed the description

added 4 commits

• 383fba13...d3f30494 - 2 commits from branch master
• 6efab348 - Merge remote-tracking branch 'origin/master' into feature-policy
• 34ca31b9 - Fixed features

Compare with previous version

added 1 commit

• 15207386 - Fixed features

Compare with previous version

mentioned in merge request osdu/platform/deployment-and-operations/helm-charts-azure!813 (merged)

approved this merge request

added 1 commit

• dda4da22 - Fixed features

Compare with previous version

reset approvals from @thulasi_dass by pushing to the branch

@hutchins - FYI

added MREnhancement label

If this is to be used as a feature flag, with it's drastic impact on testing and security I'd like some way to programmatically check if this is enabled or not. Maybe an addition to /info or another status/config related API @chad

resolved all threads

resolved all threads

Hi again, this is an automated friendly reminder- this MR is targeted for M24 - Release 0.27 as indicated by the Milestone label. We are going to fork the release branch by the end of the week as per the timeline. Please merge this MR if this is ready. As per the PMC policy:

• For CSP-specific change, you can merge this once you get another approval from your team.
• For common code change, please ensure the pipelines are passing and we get 2+ approvals from the other maintainers, ADR approved as needed for new features.
• For lib upgrades/security fixes, you can merge as long as the pipelines are passing.
• For documentation changes, you can merge as long as the changes are reviewed with due diligence.

Otherwise, please move this to the next milestone for us to unblock the release process. Thank you.

approved this merge request

Hi again, this is an automated friendly reminder- this MR is targeted for M24 - Release 0.27 as indicated by the Milestone label. We are going to fork the release branch by the end of the day as per the timeline. Please merge this MR if this is ready. As per the PMC policy:

• For CSP-specific change, you can merge this once you get another approval from your team.
• For common code change, please ensure the pipelines are passing and we get 2+ approvals from the other maintainers, ADR approved as needed for new features.
• For lib upgrades/security fixes, you can merge as long as the pipelines are passing.
• For documentation changes, you can merge as long as the changes are reviewed with due diligence.

Otherwise, please move this to the next milestone for us to unblock the release process. Thank you.

resolved all threads