Can a Policy Be Exported in OAG Without Exporting its Dependencies?
(Doc ID 1961761.1)
Last updated on MARCH 25, 2021
Applies to:Oracle API Gateway - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
There is a process in the environment to expose many APIs and reuse filters/policies chains to construct their policies . But when an export of a policy occurs that has dependencies, all of the dependencies are exported as well. There is not option to export only principal policy.
All developed Policies, when exported, will carry the same policy physically in their .pol , replicating the code.
Suppose, for example, the environment has three policies and it is necessary to export all these policies (MyPolicyA, MyPolicyB and GlobalRequestSecurity) and use a VCS to maintain version control of them. After that, suppose it is necessary to change the GlobalRequestSecurity Policy that is called by the others. The other Policies will be invalidated as MyPolicyA and MyPolicyB will be accessing an old version of GlobalRequestSecurity.
So, the way to fix this, apparently, is to checkout both MyPolicyA and MyPolicyB, update GlobalRequestSecurity, export again, and then distribute to the new version of all the policies to all environments, not only GlobalRequestSecurity.
Is there an way to export only the principal policy?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document