The ability to Power a remote VM On or Off via Automated Activities or Life Cycle Actions could enhance the designer's capacity to manipulate the environment without user intervention during the lab. This could allow greater control and ensure that the only required VMs are powered on or off at a given time within the lab.
This functionality should also include the ability to query for the power state before changing it.
Who would most benefit from this idea? | Lab Developers or Lab Authors |
Thanks for taking a minute to send along this suggestion! Our Product Group has given this an initial review and assigned this a status of "Future Consideration." This status mean this Idea is not yet on our roadmap, but will be part of our normal prioritization processes.
If you have additional context or would like to generate more demand, feel free to edit your original post, add a comment, and/or invite your peers to upvote your Idea.
Moving this idea to "Future Consideration" for the next stage of evaluation