apigee / apigee/apigeetool-node
Per project configs
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 91
- Forks
- 91
- PR merge metrics
- No merged PRs in 30d
Description
I wanted to query whether it would be possible to setup config files within our projects to specify common options such as base path etc which we could store in git.
This would make deployments much easier, and by requiring each person to have their username and password as a environment variable, it'd mitigate any leaking of sensitive data into git.
Obviously I could create a wrapper tool which performs this task and then simply builds up the command to execute, but it would be nicer for this functionality to be built into the tool itself.
Perhaps some sort of . rc file which can be automatically read if it exists, which sets default values such as baseuri etc, but can still be overridden directly in the command via the current flags.
I'm happy to open a PR implementing this, but file name and format need discussing first.
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
Begin by reviewing the tool's existing command-line flags and how values such as base path or baseuri are currently supplied. The filename and config format still need agreement before implementation; done should include project-local defaults, environment-based credentials, and direct flags overriding those defaults.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100