You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When importing resources using asoctl, it synthesizes resource names based on the hierarchy of ownership in order to generate unique names for every resource.
This means that we generate different names based on which root is specified for import - importing an entire resource group will give different resource names compared to importing something more specific.
Describe the improvement
Ideally, we'd generate the same names for resources regardless of the root used for the import. Even better, if we only synthesize unique names where required - if they're already unique, use the names directly from Azure.
The current approach is generating some long names with odd repetitions.
It seems like [asoctl importing] the resource group gets the correct owner, but pointing at the CosmosDB Database Account duplicates it wrongly owner: name: bulksend-cosmosdb-preview-nld2-bulksend-cosmosdb-preview-nld2 (edited)
Describe the current behavior
When importing resources using
asoctl
, it synthesizes resource names based on the hierarchy of ownership in order to generate unique names for every resource.This means that we generate different names based on which root is specified for import - importing an entire resource group will give different resource names compared to importing something more specific.
Describe the improvement
Ideally, we'd generate the same names for resources regardless of the root used for the import. Even better, if we only synthesize unique names where required - if they're already unique, use the names directly from Azure.
The current approach is generating some long names with odd repetitions.
Additional context
Reported on Slack.
The text was updated successfully, but these errors were encountered: