Skip to content

Apigee maven plugin Vs apigeectl #258

@abiram8

Description

@abiram8

We have 3 options for Apigee automated deployment if use case already have the cloud build (trigger)
1 Option: To build and deploy Apigee proxies using Maven and Cloud Build, you will need to use the Apigee Maven plugin within a Cloud Build pipeline. Advantage : fully automatic
2nd option: apigee-edge-maven-plugin is a build and deploy utility for building and deploying the Apigee ApiProxy's/Application bundles into Apigee Platform. (This does not use Cloud Build) https://github.com/apigee/apigee-deploy-maven-plugin
3rd Option: use thethe Apigee CLI within your Cloud Build pipeline, without relying on the Apigee Maven plugin.
Listed option https://github.com/apigee/apigeecli/blob/main/docs/apigeecli.md lists the deployment of products,kvm and shared flow and proxies, but (Option 1 and 2) which uses apigee mavenh plugin ttps://github.com/apigee/apigee-deploy-maven-plugin lists only for proxies and shared flow deployment does not list all other like apigeectl. Let me know if iam missing anything, hence better option will be to use Option 3 with Cloud Build for Apigee automated CI/CD or should we be aware of any other details ?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions