silverl
commented
1 year ago For a possible repro, try this:
- Have 5-10 runbooks in a folder.
- Publish the first and while it's publishing, attempt to click on the next in line.
- Sometimes the load fails, I presume because the process is busy with the previous task. I've seen an error toast in the lower right occasionally with this process when trying to work rapidly.
- I suspect the problem lies here somewhere. The next runbook clicked highlights in the left pane, but does not load in a tab. Right-clicking on the next runbook and choosing Publish may not publish the intended runbook, but perhaps instead the previous one or the one in the active tab (not sure.
Swatidevgan
Using Azure Automation VS Code extension version
v1.2.1.Something pretty horrible just happened.
We needed to update 54 runbooks in production because for some reason, Azure Automation started failing yesterday to import a custom powershell 7.1 module we published months ago. Just wouldn't load it. We have a high severity ticket open with Azure support right now trying to figure out what's going on.
We opted to inline the code from the module that is failing to import directly into the runbooks and proceeded to use your extension to one-by-one republish all the runbooks.
Microsoft hasn't provided a powershell module that can publish a 7.1 runbook and we can't find an API that can do it, or else we'd automate this. Also, git sync doesn't work yet for 7.1 runbooks.
After this manual publishing exercise, we found over half the runbooks were overwritten with whatever runbook that was in the open VS Code tab instead of the runbook we specifically right-clicked and hit Publish for.
This has caused all kinds of problems, as you can imagine. We had to resort to going one-by-one in the portal and using the in-browser editor to republish those 54 runbooks.