Apigee X archive deployment with service account

[Danizen]

When running the following command-line:

gcloud beta apigee archives deploy --environment eval-archive

I am getting an error saying that my deployment requires a service account, and that this needs to be specified in deployments.json.  That's fine on one level, but there is no clear documentation of deployments.json that I have found - I can *guess* that it is "serviceAccount", followed by a string.

The other problem is that the source code is then coupled to the service account, as if the same service account will be used in development, QA, and production.  We all know that this is not real-world.

What is needed here is a --service-account argument to the beta command, or an acknowledgement from Google that the maven plugin is the official way to deploy an API Proxy.

For CICD and IaC (Infrastructure as Code) for Apigee, Google seems to be pushing Apigee X archive deployments in their public documentation.  See https://cloud.google.com/apigee/docs/api-platform/deploy/manage-archive-deployments.

However, the most mature solution appears to be the Maven plugin at https://github.com/apigee/apigee-deploy-maven-plugin

@madhans , how do you think I should proceed?  I like the integration of VS code with Apigee X, but need the ability to deploy with a service account.

[apickelsimer · Accepted solution]

Archive deployments are currently in preview and are subject to change. I strongly recommend taking a different approach.

I suggest you use the Apigee Maven plugin as this is used by many (100s?) Apigee customers and is quite mature, as you indicated. It supports all versions of Apigee, including X.

Another alternative (if you're using Apigee X or hybrid) is apigeecli