cloudfoundry-community / cloudfoundry-community/node-cfenv
Invalid PORT value
Nobody has claimed this yet.
- Dominant language
- CoffeeScript
- Stars
- 74
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
Trying to keep a codebase compatible between CloudFoundry (Bluemix) and Azure.
I'm getting an error on getAppEnv, because under Azure, port is not a number but a named pipe (/\\.\pipe\xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).
I was hoping to use cfenv with the vcap option filled some other way when running "locally" on Azure.
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
No file or test is named. Start by locating getAppEnv and the vcap environment parsing, then reproduce the Azure case where PORT is a named pipe rather than a number. Done means the Azure value is handled without breaking Cloud Foundry environment handling, with coverage for both forms.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, coffeescript, node.js
- Domain
- backend, cloud
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100