-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
[BUG]: Legacy flag does not get passed through in opensslPkcsArgs argument of the InstallAppleCertificateV2 task #19436
Comments
Can someone help please ? Do I need to update the Azure Devops version ? My current version is Version Azure DevOps Server 2022 (AzureDevOpsServer_20221122.1) Is it tied to the version, or the agent version ? What is it tied to ? Which Azure Devops version has this argument available |
Hi @darijan-darijan, |
Hello @darijan-darijan, I was wondering if you’ve had a chance to update the task and make sure the issue has been resolved for you? Thank you. |
if anyone experiences this issue in the future , make sure that your version of InstallAppleTaskCertificate@2 is up to date. You can find the current version in the pipeline log. And as for the development team, please next time you change a feature, dont simply say "we have added the flag" You have the task @ version (eg. @ 2, @ 3, @ 4) There are so many versions and version types to keep track of, its super finnicky, so please be more verbose and descriptive moving forward. Closing this task, thank you! |
New issue checklist
Task name
InstallAppleCertificateV2
Task version
2
Issue Description
What did I do
passed the '-legacy' flag through the opensslPkcsArgs
What did I see
/usr/local/bin/openssl pkcs12 -in ... -nokeys -passin pass:*** | /usr/local/bin/openssl x509 -noout -fingerprint -subject -dates -nameopt utf8,sep_semi_plus_space
Error outputting keys and certificates
The error that was already reported here
#18560
What did I expect to see
I expected to see the '-legacy' flag appended to the command, but looks like it does not get passed. Also I expected the command to be executed successfully on MacOS 13 with the '-legacy' flag
Environment type (Please select at least one enviroment where you face this issue)
Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
Agent version: 2.213.2
Operation system
MacOS 13
Relevant log output
Full task logs with system.debug enabled
Repro steps
The text was updated successfully, but these errors were encountered: