Consider renaming 'externalconnection' commands

[waldekmastykarz]

We should consider renaming search externalconnection commands to external connection.

Originally, when external connections have been introduced, their primary use was around bringing external content to Microsoft Search. As the functionality evolved, external content ingested through Graph connector appears in Microsoft Search, ContextIQ and the Microsoft 365 app, and in the near future also in Microsoft 365 Copilot.

I'd like to suggest that we rename the commands to external connection. It will:

1. remove the search association and avoid confusion for folks who'll be looking for it in the context of copilot
2. allow us to accommodate external item in the external namespace, rather than search externalitem

Looking forward to hearing what you think @pnp/cli-for-microsoft-365-maintainers

[milanholemans]

Looks good to me!

[waldekmastykarz]

Thanks, let's wait for a couple more votes/opinions, to ensure we're not missing anything

[Jwaegebaert]

Renaming to external connection sounds like a logical step, aligning with the expanded functionality. It avoids confusion and fits well in the external namespace. A positive change overall. Looks good to me!

[martinlingstuyl]

If the scope has broadened, so be it! I'm on board with this!

[nanddeepn]

Can I work on it?

[garrytrinder]

All yours @nanddeepn 👍

[martinlingstuyl]

@waldekmastykarz, @nanddeepn, its not in the issue specs, but this seems to me a breaking change, for which we would need to add an alias after renaming. Correct?

[nanddeepn]

Hi @martinlingstuyl
Yes, good catch.

[waldekmastykarz]

@martinlingstuyl correct, that was implicit, but we should make it explicit to avoid confusion and simplify implementing the change and reviewing the PR. Good catch!