microsoft / microsoft/security-devops-azdevops
error while running on a self-hosted agent behind proxy
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 86
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I am trying to use the Microsoft Security DevOps extension for Azure Devops on a self-hosted machine that runs behind the proxy.
The Azure Devops agent configuration has veen done using the proxy configuration (--proxyurl http://:8080)
Looks to me the proxy is non used by the scanner.
I see in the log:
2023-01-11T09:23:35.820+0100 error cli/init.go:42 failed to initialize terrascan. error : could not connect to github.com
2023-01-11T09:23:35.820+0100 error cli/init.go:42 failed to initialize terrascan. error : could not connect to github.com
Kind regards
Gianluca
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at cli/init.go around line 42 and trace terrascan initialization and how the agent's proxy configuration is passed to the scanner. Reproduce the failure on a self-hosted agent behind a proxy and verify that the scanner can connect to github.com through the configured proxy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devops, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100