azure-sdk-for-python | active development of the Azure SDK | Azure library

The method you are looking for is list_topics in ServiceBusAdministrationClient class.

Here's the sample code taken from here:

This issue is caused by Azure CLI version 2.30.0 which seemed to be rolled out MS hosted agents recently.

Hence I adapted all my Python scripts running on (MS and self) hosted agents to this model:

In my opinion, partition is something which applies over keys sharing some common group, for example partition over food groups.

This is not entirely true. If you look at the documentation, it says that you should choose a partition key that has a high cardinality. In other words, the property should have a wide range of possible values. It should be a value that will not change. You also need to note that if you want to update or delete a document, you will need to pass the partition key.

What happens in the background, is Cosmos can have multiple servers from 1 to infinity. It uses your partition key to logically partition your data. But it is still on one server. If your throughput goes beyond 10K RU or if your storage goes beyond 50GB, Cosmos will automatically split into 2 physical servers. This means your data is split into the 2 servers. The splitting can go on until the max throughput per server is < 10K RU and storage per server is < 50GB. This is how Cosmos can manage infinite scale. You may ask how would you predict which partition a document may go into. The answer is you can't. Cosmos produces a hash using your partition key with a value between 1 and the number of servers.

So the doc id is a good partition key because it is unique and can have a large range of values.

Just be aware that once Cosmos partitions to multiple servers, there is no automatic way currently to bring the number of servers down even if you reduce the storage or reduce the throughout.

The issue with the code snippet was the encoding of the key hash. Since the hexdigest of the hash is a python string object that represents a hex string, we must take special care to decode it and treat its type as hex. Additionally, we must re-encode the base64 encoded strings into python string objects before passing it to the CustomerProvidedEncryptionKey.

See https://gist.github.com/CodyRichter/a18c293d80c9dd71a3905bf9c44e377f for the complete working code

If you want to access an Azure Key Vault from an Azure Web App for Containers in Python, the recommended way is to use Managed Identity instead of creating and managing your own Service Principal. Managed Identity is supported in Web App for Containers.

In the Python container, you can access the Azure Key Vault secret using the managed identity with the following lines of code

For pagination by specific page number, you can make use of OFFSET LIMIT clause available in Cosmos DB SQL API.

All you need to do is specify the offset and limit clause in your query itself. Something like:

For SDK version 3.x (that you're using), please try by definining maxItemCount in the query options. Your code would be something like:

Why create a BlobServiceClient then a BlobClient instead of just directly creating a BlobClient?

BlobClient only allows you to work with blobs so if you want to work with just blobs, you can directly create a BlobClient and work with it. No need for you to create a BlobServiceClient first and then create BlobClient from it.

BlobServiceClient comes into picture If you want to perform operations at the blob service level like setting CORS or list blob containers in a storage account. At that time you will need BlobServiceClient.

In Cosmos DB terminology, Container is equivalent to a Table as Container holds the data like Table. If you're coming from a relational database world, here's the mapping (kind of):