Skip to content
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

Support for specifying scsast controller URL for sc-sast-scan #47

Open
crance opened this issue Sep 9, 2024 · 1 comment
Open

Support for specifying scsast controller URL for sc-sast-scan #47

crance opened this issue Sep 9, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@crance
Copy link

crance commented Sep 9, 2024

Enhancement Request

The native scancentral cli supports either specifying SSC_URL or SCSAST Controller URL (henceforth SCSAST_URL).

Currently, if SSC_URL is specified in the native scancentral cli, it will retrieve the SCSAST_URL setting configured in SSC.
In some environments, SCSAST_URL specified in SSC could be using internal DNS/IP (or even k8s cluster name).
In such scenario, the resolved SCSAST_URL will be an internal DNS/IP, and hence not accessible via GitHub.

The current workaround is use fortify/github-action/setup to install sc-client and run the native scancentral command via shell.
A reusable GitHub action approach would be nice.

@rsenden
Copy link
Contributor

rsenden commented Sep 25, 2024

Sorry for the delay; as this will need to be implemented in fcli, I've created a new issue on the fcli repo with similar contents.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants