-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ExcludedVMLists property support for finding keywords in a VM name #44
Comments
@rjhernandez That's correct. As mentioned in the doc '*' wildcard will have to use as suffix. For example if you have VMs with AZdev1, AZdev2 then you can specify AZ* |
Yikes, that does not work with my naming conventions. Can you point me to the doc? URL? The one I referenced does not seem to have those details. |
@rjhernandez Closing this issue, but do reply back if you need further assistance. Thanks! |
Thanks for the info @raldaba, I got to say, I am really disappointed in the limitations of this tool. Is there anywhere else where I can drop feature suggestions, or maybe even contribute code for this tool? |
Problem
I am trying to exclude a set of machines from being
started
on a schedule that are part of the includedResourceGroups
but the name contains a specific key word. During my tests, theExcludedVMLists
expression is being ignored. Is the use of star (*) as part of the beginning of the expression not supported?Example configuration of
ststv2_vms_ScheduleStart_start
Ref: https://docs.microsoft.com/en-us/azure/azure-functions/start-stop-vms/deploy#scheduled-start-and-stop-scenario
The text was updated successfully, but these errors were encountered: