Azure / Azure/AzureStackHCI-EvalGuide
Multiple Eval instances in the same Tenant/Sub
- Dominant language
- PowerShell
- Stars
- 142
- Forks
- 81
- PR merge metrics
- No merged PRs in 30d
Description
What files/parameters need to be modified so that my team can deploy multiple instances of an Eval HCI cluster in a single tenant/sub? My team has a need to have an HCI instance for each dev to work independently. Since each HCI instance will create app registrations, when using the guided eval to create the instance it does not have the flexibility to change the name of the cluster and therefor the app registrations.
Is there a way for us to edit scripts that get run to provide the uniqueness?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the guided eval scripts and the parameters used to name the HCI cluster and its app registrations. Determine whether those names can be made unique per deployment; done would mean documenting the required changes or providing a supported way to deploy multiple instances in one tenant/subscription.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, powershell
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100