TIER3: binary analysis

[mguetta1]

Adding binary analysis test case for tackle-testapp, private repo
GITHUB_USER and GITHUB_TOKEN can be provided as configuration variables (in config/config.json) or as environment vars

[aufi]

@mguetta1 Please take as a template test case TestApp with deps https://github.com/konveyor/go-konveyor-tests/blob/main/analysis/tc_tackle_testapp_public_deps.go (this one is part of TIER0)

[aufi]

Thanks for update Maayan! PR looks good, Just to understand better what the Binary mode means. I can see Binary field on analysis and application (that should be checkout from SVN) in this PR. Just to be sure, isn't it needed to upload the application binary file to application's bucket to use it for analysis?

[sshveta]

Thanks for update Maayan! PR looks good, Just to understand better what the Binary mode means. I can see Binary field on analysis and application (that should be checkout from SVN) in this PR. Just to be sure, isn't it needed to upload the application binary file to application's bucket to use it for analysis?

There are two modes of analysis @aufi .
In binary analysis we provide source code which contains an embedded binary in the repo.
Second is "Upload Binary" where we upload a ear/jar/war/zip file for analysis .

This PR covers the first option . Binary analysis on source repo.