Comments (7)
gunnim
commented on May 30, 2024
1
Managed to beat the powershell azure setup scripts into submission and have some step-by-step instructions for usage of that and upload of package afterwards.
https://github.com/gunnim/winget-restsource
HTH !
from winget-cli-restsource.
commented on May 30, 2024
I've been spending a lot of time looking through the pipeline YAML files, and there's a lot that's done there that's not done when building locally. These steps are critical for the cmdlets to actually work. I'll add more details as I continue to work through this.
from winget-cli-restsource.
commented on May 30, 2024
After spending many hours working on this, I was unsuccessful in getting the automated approach to work and just finally went with a completely manual approach as outlined in the new-winget-rest-source-azure.md document.
This isn't only a doc issue, there's bugs in the cmdlet itself and there's files (such as asp.json) that are missing completely.
from winget-cli-restsource.
RDMacLachlan
commented on May 30, 2024
Hi @ameltzerMSFT, we appreciate the feedback on your experience. I will be looking through your different Issue's that you've logged from your experience and see what we can do to improve upon the experience.
from winget-cli-restsource.
commented on May 30, 2024
Thanks! I was trying to get this to work building/running from source versus trying the released module which may be in a different functional state.
from winget-cli-restsource.
RDMacLachlan
commented on May 30, 2024
The PowerShell Module has a dependency on a HelperLib file that is used by another section of code in the project. So, to ensure the experience is shared across two separate tools we include a copy of the HelperLib in the Released PowerShell Module.
Sorry for the confusion when trying to use the PowerShell scripts.
from winget-cli-restsource.
jmservera
commented on May 30, 2024
After spending many hours working on this, I was unsuccessful in getting the automated approach to work and just finally went with a completely manual approach as outlined in the new-winget-rest-source-azure.md document.
This isn't only a doc issue, there's bugs in the cmdlet itself and there's files (such as asp.json) that are missing completely.
I downloaded the last release and followed the step by step many times, but I still get the issue, it asks for a manifestCacheEndPoint value and when looking at the $Error shows that the asp.json is missing:
PS C:\> New-WinGetSource -Name "jmrestsource" -ResourceGroup "WinGet" -Region "northeurope" -ImplementationPerformance "Demo" -ShowConnectionInstructionswConnectionInstructions
WARNING:
The "Demo" build creates the Azure Cosmos DB Account with the "Free-tier" option selected which offset the total cost. Only 1 Cosmos DB Account per tenant can make use of this.
True
cmdlet Test-AzResourceGroupDeployment at command pipeline position 1
Supply values for the following parameters:
(Type !? for Help.)
manifestCacheEndpoint:
PS C:\> $Error
Test-AzResourceGroupDeployment: C:\Users\juanserv\Downloads\WinGet.RestSource-Winget.PowerShell.Source\WinGet.RestSource-Winget.PowerShell.Source\Library\Test-ARMTemplate.ps1:44
Line |
44 | … rceResult = Test-AzResourceGroupDeployment -ResourceGroupName $Resour …
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| Cannot retrieve the dynamic parameters for the cmdlet. Cannot find path
| 'C:\Users\juanserv\Downloads\WinGet.RestSource-Winget.PowerShell.Source\WinGet.RestSource-Winget.PowerShell.Source\Library\ARMTemplate\asp.json' because it does not exist.
Get-AzResourceGroup: C:\Users\juanserv\Downloads\WinGet.RestSource-Winget.PowerShell.Source\WinGet.RestSource-Winget.PowerShell.Source\Library\Add-AzureResourceGroup.ps1:62
Line |
62 | … $Result = Get-AzResourceGroup -Name $Name -ErrorAction SilentlyCont …
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| 9:23:36 AM - Provided resource group does not exist.
Get-Process: A positional parameter cannot be found that accepts argument 'Get-ChildItem'.But if I look into the generated Parameters file, there's an asp.json file there:
ls .\Parameters\
Directory: C:\temp\Parameters
Mode LastWriteTime Length Name
---- ------------- ------ ----
-a--- 1/31/2023 9:32 AM 214 applicationinsights.json
-a--- 1/31/2023 9:32 AM 375 asp.json
-a--- 1/31/2023 9:32 AM 729 azurefunction.json
-a--- 1/31/2023 9:32 AM 928 cosmosdb-sql-container.json
-a--- 1/31/2023 9:32 AM 400 cosmosdb-sql.json
-a--- 1/31/2023 9:32 AM 1609 cosmosdb.json
-a--- 1/31/2023 9:32 AM 679 keyvault.json
-a--- 1/31/2023 9:32 AM 346 storageaccount.jsonShould the command be run in a specific path?
I downloaded the latest script version in 1.1.20230126 and my current versions are:
PS C:\> $PSVersionTable.PSVersion
Major Minor Patch PreReleaseLabel BuildLabel
----- ----- ----- --------------- ----------
7 3 2
PS C:\> (get-module Az).Version
Major Minor Build Revision
----- ----- ----- --------
9 3 0 -1
PS C:\> (get-module Microsoft.WinGet.Source).Version
Major Minor Build Revision
----- ----- ----- --------
0 1 0 -1And if I just ignore the errors, some resources are deployed, but the Function App is missing:
from winget-cli-restsource.
Related Issues (20)
- Get-WinGetManifest does not work with .yaml files because it's relying on a missing variable HOT 1
- Get-WinGetManifest logic is broken around how it performs path detection HOT 1
- Completely broken HOT 1
- Unable to Invoke API Requests
- OpenApi definition: autorest
- How should a REST source handle different ManifestVersions?
- Full Offline / closed network capabilities including feed generation HOT 5
- Missing application settings under Azure function
- make a non azure referance implementation HOT 5
- Parameter missing in Automate the creation of a Windows Package Manager REST source HOT 2
- New-WinGetSource cmdlet doesn't exist HOT 1
- Select and upgrade like options HOT 3
- Add Manifest to Private Repo using "Add-WingetManifest" command failed. HOT 1
- Entra ID authentication
- Package installed from private repository is being listed as being installed from public repository HOT 6
- Unable to Create Rest Source HOT 4
- Installer `RepairBehavior` never used by the 1.7.0 API schema?
- Native Winget Repo Server for Windows Server HOT 6
- Deployment fails if there are multiple CosmosDB accounts in the RG HOT 1
- New-WinGetSource fails with Unauthorized error on publish-azwebapp HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from winget-cli-restsource.