According to the documentation, the export.from configuration property specifies the plugin and optional configuration name used to load vulnerability data. However, specifying a configuration name will cause problems as the fod or ssc profile will not be properly activated.
Technical details:
AbstractVulnerabilityLoaderFactory properly handles the optional configuration name
application.yml defines property spring.profiles.active as default, ${export.from}
Setting for example export.from to fod.instance1 will result in a profile named fod.instance1 to be activated instead of just fod
Plugin configuration files shipped with the to-json plugin however expect that either fod or ssc profile is activated
According to the documentation, the
export.fromconfiguration property specifies the plugin and optional configuration name used to load vulnerability data. However, specifying a configuration name will cause problems as thefodorsscprofile will not be properly activated.Technical details:
AbstractVulnerabilityLoaderFactoryproperly handles the optional configuration nameapplication.ymldefines propertyspring.profiles.activeasdefault, ${export.from}export.fromtofod.instance1will result in a profile namedfod.instance1to be activated instead of justfodfodorsscprofile is activated