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

[Bug]: VMware applications fail due to changes to product API #678

Open
2 tasks done
aaronparker opened this issue May 7, 2024 · 1 comment
Open
2 tasks done
Labels
bug Something isn't working vendor issue An issue with the source data from the vendor

Comments

@aaronparker
Copy link
Owner

aaronparker commented May 7, 2024

What happened?

Recent changes to the VMware products and the move Omnissa have broken the available updates from the products API at: https://customerconnect.vmware.com/channel/public/api/v1.0/products/getProductsAtoZ

These will likely remain broken until the new Omnissa downloads site is live and working, and assuming it will also provide a similar API.

This affects:

  • VMwareHorizonClient
  • VMwareOSOptimizationTool
  • VMwareSDWANClient
  • VMwareWorkstationPlayer
  • VMwareWorkstationPro

Version

2405.994

What PowerShell edition/s are you running Evergreen on?

PowerShell Core, Windows PowerShell

Which operating system/s are you running Evergreen on?

Windows 10+, macOS

Have you reviewed the documentation?

Verbose output

VERBOSE: Function path: /Users/aaron/projects/evergreen/Evergreen/Apps/Get-VMwareWorkstationPro.ps1
VERBOSE: Function exists: /Users/aaron/projects/evergreen/Evergreen/Apps/Get-VMwareWorkstationPro.ps1.
VERBOSE: Dot sourcing: /Users/aaron/projects/evergreen/Evergreen/Apps/Get-VMwareWorkstationPro.ps1.
VERBOSE: Get-FunctionResource: read application resource strings from [/Users/aaron/projects/evergreen/Evergreen/Manifests/VMwareWorkstationPro.json]
VERBOSE: Calling: Get-VMwareWorkstationPro.
VERBOSE: Get-VMwareAPIPath: Return https://customerconnect.vmware.com/channel/public/api/v1.0/products
VERBOSE: Invoke-EvergreenRestMethod: Invoke-RestMethod parameter: ContentType: application/json; charset=utf-8.
VERBOSE: Invoke-EvergreenRestMethod: Invoke-RestMethod parameter: DisableKeepAlive: True.
VERBOSE: Invoke-EvergreenRestMethod: Invoke-RestMethod parameter: Method: Default.
VERBOSE: Invoke-EvergreenRestMethod: Invoke-RestMethod parameter: MaximumRedirection: 2.
VERBOSE: Invoke-EvergreenRestMethod: Invoke-RestMethod parameter: UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36 Edg/124.0.2478.67.
VERBOSE: Invoke-EvergreenRestMethod: Invoke-RestMethod parameter: Uri: https://customerconnect.vmware.com/channel/public/api/v1.0/products/getProductsAtoZ.
VERBOSE: Invoke-EvergreenRestMethod: Invoke-RestMethod parameter: UseBasicParsing: True.
VERBOSE: Requested HTTP/1.1 GET with 0-byte payload
VERBOSE: Received HTTP/1.1 response of content type text/html of unknown size
VERBOSE: Content encoding: utf-8
Get-VMwareProductDownload: /Users/aaron/projects/evergreen/Evergreen/Apps/Get-VMwareWorkstationPro.ps1:17
Line |
  17 |          Get-VMwareProductDownload | `
     |          ~~~~~~~~~~~~~~~~~~~~~~~~~
     | The input object cannot be bound to any parameters for the command either because the command does not take pipeline input or the input and its
     | properties do not match any of the parameters that take pipeline input.
@aaronparker aaronparker added bug Something isn't working vendor issue An issue with the source data from the vendor labels May 7, 2024
@aaronparker aaronparker changed the title [Bug]: VMware EUC applications fail due to changes to product API [Bug]: VMware applications fail due to changes to product API May 19, 2024
@aaronparker
Copy link
Owner Author

I'll be removing these applications from Evergreen for the time being. It's likely the API used to find downloads is not going to be available on the Broadcom site and changes at Omnissa are still on-going

aaronparker added a commit that referenced this issue May 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working vendor issue An issue with the source data from the vendor
Projects
None yet
Development

No branches or pull requests

1 participant