Skip to content

Storage devtool migration #17396

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

Merged
merged 10 commits into from
Apr 20, 2021
Merged

Conversation

xiafu-msft
Copy link
Contributor

No description provided.

@ghost ghost added the Storage Storage Service (Queues, Blobs, Files) label Mar 17, 2021
@xiafu-msft
Copy link
Contributor Author

/azp run python - storage - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).


class StorageTestCase(AzureTestCase):
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I assume we're not inheriting from AzureMgmtTestcase because its deprecated? or what is the reason we're opting for AzureTestcase over AzureMgmtTestcase?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

StorageTestCase and AzureMgmtTestcase are both inheriting AzureTestcase. We don't need anything specific from either StorageTestCase/AzureMgmtTestcase, so there's no need to use them.
For example people who are using AzureMgmtTestcase is mainly because they need to create_mgmt_client to do some mgmt plane operation. For StorageTestCase we were using that to create storage account, while for datalake the storage account is created through ARM Template deployment so we don't need StorageTestCase either.
I know blob is using AzureMgmtTestcase probably when it was added we were using something?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah ok that explains it - so blobs we have

when we're creating the account, whereas in Datalake we're directly passing account name and key using the ARM template to deploy these resources (storage accounts)?

# fixture needs to be visible from conftest

# Ignore async tests for Python < 3.5
collect_ignore_glob = []
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Out of curiosity, how did we specify this prior to this migration?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@@ -5,6 +5,8 @@
# license information.
# --------------------------------------------------------------------------
from __future__ import division

import functools
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's a bunch of imports that we can remove now that we're migrating

@tasherif-msft tasherif-msft self-requested a review April 19, 2021 20:34
@xiafu-msft xiafu-msft force-pushed the storage-devtool-migration branch from 1924ca5 to ebd4b7e Compare April 20, 2021 17:26
@xiafu-msft xiafu-msft requested a review from benbp as a code owner April 20, 2021 17:26
@xiafu-msft xiafu-msft enabled auto-merge (squash) April 20, 2021 17:28
@xiafu-msft xiafu-msft disabled auto-merge April 20, 2021 17:28
@xiafu-msft xiafu-msft enabled auto-merge (squash) April 20, 2021 17:28
@xiafu-msft xiafu-msft merged commit 0ae834b into Azure:master Apr 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Storage Storage Service (Queues, Blobs, Files)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants