Question about Nuget #1674
Replies: 1 comment
-
If you are using a feed on Azure DevOps, then your nuget token needs to be a PAT from Azure DevOps. Note that the delivery mechanism in AL-Go for GitHub delivers FULL app packages - not runtime packages and not symbols packages. AppSource validation automatically publishes symbols for all appsource apps and the appsource symbols feed is automatically trusted by AL-Go for GitHub, so for the symbols story, you don't really need to do anything. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
first of all , the nuget system is a life + time saver , it really helps getting what you need from appsource instead of asking for runtime packages from ISVs each nextmajor (ofc if nextmajor version is available) , I only have some questions to fully understand it:
1. when does my Appsource app's nuget get generated ?
2. what value do i need to add to NuGetContext Token ? is it the same as GHTOKENWORKFLOW that needs to be generated from a classic token ? if it is which permissions do i need add to my NuGetContext ?
3. and based on my understanding , the NuGetContext will automagically send the "app symbol" if i m not mistaken to the Nuget feed that i configured in Deliver to the nuget feed , so any app Appsource App or PTE App can be used to generate a symbol that will be delivered as nuget ?
4. Here , i tried to a delivery to nuget for my PTE App : using this NugetContext :

{"token":"ghp_TzS7QXYZ...","serverUrl":"https://pkgs.dev.azure.com/*****-cli****/apps/_packaging/Test-appDependency/nuget/v3/index.
json"}
i wasn't sure which permissions to add so i added multiple ones just for testing before starting a new discussion here but i got an error :
let me know if the log files are needed for more information
Beta Was this translation helpful? Give feedback.
All reactions