Documentation ¶
Index ¶
Constants ¶
This section is empty.
Variables ¶
This section is empty.
Functions ¶
This section is empty.
Types ¶
type Config ¶
type Config struct { DefaultValues DefaultValues `yaml:"defaultValues"` Mappings []Mappings `yaml:"mappings"` DescriptionExtras []string `yaml:"addToDescription"` SyncMappings []JiraToDraconVulnMappings `yaml:"syncMappings"` }
Config contains all the data parsed from the conf.yaml file
type CustomField ¶
type CustomField struct { ID string `yaml:"id"` FieldType string `yaml:"fieldType"` Values []string `yaml:"values"` }
CustomField represents a Jira Custom Field
type DefaultValues ¶
type DefaultValues struct { Project string `yaml:"project"` IssueType string `yaml:"issueType"` Components []string `yaml:"components"` AffectsVersions []string `yaml:"affectsVersions"` Labels []string `yaml:"labels,omitempty"` CustomFields []CustomField `yaml:"customFields,omitempty"` }
DefaultValues represents the Values that exist by default in all jira tickets we had access to
type JiraToDraconVulnMappings ¶
type JiraToDraconVulnMappings struct { JiraStatus string `yaml:"jiraStatus"` JiraResolution string `yaml:"jiraResolution"` DraconStatus string `yaml:"draconStatus"` }
JiraToDraconVulnMappings used by the sync utiity, this Mapping matches DraconStatus-es to combinations of JiraStatus and JiraResolution, look in the sample config file for examples supported DraconStatus values: * FalsePositive <-- will set the issue's FalsePositive flag to True * Duplicate <-- if the issue already exists in the database, will do nothing, otherwise will insert a new one * Resolved <-- will _REMOVE_ the finding from the database JiraStatus will be matched as a string JiraResolution will be matched as a string