-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
[Cloud] Perform cloud discovery with API Version 2022-09-01 and support dataplaneEndpoints
for Azure Stack
#25834
base: dev
Are you sure you want to change the base?
Conversation
️✔️acr
️✔️acs
️✔️advisor
️✔️ams
️✔️apim
️✔️appconfig
️✔️appservice
️✔️aro
️✔️backup
️✔️batch
️✔️batchai
️✔️billing
️✔️botservice
️✔️cdn
❌cloud
️✔️cognitiveservices
️✔️config
️✔️configure
️✔️consumption
️✔️container
️✔️core
️✔️cosmosdb
️✔️databoxedge
️✔️dla
️✔️dls
️✔️dms
️✔️eventgrid
️✔️eventhubs
️✔️feedback
️✔️find
️✔️hdinsight
️✔️identity
️✔️iot
️✔️keyvault
️✔️kusto
️✔️lab
️✔️managedservices
️✔️maps
️✔️marketplaceordering
️✔️monitor
️✔️netappfiles
️✔️network
️✔️policyinsights
️✔️privatedns
️✔️profile
️✔️rdbms
️✔️redis
️✔️relay
️✔️resource
️✔️role
️✔️search
️✔️security
️✔️servicebus
️✔️serviceconnector
️✔️servicefabric
️✔️signalr
️✔️sql
️✔️sqlvm
️✔️storage
️✔️synapse
️✔️telemetry
️✔️util
️✔️vm
|
Cloud enhancement |
Although the main post mentioned that a new nested group called
The method is from this deprecated library: https://github.com/Azure/msrestazure-for-python/blob/8e3def8c9927a349596e575de93df76de7a3a2b6/msrestazure/azure_cloud.py#L204 |
If these new suffixes and endpoints are not passed by a
We can certainly update Reading all endpoints and suffixes is simply against our modeling principal which enforces all endpoints to be an attribute of the cloud object. Of course, we can leverage |
The new endpoints and suffixes will appear in the GET request to the metadata endpoint URL.
Is there a reason there is an exception made for reading all endpoints and suffixes from the cloudconfig.json but not from the metadata endpoint?
|
I didn't write that code, but I guess it is because |
@jiasli Bumping this. FYI 2022-09-01 is a breaking change for the metadata endpoint. Prior versions returned a JSON array of cloud endpoints for multiple environments. This version returns a single JSON object for the endpoints associated with the ARM instance being queried. Is the goal to support both schemas with this for backwards compatibility? |
|
||
|
||
# The exact API version doesn't matter too much right now. It just has to be YYYY-MM-DD format. | ||
METADATA_ENDPOINT_SUFFIX = '/metadata/endpoints?api-version=2022-09-01' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
msrestazure
current uses 2015-01-01
API version: https://management.azure.com/metadata/endpoints?api-version=2015-01-01
> az cloud register -n myazurestack --endpoint-resource-manager https://management.azure.com/ --debug
...
urllib3.connectionpool: https://management.azure.com:443 "GET //metadata/endpoints?api-version=2015-01-01 HTTP/1.1" 200 295
Related command
az cloud
Description
Close #25815
Testing Guide
Populate
dataplaneEndpoints
from metadata:Populate
dataplaneEndpoints
from local cloud config JSON file: