forked from RedHatProductSecurity/rapidast
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[containerize] Create optional default config (RedHatProductSecurity#128
) * [containerize] Create optional default config If there is a file called 'rapidast-defaults.yaml' located in the same directory as `rapidast.py`, then this file is loaded as a YAML file. It content will be merged to the current rapidast config BUT without overwriting any existing entries. In practice, this allows anyone to create default values. Containerfile uses that to set `general.container.type` to 'none' This way, if a config file does not set a container type for a given scanner, `none` will be chosen. * [templates] container type set to default Commenting out the container.type, so that templates rely on default. Except in `generic` scanner, where `podman` is the only supported type, so it makes sense to enforce it at the moment. Relying on default will allow RapiDAST to use podman on a host, and none in the RapiDAST image. Additional changes: I tried to normalize documentation within the YAML templates. e.g.: ``` ``` Is that a entry called `Optional` commented out or is it documentation? Now: - if there is no space between the `#` and the first letter, it's an entry commented out - if there is a space between `#` and the first letter, and that letter is upper case, it's probably documentation * fix: MacOS template selects type none
- Loading branch information
Showing
9 changed files
with
44 additions
and
20 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,3 @@ | ||
general: | ||
container: | ||
type: "none" |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters