fix: Cloud missing_config should name config context add
- Dominant language
- TypeScript
- Stars
- 41
- Forks
- 24
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 56
Description
`src/lib/cloud-client.ts` tells users to `elastic config set`. That command is `config current-context set`. Cloud setup is `elastic config context add --cloud-url … --cloud-api-key …`.
Same string on missing Cloud block and missing `api_key`.
This is Cloud-specific. #631 covers the generic no-file path.
Acceptance: unset Cloud on a context, run `elastic cloud orgs list-organizations --json`. `error.message` names `elastic config context add` and `--cloud-api-key`. No `config set`.
Contributor guide
Research direction
Start in src/lib/cloud-client.ts, where the missing Cloud block and missing api_key use the incorrect guidance. Run elastic cloud orgs list-organizations --json with Cloud unset on a context, then verify error.message names elastic config context add and --cloud-api-key and contains no config set.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli, cloud
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 88/100