Adding CLI and PS error logs & optional audience parameter - #159
Merged
Conversation
Balaga Gayatri (BALAGA-GAYATRI)
had a problem deploying
to
Automation test
October 25, 2021 13:26
Failure
Balaga Gayatri (BALAGA-GAYATRI)
temporarily deployed
to
Automation test
October 25, 2021 13:28
Inactive
Balaga Gayatri (BALAGA-GAYATRI)
had a problem deploying
to
Automation test
November 1, 2021 10:49
Failure
Balaga Gayatri (BALAGA-GAYATRI)
had a problem deploying
to
Automation test
November 1, 2021 11:46
Failure
Balaga Gayatri (BALAGA-GAYATRI)
temporarily deployed
to
Automation test
November 1, 2021 11:51
Inactive
| pwd | ||
| ``` | ||
| This action supports login az powershell as well for both windows and linux runners by setting an input parameter `enable-AzPSSession: true`. Below is the sample workflow for the same using the windows runner. Please note that powershell login is not supported in Macos runners. | ||
| Users can also specify `audience` field for access-token in the input parameters of the action. If not specified, it is defaulted to `api://AzureADTokenExchange`. This action supports login az powershell as well for both windows and linux runners by setting an input parameter `enable-AzPSSession: true`. Below is the sample workflow for the same using the windows runner. Please note that powershell login is not supported in Macos runners. |
Contributor
There was a problem hiding this comment.
nit: we should have "This action supports login... " in a new line
Kanchan Verma (kaverma)
approved these changes
Nov 8, 2021
Contributor
|
We need to update the documentation/readme to include the audience field |
Kanchan Verma (kaverma)
suggested changes
Nov 9, 2021
Kanchan Verma (kaverma)
left a comment
Contributor
There was a problem hiding this comment.
Balaga Gayatri (@BALAGA-GAYATRI), Usha N (@N-Usha) , should we have a security review to ensure whether we are good with all these claims in logs that anyone can see?
Balaga Gayatri (BALAGA-GAYATRI)
had a problem deploying
to
Automation test
November 12, 2021 12:15
Failure
Balaga Gayatri (BALAGA-GAYATRI)
had a problem deploying
to
Automation test
November 12, 2021 12:16
Failure
Balaga Gayatri (BALAGA-GAYATRI)
temporarily deployed
to
Automation test
November 15, 2021 07:05
Inactive
Balaga Gayatri (BALAGA-GAYATRI)
added a commit
that referenced
this pull request
Nov 15, 2021
* cherry pick changes * added audience field option in input params * added js * removed extra spaces * Adding logs to surface AZ-CLI and powershell errors (#171) * removing token logs
Contributor
Author
|
Printing token logs changes are removed from this PR and will be done post security approval. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Added federated token logs - sample output:

Also, added audience parameter (which will be optional) and defaults to ‘api://AzureADTokenExchange’