-
Notifications
You must be signed in to change notification settings - Fork 279
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
Masking schedules between date ranges #469
Comments
hi @Idosegal I'm not sure I completely follow, could you give an example scenario and explain what you would like to be able to achieve with Instance Scheduler in that scenario? |
Hi thank you for your response. Sometimes there are exceptions and the environment should be up So we want to do the instance scheduler like "self service" and give the qa for example the ability to change the period for a schedule in a simple way and get back to the default period when the time passed- to avoid people to forget change it back to the default manually. For example: I hope it's more clear now. |
Hi @Idosegal Have you looked into using the feature in SSM called Resource Scheduler, Resource Scheduler creates State Manager resources for the default start/stop, Resource Scheduler also creates a change calendar, where you can temporarily override the default start and stop times. |
But it possible to use it within the solution, or I need to configure it outside? |
Hi @Idosegal |
There are cases which environments needs to be up for a different reasons.
For example: QA needs the environment up for a specific date range because of testing before a new version release etc.
This issue opened to verify if it's possible and if not to implement an automatic way to "mask" schedules for specific date range and get back to a default value when the end date passed.
It's possible to specify 'datemonth' but there is no way to specify the year.
In case that a year can be used in period I can use the cli to update a custom period in addition to a default one.
But current behavior will run the instances every year in the date range provided.
The text was updated successfully, but these errors were encountered: