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

Investigate if support to install the CQL Packager as a dotnet tool still works #572

Open
baseTwo opened this issue Sep 24, 2024 · 2 comments
Assignees
Labels
Help Wanted Extra attention is needed Packaging

Comments

@baseTwo
Copy link
Collaborator

baseTwo commented Sep 24, 2024

According to online documentation one is supposed to easily install the CQL Packager via the dotnet tool installed like so:

dotnet tool install Hl7.Cql.Packager --global --prerelease

Investigate if this is still working. If not, it needs to be implemented. Also check that the documentation is still valid

@baseTwo baseTwo added Help Wanted Extra attention is needed Packaging Enhancement New feature or request labels Sep 24, 2024
@baseTwo baseTwo self-assigned this Sep 24, 2024
@baseTwo baseTwo changed the title Add support to install the CQL Packager as a dotnet tool Investigate if support to install the CQL Packager as a dotnet tool still works Sep 24, 2024
@baseTwo
Copy link
Collaborator Author

baseTwo commented Sep 24, 2024

Getting the following exception.
Image

Found some documentation online : dotnet/interactive#3319

Running the tool with verbose output
Image

Listing Nuget sources
Image

Update expired tokens in local GitHub settings https://github.com/settings/tokens for in my case, the 2nd source as shown above. Capture the token.

Run command to update the source with the new token.

 dotnet nuget update source Github_FirelyTeam --source https://nuget.pkg.github.com/FirelyTeam/index.json --username {your user name} --password ghp_{your token}

Run dotnet install tool again (important that --prerelease is specified!!)
Image

@and-hus
Copy link
Contributor

and-hus commented Sep 24, 2024

The process works for me smoothly, without any token update or change to sources. I have nuget.org configured as the only source:
Screenshot4

Screenshot3

The --prerelease options is currently required, because no full release was published yet.

From your screenshots I see that you are installing v2.0.4-build-20240924-2 - which is not available on nuget.org.
I assume your process is retrieving the package from github. That might be the reason, why you need to provide the token. Can you try on a system that has only nuget.org configured?

@baseTwo baseTwo removed the Enhancement New feature or request label Oct 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Help Wanted Extra attention is needed Packaging
Projects
None yet
Development

No branches or pull requests

2 participants