You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: