New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for authorizing VSTS in Azure Key Vault task #8073
Comments
@Mardoxx provisioning of ACL for selected key vault needs user authentication hence it needs to go through user interaction flow only. |
Why have you closed this? :(
Currently there is no way to auth vsts with the kv within the task
…On Tue, 21 Aug 2018, 12:34 Lova Kumar Katikala, ***@***.***> wrote:
Closed #8073 <#8073>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#8073 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAOoMbD9IaHORF65zATlOjOk3ryX_quHks5uS_BTgaJpZM4WD7_a>
.
|
@Mardoxx Link that you shared and issue description sounded like you are looking for auto provisioning of ACL in key vault variable group. If you are looking for similar thing in Azure Key Vault task, we currently generate a scrip as part of the task logs that you can run to provision ACL. Inline support in task (similar variable group) is not in our backlog yet. Can you please try using the script generated by task. If that is not helping then we can add inline support for auto provisioning ACL in our backlog. |
Sorry should have been more clear!!
Digging through logs only after pipeline has failed is not great imo.
Inline Auth in task would be perfect!
…On Tue, 21 Aug 2018, 13:33 Lova Kumar Katikala, ***@***.***> wrote:
Reopened #8073 <#8073>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#8073 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAOoMU81wU62DGGZDg7YnV7Yx7F00WsSks5uS_4fgaJpZM4WD7_a>
.
|
Ok got it. @N-Usha @RoopeshNair can you please add this feature to our backlog. |
Added to the backlog and will update as we make progress in addressing it. Thanks! |
No news on this? |
|
This issue is stale because it has been open for a year with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days |
This issue is stale because it has been open for 180 days with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days |
#dontclose |
This issue is stale because it has been open for 180 days with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days |
Would be nice to have ACL for selected keyvault auto provisioned.
Have to do this workaround, adding SP manually failed every time because I don't know what I'm doing and documentation is sparse at best!!
Please see https://stackoverflow.com/questions/50968613/cannot-acces-keyvault-secrets-through-service-endpoint-in-a-vsts-release/51931131#51931131
The text was updated successfully, but these errors were encountered: