...
Parameter | Type | Description | Required | Default | ||||
---|---|---|---|---|---|---|---|---|
repoConfigMode | String | The configuration mode to be used on all integrated repositories. There are three options:
| Yes | createOnboardingPR | ||||
repoConfigFileName | String | It is possible to rename the .whitesource configuration file added to an integrated repository. NOTES:
| No | .whitesource | ||||
branchProtectionRule | Automatically create a “WhiteSource Security Check” branch protection rule for all branches configured by the “baseBrances” property. This will only occur for newly onboarded repositories. NOTES:
| No | “none” | |||||
settingsInheritedFrom | Add an option for a regular account repo-settingsconfig.json or global-settingsconfig.json file to inherit settings from the whitesource-config account’s global-settingsconfig.json file. For example, a global-config.json file in {someOrg}/whitesource-config could inherit settings from the whitesource-config/whitesource-config file. If this parameter is enabled, after creating a whitesource-config file inside the repos of the given organization, it will be automatically populated with the settings from the whitesource-config/whitesource-config file. NOTE: You can override specific parameters that are relevant only in the specific repository by adding these after this parameter. Examples: Using only values defined in the global configuration:
Using values defined in the global configuration and overriding the scan settings parameters:
| No | “none” |
...
Name of the zip file: scanner_logs_{SCAN_TOKEN}.zip
The name of the ws-logs repo is configurable using the env var
WS_LOG_REPO_NAME
If that repo whitesource-config/ws-logs does not exist - then the manual scan will not run, and there will be a check run explaining why:
Migrating Existing Repositories to the Global Configuration
...