apigee / apigee/apigeetool-node
Deploy to higher env
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 91
- Forks
- 91
- PR merge metrics
- No merged PRs in 30d
Description
Does apigeetool deploys to higher environment from the same code base as main proxy and replace the targetendpoint/targetservers from some kind of properties file similar to maven plugin
in mavenplugin we have config.json and edge.json for higher env properties and maven will build new configuration zip file based on those properties and imports to apigee edge.
Ex: https://github.com/apigee/apigee-config-maven-plugin/tree/master/samples/APIandConfig/HelloWorld
Do we have similar functionality in apigeetool too? If so how to do it
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 by reviewing apigeetool's deployment commands and the referenced apigee-config-maven-plugin sample, especially config.json and edge.json. Determine whether environment-specific target endpoints and target servers are supported; done means documenting the existing workflow or defining the scope for adding equivalent configuration-based deployment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100