In the attached image there is a field for Script Parameters that I can’t see in our 3.3.2 installation. Does anyone know if that turned up in a later version or if I should look for some other reason for that gone missing? (I just want to check before I go ahead with an upgrade that turns out not to fix that)
Please make sure that when the feature gets released it covers the Azure variant of Script file from package.
What would be the best way to do something similar now?
I would be running this on a server that doubles as octopus server and tentacle so I could do “Deploy package” to a known file location and then do “Run Azure Powershell script” using that location since it is going to be on the same “physical” server. (Cleanup afterwards as well)
The package contains a lot more than the script itself that will be used by the script.
Yeah its a good enhancement (I was the one vouching for it on the team ). Sadly its still not quite there, as it implicated a bit more work than we expected.
Attached screenshot shows a sneak-peak at the commits as proof that we already though about Azure steps
That approach you described is what I’d do to workaround this.
Can you do a Hard Refresh of your Octopus tab? Sometimes you need to do this to see the front-end changes if you had the Octopus tab open while you were still in a prior version.