Skip to content

Conversation

@BernieEllis
Copy link
Contributor

@BernieEllis BernieEllis commented Oct 20, 2017

Description

Updated the USGovernmentActiveDirectoryEndpoint from login-us.microsoftonline.com to login.microsoftonline.us in AzureEnvironmentConstants.

This checklist is used to make sure that common guidelines for a pull request are followed. You can find a more complete discussion of PowerShell cmdlet best practices here.

General Guidelines

  • [Yes] Title of the pull request is clear and informative.
  • [Yes] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.
  • [No breaking changes] The pull request does not introduce breaking changes (unless a major version change occurs in the assembly and module).

Testing Guidelines

  • [N/A] Pull request includes test coverage for the included changes.
  • [N/A] PowerShell scripts used in tests should do any necessary setup as part of the test or suite setup, and should not use hard-coded values for locations or existing resources.

Cmdlet Signature Guidelines

  • [N/A] New cmdlets that make changes or have side effects should implement ShouldProcess and have SupportShouldProcess=true specified in the cmdlet attribute. You can find more information on ShouldProcess here.
  • [N/A] Cmdlet specifies OutputType attribute if any output is produced - if the cmdlet produces no output, it should implement a PassThru parameter.

Cmdlet Parameter Guidelines

  • [N/A] Parameter types should not expose types from the management library - complex parameter types should be defined in the module.
  • [N/A] Complex parameter types are discouraged - a parameter type should be simple types as often as possible. If complex types are used, they should be shallow and easily creatable from a constructor or another cmdlet.
  • [N/A] Cmdlet parameter sets should be mutually exclusive - each parameter set must have at least one mandatory parameter not in other parameter sets.

@cormacpayne
Copy link
Member

@azuresdkci test this please

@cormacpayne
Copy link
Member

@bernie-msft thanks for the PR, Bernarldo. This looks good to me, we just need to do some light validation on our side to ensure both endpoints work.

As a note to myself, the URL has changed, but the old one will continue to be supported moving forward, according to this article:

The Active Directory Authority for Azure Government has changed from https://login-us.microsoftonline.com to https://login.microsoftonline.us. The original URL will continue to work but all applications should be updated to the new authority URL.

@markcowl markcowl changed the base branch from preview to release-5.0.0 November 6, 2017 18:38
markcowl
markcowl previously approved these changes Nov 6, 2017
@markcowl
Copy link
Member

markcowl commented Nov 6, 2017

@BernieEllis
Copy link
Contributor Author

Thanks Mark,

#sign-off

@cormacpayne cormacpayne changed the base branch from release-5.0.0 to preview November 14, 2017 16:32
@BernieEllis
Copy link
Contributor Author

Hi, I signed off on this. Was it ever merged?

@cormacpayne
Copy link
Member

@bernie-msft I was able to log-in and run a few cmdlets in the AzureUSGovernment cloud with the new AD endpoint. This should be good to merge.

@cormacpayne
Copy link
Member

@bernie-msft before we merge this, our team is discussing how we want to do versioning around this change (since it touches common code used by all of the modules we ship). Once we figure that out, we will merge this.

@BernieEllis
Copy link
Contributor Author

BernieEllis commented Nov 27, 2017 via email

@cormacpayne
Copy link
Member

@cormacpayne cormacpayne removed their assignment Nov 29, 2017
@cormacpayne cormacpayne merged commit 0e40f91 into Azure:preview Nov 30, 2017
@BernieEllis
Copy link
Contributor Author

BernieEllis commented Nov 30, 2017 via email

@cormacpayne
Copy link
Member

@bernie-msft our upcoming release is next Friday (12/8), so it will be available then

@BernieEllis
Copy link
Contributor Author

BernieEllis commented Nov 30, 2017 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants