Be able to define containers

[agoncal]

At startup it would be good to create containers. We could do that using a set of properties:

quarkus.azure.storage.blob.container."containerA".generation=create
quarkus.azure.storage.blob.container."containerB".generation=drop-and-create
quarkus.azure.storage.blob.container."containerC".generation=none

And then be able to set some properties:

quarkus.azure.storage.blob.container."containerA".auth-mode=key
quarkus.azure.storage.blob.container."containerA".fail-on-exist=true
quarkus.azure.storage.blob.container."containerA".public-access=blob
quarkus.azure.storage.blob.container."containerA".metadata={key1/value1,key2/value2,key3/value3}

Where:

• auth-mode: The mode in which to run the command. "login" mode will directly use your login credentials for the authentication. The legacy "key" mode will attempt to query for an account key if no authentication parameters for the account are provided. Allowed values: key, login.
• fail-on-exist: Throw an exception if the container already exists.
• metadata: Metadata in space-separated key=value pairs. This overwrites any existing metadata.
• public-access: Specifies whether data in the container may be accessed publicly. Allowed values: blob, container, off.

[melloware]

This would be an awesome feature!

[JoaoBrandao]

@agoncal I would recommend adding another property that enables the developer to insert files on those containers

quarkus.azure.storage.blob.container."containerA".folder="resources/demo"

In this case, demo would be a root folder with files inside