connection-string | A connection | Runtime Evironment library

I believe you are getting false back is because your storage account is a regular storage account and does not have hierarchical namespace enabled i.e. your storage account is not a Data Lake Gen2 account.

In regular storage accounts, the folders are virtual. They are real folders in Data Lake Gen2 accounts. All the directory related commands will only work with Data Lake Gen2 accounts. Documentation unfortunately does not mention it.

Plese add id to you first action:

Try

Yes, using a mix of azcli and azure powershell, as they are their seperate entities in their own right, you would need to login to each of them individually. And yes, you are right its better to ditch of them and choose one or the other ! Just much cleaner that way

All I had to do was npm install mysql2, then use the Connection String to run queries:

You need Instant Client 19.14 (or later), or 21.5 (or later). The 1-way TLS support was added to this version.

If you have a sqlnet.ora file from a previous use of mTLS, then you should remove it: it's likely you have one and the wallet location in that file is being looked up and giving you the error.

Then follow the doc or the new blog Easy wallet-less connections to Oracle Autonomous Databases in Python

(Yes technically the feature is useable with the recut 19.13 Instant Client on Linux as noted in the doc, but that is now superseded and the feature is available on more architectures from 19.14 and 21.5 onward)

The Azure Functions runtime uses the AzureWebJobsStorage connection string to create internal queues

When Application Insights is not enabled, the runtime uses the AzureWebJobsDashboard connection string to log to Azure Table storage and power the Monitor tab in the portal

AzureWebJobsStorage and AzureWebJobsDashboard are created in the Application Settings by default while creating the Azure Function App

So, these are created as App Service Config as Source

After the creation of Function App, you can edit the values of AzureWebJobsStorage and AzureWebJobsDashboard as key vault secrets

Then the values will be changed with Key Vault Reference as Source

The headless service serves as an entrypoint for you to connect to MongoDB, without the need to specify a pod address. Kubernetes will balance the load and serve it to a specific pod.

If you wish to connect to MongoDB, using externalAccess.enabled, you should take a look at the Helm deployment notes that are shown when you deploy the chart. You can read them post-deployment by executing the helm get notes MY-RELEASE command.

For instance, in my case, it shows this, though depending on the deployment options it would show something else:

The whole point of using Azure App Configuration is to store your config in one place and easily manage it without redeploying / restarting the app. Therefore I don't think this is should be even possible.

I would recommend to use labels to load specific version of your prop based on labels data. Few cases:

1. If you need this property only locally, don't specify it in App Configuration.
2. If you need multiple versions of it, then just create same property with multiple labels and use your spring.profile (or other conf-property) to distinguish the version.
3. If you need to load multiple versions of it, load multiple labels:
   As described here: https://docs.microsoft.com/en-us/java/api/overview/azure/spring-cloud-starter-appconfiguration-config-readme?view=azure-java-stable#load-from-multiple-labels

You can use this sample to see how it works: https://github.com/Azure/azure-sdk-for-java/tree/azure-spring-boot_3.6.0/sdk/appconfiguration/spring-cloud-starter-azure-appconfiguration-config