Hi just righting a bit of Azure(RM) Powershell - currently octopus comes with AzureRM… had issue running Az.sql command, as not there when listing all Azure modules in script got following out put…
I was able to do what I needed with AzureRm.Sql included.
Through Microsoft support site had following…
“You’ve reached a webpage for an outdated version of Azure PowerShell. All versions of the AzureRM PowerShell module are outdated, but not out of support.”
I’m going to reach out to some colleagues to get a definitive answer for you on this one. I believe we’re leveraging containers for tools going forward, but I want to be certain that’s still the case.
I heard back. We don’t have plans to update the bundled tools as it may cause issues for customers when versions change unexpectedly and functionality changes within the tool.
If you go that route, you could create runbooks or use the script console to keep tentacles and workers up to date with local tools, but keep in mind the service will need to be restarted each time you install local tools.
Please let me know if that helps or if you need further assistance.
Thanks Jeremy - totally understand - except for the bit about Execution Containers - but I suppose the bed time reading you’ve provided should help with that.
Essentially the execution containers are docker images that workers can utilize where the versions of the tooling are updated as needed. It allows people to select the tool versions they want, rather than whatever we choose to give them. The documentation will probably do a better job of explaining it than I can, but please reach out if you get stuck and need any help along the way and we can work on it together.