Notify users about discovery step after connection
Nobody has claimed this yet.
- Dominant language
- Perl
- Stars
- 737
- Forks
- 214
- PR merge metrics
- No merged PRs in 30d
Description
User story
As maintainer,
I would like to print a message about the initial discovery step of the managed endpoint,
so I can inform users about what's happening right after connection.
Additional context
It feels like we need to often explain that Rex does some discovery of the managed endpoint after establishing the connection in order to determine which shell it's talking to, or which package/service manager module should be used for the given endpoint.
Describe the solution you'd like
I'd like to print a single INFO-level message to the output, for example: "Discovering endpoint details".
Describe alternatives you've considered
Adding some documentation about this step would be useful too, but I feel like this step during execution is worth to be explicit about.
I'm not sure how useful a FAQ item would be on the website. The goal is to keep users informed about what's happening under the hood right where it's in context.
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 locating the managed-endpoint connection flow and the discovery step that determines the shell or package/service manager module. Add one INFO-level message after connection and verify that execution output includes it before discovery begins.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- perl
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100