Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automated updates #263

Closed
ChristianGalla opened this issue May 21, 2020 · 6 comments
Closed

Automated updates #263

ChristianGalla opened this issue May 21, 2020 · 6 comments
Labels
Issue-Feature This is a feature request for the Windows Package Manager client. Resolution-Duplicate Issue is a duplicate

Comments

@ChristianGalla
Copy link

Description of the new feature/enhancement

As a user I always want to use the newest version of a program I installed. As addition to #120 I want the new versions to be installed automatically.

Currently there are some programs that have no update mechanism, some are prompting for updates and some are installing updates automatically for example via a custom service.

If programs are not updated, new useful features cannot be used. Also, there may be bugs that were already fixed and security vulnerabilities.

If software developers do not have to implement their own update mechanism, they can focus on the main functionality of their programs. Also, users do not have to do updates manually.

Proposed technical implementation details

The easiest implementation I can think of is a scheduled task or service to automatically call winget's update method (#120).

Ideally, this should be handled by Windows Update like updates for drivers or Microsoft Office. This way updates can be installed when no program instance is running.

Open topics

Maybe there should be a flag to disable automated updates for some programs if someone wants to stick to a specific version?

There can be some breaking changes between program versions. Maybe there should be no automated updates between major versions? Unfortunately, not all programs are using semantic versioning, so this may be difficult to implement. Also, there may be no (security) updates for an old major version anymore, which leaves a vulnerable system.

If programs already have an updater included, winget's updater or the included updater has to be disabled. I think the yaml file should have a new parameter to disable winget's updater and / or a setup parameter to disable the installation of a build in update service.

@ChristianGalla ChristianGalla added the Issue-Feature This is a feature request for the Windows Package Manager client. label May 21, 2020
@ghost ghost added the Needs-Triage Issue need to be triaged label May 21, 2020
@doctordns
Copy link

The desire to be running the latest version is good. IT Pros, however, need to manage that process. Configuration management means having control over what updates and when they get applied.
Winget appears to be aimed at the individual developed, rather than IT Pros, but more control would be good for IT Professionals.

@kramfs
Copy link

kramfs commented May 22, 2020

The desire to be running the latest version is good. IT Pros, however, need to manage that process. Configuration management means having control over what updates and when they get applied.
Winget appears to be aimed at the individual developed, rather than IT Pros, but more control would be good for IT Professionals.

I guess this is an evolving topic especially at this early stage but I'd imagine the scenario you posted can be controlled using the repository a.k.a source where only approved apps are available

@doctordns
Copy link

Unfortunately, that does not help. Winget.exe is Linux like and not easily automatable. If you are doing configuration management in any sort of larger organisation, you want to be able to script. A tool with such limited scripting ability is not a great one.

@slaet
Copy link

slaet commented May 27, 2020

and please add also the possibility to update all Application that are installed trough winget. That all Applications has the latest version, that we can add a Scheduled Task for example running once a Week to update all Applications. This would be a benefit for security related aspects of Buggy Applications.

@denelon denelon removed the Needs-Triage Issue need to be triaged label May 28, 2020
@denelon denelon added this to the Package Manager Backlog milestone May 28, 2020
@denelon
Copy link
Contributor

denelon commented Aug 11, 2020

Duplicate of #212

@denelon denelon marked this as a duplicate of #212 Aug 11, 2020
@ghost
Copy link

ghost commented Aug 11, 2020

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost closed this as completed Aug 11, 2020
@ghost ghost added the Resolution-Duplicate Issue is a duplicate label Aug 11, 2020
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Feature This is a feature request for the Windows Package Manager client. Resolution-Duplicate Issue is a duplicate
Projects
None yet
Development

No branches or pull requests

5 participants