Allow parameterizing Azure key vault secret names
I would like to be able set secret name as parameter. Now it does allow me to "add dynamic content" but when I do try to add actual parameter to keyvault secret name it does not provide me ability to do so. There is a bug or this feature is limited? At least this happens when trying to parameterize ADF SSIS IR package parameters
Zicheng Wang commented
I managed to parameterize the secret name by adding the access token-> secret name. In my case I was trying to overwrite the secret name that used to store Databricks AccessToken for multiple environments in CI/CD pipeline.
Torben Jensen commented
It should also be possible to parameterize the name of the key vault itself
I need this functionality, I have one key vault to store my secrets this is used across the dev/test/uat environments and therefore they have appended environment name. CI/CD has been set up, and works great as I am able to pass the override parameters for the connections within the release pipelines in DevOps. However with my secretnames being for example devdatalake / testdatalake / devsource1 / testsource1 within keyvault I am unable to override the value on release and therefore have a manual interation to correctly prefix the environment after my auto release; obviously I don't want to do anything manually in the release so I can schedule it to happen overnight/in down time etc and only interact if there is a failure etc.