Skip to content

Conversation

@weshaggard
Copy link
Member

@weshaggard weshaggard commented May 7, 2024

Switch ApiScan to use Azure CLI auth. While I'm not particularly happy with this approach, the APIScan tool/task doesn't support WIF directly currently so we are moving to use the Azure CLI login instead.

@weshaggard
Copy link
Member Author

/azp run net - aggregate-reports

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@weshaggard
Copy link
Member Author

/azp run net - aggregate-reports

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@weshaggard
Copy link
Member Author

/azp run net - aggregate-reports

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@weshaggard
Copy link
Member Author

/azp run net - aggregate-reports

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@weshaggard
Copy link
Member Author

/azp run net - aggregate-reports

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@weshaggard
Copy link
Member Author

/azp run net - aggregate-reports

@weshaggard weshaggard marked this pull request as ready for review May 14, 2024 00:22
@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@weshaggard weshaggard changed the title Test ApiScan change Switch ApiScan to use Azure CLI auth May 14, 2024
@weshaggard weshaggard requested a review from benbp May 14, 2024 00:23
Co-authored-by: Ben Broderick Phillips <[email protected]>
Co-authored-by: Ben Broderick Phillips <[email protected]>
@weshaggard
Copy link
Member Author

/check-enforcer override

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants