-
Notifications
You must be signed in to change notification settings - Fork 504
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
Issue on Azure DevOps Agents since 1.3.2 : failed to initialize terrascan #561
Comments
Hi @alex-3sr! Thanks for the report. Will follow up soon |
Hey @alex-3sr , we're working on a fix for this issue. gonna release with a patch soon. meanwhile, could you try specifying the policy path in the config file for now? let us know if that works for you. Also, could you let us know if there's any HOME environment variable set on the host machine? |
Could you try this terrascan binary (compiled for windows) in your pipeline and see if you face the same issue? |
Hi @dev-gaur , yes, now with this new binary file, it's working as expected ;) Thanks. I've no idea what the difference between previous one, but it's work again now. About HOME environnements variables, we had some, i exported all environnent ->
The main environnements variables, especially TEMP if I take a look on Terrascan debug error (like bellow), who is different thant the home folder with this env HOMEPATH Does it give you enough informations ? |
Description
Until 1.3.1, we didn't have any issue, and since 1.3.2 all pipelines failed with warning. The issue still present with 1.3.3.
It seem that the issue is coming with the last fix about downlaod policies on 1.3.2 #521
When we add debug log, we can see that Terrascan are unable to init because can't install policies. I think it's because the target folder is write protected, but on Hosted Azure Devops Agent we can't change it.
So, I'm a bit confused if it's a limitation of Azure DevOps and at same time like it's worked until 1.3.1 if last update can break the usage of terrascan on Azure DevOps. Is it really an issue ? BTW in anycase, works perfectly locally on my Windows Computer. Maybe it's just be an improvement that we need for still use in Azure DevOps by using an extra arguments for say where policies need to be downloaded (on a non protected write folder) for workaround, but I didn't find a way to add this extra args.
Thanks for your help/advice, Regards
Alex
What I Did
Here the error log that I can have with just a terrascan init on Azure DevOps
The text was updated successfully, but these errors were encountered: