Skip to content

Update-Module "untrusted repository" prompting is broken #26

@Jaykul

Description

@Jaykul

I assume that when modules are being UPDATED, they're only updated from the original source repository? If not, why?

Not to put it too strongly, but the way that prompting happens in Update-Module is

  1. Awful: You get prompted for every module from an untrusted repository. Not once per repository as happens when installing modules.
  2. Confusing: You're not told which module(s) are being updated, and you're only given a repository nickname (this is a major problem on install as well, but it's particularly problematic with Update-Module when you're being prompted multiple times for the same repository)
  3. Pointless: I have already installed these modules once, and I have already chosen to trust the repository.

Assuming that I'm upgrading all my module, I'm being asked if I want to trust a repository without being told which module is being installed -- as a result, when I'm asked about trusting a repository, I don't have enough information. If the module came from an untrusted repository originally, then it's logical to assume it will come from there again. If it didn't, then I definitely don't want to trust it for an update ...

Ideally, I don't think I should be prompted if I already trusted the source for a module.

Failing that, I think the prompt has to include the module name, so I can make a decision.

Failing that, I should only be prompted once per repository, because being asked the same question multiple times even when I say Yes to all, is non-intuitive, confusing, and a waste of time.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions