apigee / apigee/apigeetool-node
Creating a cache with "--timeoutInSec 300" results in incorrect "expirySettings"
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 91
- Forks
- 91
- PR merge metrics
- No merged PRs in 30d
Description
For example:
createCache -N --cache test-cache -o ORG -e ENV --cacheExpiryInSecs 300
results in:
"expirySettings": {
"expiryDate": {
"value": "12-31-9999"
},
"timeoutInSec": {
"value": "300"
}
}
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 createCache command and reproduce the example using --cacheExpiryInSecs 300. Trace how the command produces expirySettings and verify that the generated expiryDate and timeoutInSec represent the requested cache timeout.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100