Skip to content
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

Closed
rjhernandez opened this issue Jan 13, 2022 · 5 comments
Closed

Comments

@rjhernandez
Copy link

rjhernandez commented Jan 13, 2022

Problem

I am trying to exclude a set of machines from being started on a schedule that are part of the included ResourceGroups but the name contains a specific key word. During my tests, the ExcludedVMLists 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

{
  "Action": "start",
  "EnableClassic": false,
  "RequestScopes": {
    "ResourceGroups": [
      "/subscriptions/11111111-0000-1111-2222-444444444444/resourceGroups/rg2/"
    ],
    "ExcludedVMLists": [
      "*doNotStart*"
    ]
  }
}

Ref: https://docs.microsoft.com/en-us/azure/azure-functions/start-stop-vms/deploy#scheduled-start-and-stop-scenario

@balas77
Copy link
Contributor

balas77 commented Jan 14, 2022

@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*

@rjhernandez
Copy link
Author

rjhernandez commented Jan 16, 2022

@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.

@balas77
Copy link
Contributor

balas77 commented Jan 27, 2022

@raldaba
Copy link
Member

raldaba commented Jan 31, 2022

@rjhernandez Closing this issue, but do reply back if you need further assistance. Thanks!

@raldaba raldaba closed this as completed Jan 31, 2022
@rjhernandez
Copy link
Author

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants