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

Add usage_type for configs and tasks #613

Merged
merged 5 commits into from
Jun 24, 2019

Conversation

timopollmeier
Copy link
Member

Configs are now marked as either a "scan" config or a "policy" while tasks are marked either "scan" tasks or "audits".

While the tasks and configs currently still behave the same, normal vulnerability assessments can now be handled separately from compliance audits.

Configs are now marked as either a "scan" config or a "policy" while
tasks are marked either "scan" tasks or "audits".
@timopollmeier timopollmeier requested a review from a team June 21, 2019 15:05
Copy link
Contributor

@mattmundell mattmundell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks Timo, looks good.

src/manage_sql.c Show resolved Hide resolved
@mattmundell mattmundell self-requested a review June 21, 2019 15:19
Copy link
Contributor

@mattmundell mattmundell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just the one doc needs to be fixed for the build checks.

The variable isn't just escaping the quotes, so quoted_usage_type
wasn't the most appropriate name. It is also changed to const char*
because allocating and freeing memory is unnecessary for fixed values.
@timopollmeier
Copy link
Member Author

The documentation has been fixed now (395696d).

@mattmundell mattmundell merged commit dfb245c into greenbone:master Jun 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants