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

Add installation with winget #498

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

mloskot
Copy link

@mloskot mloskot commented Jun 29, 2023

User description

This is a follow-up to my submission of Infracost package manifests which have been accepted to, see microsoft/winget-pkgs#110850

The winget is an official package manager on Windows, see https://learn.microsoft.com/en-gb/windows/package-manager/winget/

The winget does not require to be Run as Administrator, but it helps
to enable links in order to avoid polluting PATHwith numerous entries.
Administrator can create links to executables in common location of
$env:USERPROFILE\AppData\Local\Microsoft\WinGet\Links

From microsoft/winget-pkgs#99059 (comment)

When in user mode, winget isn't always able to create symlinks.
When it can't create a symlink, it should still add the install directory
to the path (aka "Path cramming"). This is why the command line alias
should still work, even if the symlink isn't present


Generated description

Below is a concise technical summary of the changes proposed in this PR:

Add installation instructions for winget to the Infracost documentation, allowing users to install and upgrade Infracost using the Windows package manager. Update the getting_started.md file to include winget commands for installation and version verification.

TopicDetails
Winget Installation Add winget installation instructions to the Infracost documentation, enabling users to install and upgrade Infracost using the Windows package manager.
Modified files (1)
  • docs/getting_started.md
Latest Contributors(2)
EmailCommitDate
41898282+github-action...chore-Bump-to-cli-vers...August 30, 2024
[email protected]docs-add-usage-cost-docsApril 01, 2024
This pull request is reviewed by Baz. Join @mloskot and the rest of your team on (Baz).

The winget is an official package manager on Windows, see
https://learn.microsoft.com/en-gb/windows/package-manager/winget/

The winget does not require to be Run as Administrator, but it helps
to enable links in order to avoid polluting `PATH`with numerous entries.
Administrator can create links to executables in common location of
`$env:USERPROFILE\AppData\Local\Microsoft\WinGet\Links`

From microsoft/winget-pkgs#99059 (comment)

> When in user mode, winget isn't always able to create symlinks.
> When it can't create a symlink, it should still add the install directory
> to the path (aka "Path cramming"). This is why the command line alias
> should still work, even if the symlink isn't present
@CLAassistant
Copy link

CLAassistant commented Jun 29, 2023

CLA assistant check
All committers have signed the CLA.

@vdmgolub
Copy link
Contributor

Hello @mloskot! Thank you for creating the pull request. I'll bring this to the team.

We need to investigate how we can release new versions for Winget in an automated fashion before adding it to the documentation.

@mloskot
Copy link
Author

mloskot commented Jun 29, 2023

@vdmgolub Yes, that would be the desired approach. You may want to have a look at
https://github.com/microsoft/PowerToys/blob/main/.github/workflows/package-submissions.yml
as an example of fairly generic GHA workflow to submit winget manifest on release

@vdmgolub
Copy link
Contributor

@mloskot Awesome! Thanks for the example :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants