Releases: apigee/apigee-deploy-maven-plugin
Support for OAuth (Bearer and Refresh tokens)
In this release, you can pass the bearer token and/or refresh token directly to the plugin as an argument for the deployment
<apigee.bearer>${bearer}</apigee.bearer> <!-- optional: Bearer token override -->
<apigee.refresh>${refresh}</apigee.refresh> <!-- optional: Refresh token override -->
If the bearer token is alone passed - plugin validates the token (for right issuer, expiration, etc) and then uses it for calling the Management APIs, it fails the build otherwise
If the bearer token and refresh is passed - plugin validates the bearer token (same rule as above), if not valid, uses the refresh token to generate a new access token and uses that for the Management API. If the refresh token is expired or invalid, the build fails.
_NOTE: Refresh token alone cannot be passed. It can be passed only if you pass the bearer token_
Support for Shared Flows
Support For Shared flows
There is a sample included within the github repo just like the API Proxy. The feature is built with config.json for build time config replacements and has deployment options of override and update similar to the API proxy options.
