You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# Following article on https://dev.azure.com/devdiv/DevDiv/_wiki/wikis/DevDiv.wiki/25351/APIScan-step-by-step-guide-to-setting-up-a-Pipeline
121
+
# No longer need the old format, and following guideline to use (ApiScanClientId)
122
+
- task: APIScan@2
123
+
displayName: Run APIScan
128
124
inputs:
129
-
script: |
130
-
@echo off
131
-
REM Per the documentation here - https://docs.microsoft.com/en-us/azure/devops/pipelines/process/variables?view=azure-devops&tabs=classic%2Cbatch#set-variables-in-scripts
132
-
REM
133
-
REM We can set/update pipeline variables using the syntax used below. That way we can use a script task to
134
-
REM pull secrets into the environment for APIScan to use, since the ApiScan task does not have an 'Environment'
135
-
REM section for mapping secrets in classic pipelines.
136
-
REM
137
-
REM Make sure the pipeline secret variable 'AzureServicesAuthConnectionString' is set. It's format is like
138
-
REM "runAs=App;AppId={AppId};TenantId={TenantId};AppKey={ClientSecret}"
139
-
REM The values for that connStr can be found in the Tellurium Key Vault.
0 commit comments