Sackmesser - Deploy always fails if config.json is present
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 221
- Forks
- 174
- PR merge metrics
- No merged PRs in 30d
Description
If config.json (supported by apigee-deploy-maven-plugin config.json ) is present, using sackmesser to deploy the proxy with
sackmesser deploy --googleapi -d <path to proxy> -t $(gcloud auth print-access-token) -e $ENV -o $ORG
Fails with the error
[ERROR] Failed to execute goal io.apigee.build-tools.enterprise4g:apigee-edge-maven-plugin:2.3.1:configure (configure-bundle-step) on project apigee-deployer: null: MojoExecutionException -> [Help 1]
If I remove config.json everything works just fine. This feature of the maven plugin should work when using sackmesser
Attached proxy to reproduce the issue.
mockapiSack.zip
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the attached mockapiSack.zip and reproduce the failure using the documented sackmesser deploy command with config.json present, then compare it with deployment after removing the file. Trace how Sackmesser invokes the Apigee Maven plugin's configure step; done means the proxy deploys successfully while preserving the config.json behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100