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

StackHCI Registration process Improvements #18230

Merged
merged 10 commits into from
May 24, 2022

Conversation

bniranjanbhat
Copy link
Contributor

@bniranjanbhat bniranjanbhat commented May 18, 2022

Description

Checklist

  • I have read the Submitting Changes section of CONTRIBUTING.md
  • The title of the PR is clear and informative
  • The appropriate ChangeLog.md file(s) has been updated:
    • For any service, the ChangeLog.md file can be found at src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
    • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header -- no new version header should be added
  • The PR does not introduce breaking changes
  • If applicable, the changes made in the PR have proper test coverage
  • For public API changes to cmdlets:
    • a cmdlet design review was approved for the changes in this repository (Microsoft internal only)
      • {Please put the link here}
    • the markdown help files have been regenerated using the commands listed here

@bniranjanbhat bniranjanbhat changed the title StackHCI Registration Improvements StackHCI Registration process Improvements May 18, 2022
@bniranjanbhat bniranjanbhat marked this pull request as ready for review May 18, 2022 15:13
@bniranjanbhat bniranjanbhat requested a review from isra-fel May 18, 2022 17:36
@VeryEarly
Copy link
Contributor

/azp run

@azure-pipelines
Copy link
Contributor

Azure Pipelines successfully started running 3 pipeline(s).

@VeryEarly VeryEarly self-assigned this May 23, 2022
@VeryEarly
Copy link
Contributor

/azp run

@azure-pipelines
Copy link
Contributor

Azure Pipelines successfully started running 3 pipeline(s).

@VeryEarly VeryEarly merged commit 044b566 into Azure:main May 24, 2022
- Register-AzStackHCI cmdlet now does not take any action if required Resource Providers are already registered. This allows users with Roles who do not have permissions to register resource providers to still perform registration operation
* Supported for writing event log entries from registration cmdlets
- Register-AzStackHCI and UnRegister-AzStackHCI flows will now write events to Node log reflecting the status of registration. Events will be logged under source name "HCI Registration"
* Updated IMDS Cluster network
Copy link
Contributor

@bnichms bnichms May 24, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change was already released in 1.1.1

@@ -4689,16 +4771,26 @@ function New-Directory{
#>
function Invoke-DeploymentModuleDownload{
# Remote Support
New-Variable -Name RemoteSupportPackageUri -Value "https://remotesupportpackages.blob.core.windows.net/packages" -Option Constant -Scope Script
New-Variable -Name RemoteSupportPackageUri -Value "https://srsqldatasa.blob.core.windows.net/packages" -Option Constant -Scope Script
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do not bring this change over (or anything related to RS except for logging/etc).

}

$ServiceEndpointAzureCloudFrontDoor = "https://azurestackhci.azurefd.net"
$ServiceEndpointAzureCloudFrontDoor = "https://dp.stackhci.azure.com"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you also bring over the Fairfax graph endpoint update?
$GraphServiceApiScopeAzureUSGovernment = "https://graph.windows.net/.default"
should change to
$GraphServiceApiScopeAzureUSGovernment = "https://graph.microsoft.us/.default"

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

Successfully merging this pull request may close these issues.

4 participants