[BUG] Run Publisher fails from version 5.1.0

[ttfreeman]

Release version

5.1.0 and 5.1.1

Describe the bug

Run - Publisher workflow for github actions fails at step "Run publisher with Config yaml and Commit id" . This is due to $uri for "https://github.com/Azure/apiops/releases/download/v5.0.0/$publisherFileName" no longer requires .exe in publisherFileName .

Expected behavior

It was working up to version v5.0.1. It stopped working from version v5.1.0 because Power shell API request to URI "https://github.com/Azure/apiops/releases/download/v5.0.0/$publisherFileName" throws a not found error. Run Set-StrictMode -Version Latest Downloading publisher... VERBOSE: Requested HTTP/1.1 GET with 0-byte payload VERBOSE: Received HTTP/1.1 77265990-byte response of content type application/octet-stream VERBOSE: File Name: publisher.exe Setting file permissions... dbug: Microsoft.Extensions.Hosting.Internal.Host[1] Hosting starting info: Publisher[0] Beginning execution... info: Publisher[0] Getting files from commit ID 9ec3aa44acc78fa10e11517eb454812774af6549... info: Microsoft.Hosting.Lifetime[0] Application started. Press Ctrl+C to shut down. info: Microsoft.Hosting.Lifetime[0] Hosting environment: Production info: Microsoft.Hosting.Lifetime[0] Content root path: /home/runner/work/KuvaCloud/KuvaCloud dbug: Microsoft.Extensions.Hosting.Internal.Host[2] Hosting started info: Publisher[0] Processing modified files in commit ID... info: Publisher[0] Putting named value alarm-backend-kuva... info: Publisher[0] Putting named value alarm-backend-dvn... dbug: PutRestResource[0]

Actual behavior

Run Set-StrictMode -Version Latest Downloading publisher... VERBOSE: Requested HTTP/1.1 GET with 0-byte payload VERBOSE: Received HTTP/1.1 response of content type text/html of unknown size Invoke-WebRequest: /home/runner/work/_temp/1a9902ba-17c4-4807-8fa7-6c247945bde0.ps1:11 Line | 11 | Invoke-WebRequest -Uri "$uri" -OutFile "$destinationFilePath" | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| {"locale":"en","featureFlags":["copilot_conversational_ux_history_refs","docset_management_ui","failbot_handle_non_errors","geojson_azure_maps","image_metric_tracking","turbo_experiment_risky","sample_network_conn_type","no_character_key_shortcuts_in_inputs","custom_inp","remove_child_patch"]} Page not found · GitHub · GitHub Skip to content {"props":{}} Toggle navigation Sign in Product Actions Automate any workflow Packages Host and manage packages Security Find and fix vulnerabilities Codespaces Instant dev environments Copilot Write better code with AI Code review Manage code changes Issues Plan and track work Discussions Collaborate outside of code Explore All features Documentation GitHub Skills Blog Solutions For Enterprise Teams Startups Education By Solution CI/CD & Automation DevOps DevSecOps Resources Learning Pathways White papers, Ebooks, Webinars Customer Stories Partners Open Source GitHub Sponsors Fund open source developers The ReadME Project GitHub community articles Repositories Topics Trending Collections Pricing "> Search or jump to... Search code, repositories, users, issues, pull requests... --> Search Clear Search syntax tips Provide feedback --> We read every piece of feedback, and take your input very seriously. Include my email address so I can be contacted Cancel Submit feedback Saved searches Use saved searches to filter your results more quickly --> Name Query To see all available qualifiers, see our documentation. Cancel Create saved search Sign in Sign in to GitHub --> Username or email address Password Forgot password? or sign in with a passkey Sign up You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert {{ message }} --> Find code, projects, and people on GitHub: Search Contact Support — GitHub Status — @githubstatus Subscribe to our developer newsletter Get tips, technical guides, and best practices. Twice a month. Right in your inbox. Subscribe Product Features Enterprise Copilot Security Pricing Team Resources Roadmap Compare GitHub Platform Developer API Partners Electron GitHub Desktop Support Docs Community Forum Professional Services Premium Support Skills Status Contact GitHub Company About Customer stories Blog The ReadME Project Careers Press Inclusion Social Impact Shop GitHub on X GitHub on Facebook GitHub on LinkedIn GitHub on YouTube GitHub on Twitch GitHub on TikTok GitHub’s organization on GitHub © 2024 GitHub, Inc. Terms Privacy (Updated 08/2022) Sitemap What is Git? Manage cookies Do not share my personal information You can’t perform that action at this time. Error: Process completed with exit code 1.

Reproduction Steps

Try running Run Publisher .

[github-actions[bot]]

  Thank you for opening this issue! Please be patient while we will look into it and get back to you as this is an open source project. In the meantime make sure you take a look at the [closed issues](https://github.com/Azure/apiops/issues?q=is%3Aissue+is%3Aclosed) in case your question has already been answered. Don't forget to provide any additional information if needed (e.g. scrubbed logs, detailed feature requests,etc.).
  Whenever it's feasible, please don't hesitate to send a Pull Request (PR) our way. We'd greatly appreciate it, and we'll gladly assess and incorporate your changes.

[waelkdouh]

Please try 5.1.1. Make sure you dose the pipelines as well with this version.

[ttfreeman]

Please try 5.1.1. Make sure you dose the pipelines as well with this version.

5.1.1 is the same, as mentioned in the issue description. I noticed two new issues for the same problem: https://github.com/Azure/apiops/issues/494 https://github.com/Azure/apiops/issues/486

[waelkdouh]

Please get the latest release and let us know if this issue persists.

[waelkdouh]

Also make sure you are using the latest pipeline yaml files.

[ttfreeman]

We tried updating to version 5.1.3. Now we get the following error in the publisher workflow (so still stuck at version 5.0.0):

[waelkdouh]

Did you also update the pipelines?

[ics-development]

I'm having the issue with revisions after updating to 5.1.4:

"code":"IdentifierAlreadyInUse","message":"Resource already exists."

info: Publisher[0] Putting product ipoint-shifts... ##[debug]Agent environment resources - Disk: / Available 20946.00 MB out of 74244.00 MB, Memory: Used 681.00 MB out of 6921.00 MB, CPU: Usage 25.36% info: Publisher[0] Putting policy policy in product ipoint-shifts... info: Publisher[0] Putting API ipoint-shifts;rev=1... info: Publisher[0] Putting API ipoint-shifts... crit: Publisher[0] System.Net.Http.HttpRequestException: HTTP request to URI https://management.azure.com/subscriptions/***/resourceGroups/rg-apim-staging/providers/Microsoft.ApiManagement/service/apim-acacium-staging/apis/ipoint-shifts;rev=1?api-version=2022-04-01-preview&asyncId=66361c34217d201b2473497f&asyncCode=201 failed with status code 409. Content is '{"error":{"code":"IdentifierAlreadyInUse","message":"Resource already exists.","details":null}}'.

[waelkdouh]

Publishing APIs with revisions is currently bugged. We will include a fix in our next major release (sometime in the next week or so). It will be release as part of V6. We are currently testing some alpha versions of v6 but it has some issues and it's not ready for you to start consuming yet. Stay tuned.

[ics-development]

@waelkdouh awesome, will do, thank you. Appreciate your hard work.

[guythetechie]

Please try our latest release, revision issues have been addressed there.