
EPestrikov168682 (Community Member) asked a question.
All our microservices agent based scans with ci.sh go into single project, its name is a repository name.
We have the following structure
https://bitbucket.xxxx.com/ser/service1.git
https://bitbucket.xxxx.com/ser/service2.git
We run scan like this:
curl -sSL https://download.sourceclear.com/ci.sh | DEBUG=1 sh -s -- scan --allow-dirty --uri-as-name
with or whithout last param, the difference is only in "http://" in front of the project name.
We want separate projects for separate scans.
I didn't find any parameters to add so that scan create a different project.
How do I even debug this problem?
.png)
Are you specifying the workspace? https://docs.veracode.com/r/Veracode_SCA_Agent_Commands
Nope. I though workspace is a higher level abstraction, but I'll try. This should resolve the problem.
it looks like there is another problem - I can't specify NEW workspace name so that is would be created automatically on the first scan? More over, I see they need workspace slug, not just a name, and slug is available only after you create new workspace? I'm I right?
There is then no easy automation if I have 300 microservices to create 300 workspaces upon their first scan?