Handling dynamic key names about get-keyvault-secrets HOT 6 OPEN

I made a quick change locally that has been tested and solves this issue

Change overview:

Gist changes (for copy+paste): https://gist.github.com/joseph-flinn/c940392463964b6139df4325b471c8ad

Unfortunately, I don't have the bandwidth to follow through and really dig into how this action is setup with support for the AzureStack to put in a PR. During my testing, master was breaking and I couldn't test my changes directly against master and I couldn't find documentation on how to run this Action local to a runner (if there are steps needed to compile or something). I personally made changes to a branch taken off of the current stable v1.1.

from get-keyvault-secrets.

Another workaround is that we can use square brackets to access the dynamic secrets
Assuming x holds the secret key name ex. store-id then we can use ${{ env.x }} in the get-keyvault-secrets action and we can access the value by ${{ steps.azure-secrets.outputs[env.x] }}

https://stackoverflow.com/questions/69299781/using-a-variable-inside-context-expression-in-github-actions

Hope this helps someone!

from get-keyvault-secrets.

This would also be helpful in (or enable) cases getting different secrets in a matrix job

from get-keyvault-secrets.

I was able to get dynamic name secrets by this:

One thing that concerns me is, how do I access it in the output
${{ steps.GitHubPAT.outputs.$secretName }}

How do I have the $secretName as dynamic?

from get-keyvault-secrets.

This issue is idle because it has been open for 14 days with no activity.

from get-keyvault-secrets.

This issue is idle because it has been open for 14 days with no activity.

from get-keyvault-secrets.