updated Set-APUri to work with on-prem urls & resolve #1 #2
Conversation
This file contains 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
scrthq
commented
Jan 4, 2019
|
Post update validation:
|
The module version will get updated as part of the Invoke-Build. If the build is not invoked by the pipeline the version number will not increase. I will add a section to the development documentation.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
v1.0.1
Set-APIUrinow only prepends the URL for special API Endpoints (Release, Feeds, Graph, GroupEntitlements) when running against Azure DevOps Services (hosted) due to on-prem installations using the default base URI for everything.$env:APPDATAif not already preset soSave-APSessiondoesn't fail due to missing path segments.