This repository was archived by the owner on Dec 6, 2023. It is now read-only.
Adding Hyperv and server fabric support to dependency mapping powershell commands ( earlier limited to only VMware) #421
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rohan-dassani
changed the title
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Get-AzMigDiscoveredVMwareVMs will now create a CSV consisting of all machines across all appliances in the project for all fabrics. We also have an optional $ApplianceName parameter if someone wants to get list of machines only for that appliance
Set-AzMigDependencyMappingAgentless can now take input of ARMIDs of machines of any fabric in any of the appliances
Get-AzMigDependenciesAgentless will now work with any appliance not limited to vmware fabric