Thomas, im wondering what are really the benefits of this compared to using the PowerShell scripts or python code in an Azure DevOps Repos and create a pipeline that runs on a self-hosted agent that's on-premise ?
Thanks for sharing this! What's the recommendation for scripts / runbooks to be executed on all the nodes in the worker group? Currently it does seem to pick only node from the group and use it.
Yes that is the behavior we would expect from it. The group is more designed that if one of the workers is not available, another worker node would pick the script execution up. But yes this means only one node will run it. So if you need to run the commands against multiple server, I would recommend to build this into the script.
Great video! 3 questions: 1. Is there a cost for the automation workers account? Or is it free (especially since this solution runs the actual code on-prem) 2. Can I tie in publishing to an ADO Pipeline so that when I do a Pull Request it automatically uploads my script to Azure? 3. Can you do interactive use cases? For example maybe a script approaches a decision point where the user is asked if they want to proceed or not.
1. Check out the pricing page: azure.microsoft.com/en-us/pricing/details/automation/#pricing 2. Yes, with the Git integration learn.microsoft.com/en-us/azure/automation/source-control-integration 3. Well, you would need the script in a way that this would work. I don't have something in my head, but I am sure it can be done. That said, it is not really designed for that, and jobs might can timeout.
My runbook is forbidden by traffic filter of elastic cloud. Runbook is used for deleting data on elasticsearch after each 3 months. Does Hybrid Runbook Worker work in this situation ?. I need to add an ip in traffic filter of elastic cloud to allow runbook running
This get-vm is running locally in the Hyper-V host and lists all the VMs running on-premises on that spesific host/cluster. In Azure there is a Get-AzVM cmdlet, which is different.
Thomas, im wondering what are really the benefits of this compared to using the PowerShell scripts or python code in an Azure DevOps Repos and create a pipeline that runs on a self-hosted agent that's on-premise ?
😊
Thanks for sharing this! What's the recommendation for scripts / runbooks to be executed on all the nodes in the worker group? Currently it does seem to pick only node from the group and use it.
Yes that is the behavior we would expect from it. The group is more designed that if one of the workers is not available, another worker node would pick the script execution up. But yes this means only one node will run it. So if you need to run the commands against multiple server, I would recommend to build this into the script.
Great video! 3 questions:
1. Is there a cost for the automation workers account? Or is it free (especially since this solution runs the actual code on-prem)
2. Can I tie in publishing to an ADO Pipeline so that when I do a Pull Request it automatically uploads my script to Azure?
3. Can you do interactive use cases? For example maybe a script approaches a decision point where the user is asked if they want to proceed or not.
1. Check out the pricing page: azure.microsoft.com/en-us/pricing/details/automation/#pricing
2. Yes, with the Git integration learn.microsoft.com/en-us/azure/automation/source-control-integration
3. Well, you would need the script in a way that this would work. I don't have something in my head, but I am sure it can be done.
That said, it is not really designed for that, and jobs might can timeout.
Thanks for the information
My pleasure
My runbook is forbidden by traffic filter of elastic cloud. Runbook is used for deleting data on elasticsearch after each 3 months. Does Hybrid Runbook Worker work in this situation ?. I need to
add an ip in traffic filter of elastic cloud to allow runbook running
Is the get-vm query all vms on all subscription?
This get-vm is running locally in the Hyper-V host and lists all the VMs running on-premises on that spesific host/cluster.
In Azure there is a Get-AzVM cmdlet, which is different.