Skip to content
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

Use fully qualified ARM ID to identity importers #3203

Merged
merged 1 commit into from
Aug 22, 2023

Conversation

theunrepentantgeek
Copy link
Member

What this PR does / why we need it:

During import of an Azure Resource, asoctl was using the name of the resource as a unique key to identity the resource.

While these names are often unique (due to the use of GUIDs or to specific naming conventions), they aren't always unique.

In particular, some resources have hard coded names - and when those names collided, asoctl was incorrectly assuming the importers were identical.

One case where this occured was during import of a Storage Account - all of the container resources within a Storage Account (for Blobs, Queues, Tables and Files) are named default.

This PR changes to using the full ARM ID as the unique identifier for each importer.

Fixes #3195

How does this PR make you feel:
gif

@theunrepentantgeek theunrepentantgeek added this to the v2.3.0 milestone Aug 22, 2023
@theunrepentantgeek theunrepentantgeek merged commit 239eea7 into main Aug 22, 2023
8 checks passed
@theunrepentantgeek theunrepentantgeek deleted the fix/import-naming-collisions branch August 22, 2023 23:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

Successfully merging this pull request may close these issues.

Bug: asoctl import of StorageAccount doesn't pull all sub resources
2 participants