[Mgmt] Add baseUrl customization for track2 SDK
See original GitHub issueCurrently we are using
baseUri: options.endpoint || "https://management.azure.com/"
in mgmt plane track2 SDK track2 link. which is different from what we did in the track1 SDK link
this.baseUri = options.baseUri || this.baseUri || "https://management.azure.com";
I wonder why we remove the support of baseUri customization and use endpoint instead ?
customer suggest us to change it into
baseUri: options.endpoint ?? options.baseUri ?? "https://management.azure.com/"
see original issue here https://github.com/Azure/azure-sdk-for-js/issues/20651
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
options.baseUri is always overwritten by options.endpoint in ...
WebSiteManagementClient constructor ignores and overwrites the value of options.baseUri on the options: WebSiteManagementClientOptionalParams ...
Read more >autorest-az - npm
Azure CLI Code Generator is an Autorest extension which generates functional Azure CLI code for Azure services by using Swagger specifications ...
Read more >JBrowse 2 guide
These tracks provide the user with access to the filterable track and datapoints retrieved through the GDC API. Adding files via the add...
Read more >Azure API Management Base URL - CLI Command
My APIM currently have multiple custom domains in it. My question is, how do you associated an API to a particular custom domain...
Read more >Blog - Developer Docs
Added production URL; Redesigned app icons; Handle empty api base url ... Handle empty api base url; Change pending advice string ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@bterlson, I think
baseUri
was inherited fromcore-http
and we didn’t get rid of it 😞 in favor of endpoint. I think the way we can proceed right now is with 3 changes:baseUri
, as Brian mentioned,endpoint
should win overbaseUri
if both are present.endpoint
to the ServiceClientOptions incore-client
next tobaseUri
, also markbaseUri
as deprecated to discourage users from using it, so that in the next major bump we take we can removebaseUri
endpoint
from the generated code as it extends ServiceClientOptions and would getendpoint
from there@bterlson I guess this is probably because data plane is using endpoint since track1 and mgmt plane on the other hand is using baseUri. @joheredi feel free to correct me if I am wrong. Thanks