Managed Identity Service Connection Not Supported in All Agent Runtime Environments #328
Labels
bug
Something isn't working
Comments
|
Could someone on the team clarify whether this issue and its pull request will be considered? The current radio silence doesn't give me any expectation as to whether monitoring this report is worth my effort. I've been keeping the pull request in sync with the latest from main for two and a half weeks now. If the report and fix will be considered or there are any requests for modified code or test cases (aside from merging what I hope is a pending build fix for failures on main), I'm happy to be patient about it or submit additional commits, but please at least let me know what to expect. While I debated internally if I should do this, I'm tagging you all in the hopes anyone at all actively contributing here will have some feedback: |
|
@lsuarez5280 Unfortunately it doesn't seem like many external PRs get approved or even looked at in this repo. Been doing the same for my own PR since beginning of April |
|
Thanks @ataverascrespo. Quite a way to run an open source protect... |
|
Hi @lsuarez5280 |
|
@v-schhabra The issue persists using task Full reproduction: |
|
Will check and get back to you on this soon. Thanks for sharing the logs. |
|
@v-schhabra Since you're the only one who's responded to this issue, I decided to address my query to you. Can you comment with any expectation I should have that the PR I've provided might be considered for a resolution of this issue, or should I abandon keeping it up to date? My latest merge was unsuccessful but I don't want to troubleshoot this if my effort will ultimately be wasted. |
|
Hi @lsuarez5280 |
|
Hi @lsuarez5280 - Can you please share the detailed repro steps or configuration to check the issue. |
|
@nagarajku The steps are as implied in the original issue report:
Irrespective of the specific reproduction steps used in my case, the code identified is requesting a dated API version of the MSI token API that is not supported by all potential Azure host runtimes and should be remediated. The DevOps team could reduce maintenance for this task by adopting @azure/identity to perform this task using DefaultAzureCredential (see samples). |
|
Hi @lsuarez5280 - Hope you are doing well!! |
|
@nagarajku I will need some time to reproduce this. Addressing this issue has taken long enough that the pilot environment I was working in was decommissioned and I'll have to spin this up elsewhere. |
|
Hi @lsuarez5280 - Reminder: do you have a setup ready to repro this issue as informed in the last conversation. Please let me know if it is ready, so that we can plan for a 1-1 connect to understand the issue. |
1 similar comment
|
Hi @lsuarez5280 - Reminder: do you have a setup ready to repro this issue as informed in the last conversation. Please let me know if it is ready, so that we can plan for a 1-1 connect to understand the issue. |
|
Hi @lsuarez5280 - Reminder: do you have a setup ready to repro this issue as informed in the last conversation. Please let me know if it is ready, so that we can plan for a 1-1 connect to understand the issue. |
|
Hi @lsuarez5280 - as we did not hear back, we are closing the issue. Feel free to reach us for any assistance. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The following code in
azure-arm-common.ts:357-361is dated and too prescriptive, resulting in a failure to leverage Managed Identity in Azure Container Apps hosting my Azure Pipelines agents:The current code results in the following debug output after two minutes from a pipeline using the AzureWebApp@1 task.
As an example, the following is the constructed URL for obtaining MSI tokens based on the runtime environment of one replica of my agents.
See an image capture from an example bash console session below:
I would suggest a backwards-compatible rewrite of the code to the following to leverage a more recent MSI API:
If this repository is accepting contributions, please tag me if desired and I'll submit a pull request with this information.
The text was updated successfully, but these errors were encountered: