Skip to content

Environment Variables can now be set for Parsers#532

Merged
J12934 merged 9 commits intomainfrom
feature/add-env-variables-to-parsedefinitions
Jul 6, 2021
Merged

Environment Variables can now be set for Parsers#532
J12934 merged 9 commits intomainfrom
feature/add-env-variables-to-parsedefinitions

Conversation

@JohannesZahn
Copy link
Contributor

@JohannesZahn JohannesZahn commented Jul 1, 2021

Description

Added empty environment variable array to the parse definitions. Also removed the ncrack secrect in the parse definition as it is not required anymore according to @J12934.

This will be used for #520, so users can decide if they want the program to crash if the Findings validation detects invalid findings. This also enables integration tests for the Findings Validation. A environment variable can simply be set to true to make the tests fail if the validation fails.

Checklist

  • Test your changes as thoroughly as possible before you commit them. Preferably, automate your test by unit/integration tests.
  • Make sure npm test runs for the whole project.
  • Make codeclimate checks happy
  • Make env an empty array

Signed-off-by: Johannes Zahn <johannes.zahn@iteratec.com>
Signed-off-by: Johannes Zahn <johannes.zahn@iteratec.com>
Signed-off-by: Johannes Zahn <johannes.zahn@iteratec.com>
@JohannesZahn JohannesZahn force-pushed the feature/add-env-variables-to-parsedefinitions branch from 111c63e to 56f2e66 Compare July 1, 2021 14:02
Signed-off-by: Johannes Zahn <johannes.zahn@iteratec.com>
@JohannesZahn JohannesZahn force-pushed the feature/add-env-variables-to-parsedefinitions branch from 56f2e66 to b639c47 Compare July 1, 2021 14:18
@JohannesZahn JohannesZahn self-assigned this Jul 1, 2021
@JohannesZahn JohannesZahn added the enhancement New feature or request label Jul 1, 2021
@JohannesZahn JohannesZahn marked this pull request as ready for review July 2, 2021 05:12
Signed-off-by: Johannes Zahn <johannes.zahn@iteratec.com>
@JohannesZahn
Copy link
Contributor Author

As @J12934 suggested we should discuss in the review if we want to handle feature flags for parsers like this before merging.

@JohannesZahn JohannesZahn marked this pull request as draft July 2, 2021 10:31
JohannesZahn and others added 2 commits July 6, 2021 09:34
Signed-off-by: Johannes Zahn <johannes.zahn@iteratec.com>
Signed-off-by: Johannes Zahn <johannes.zahn@iteratec.com>
@JohannesZahn JohannesZahn force-pushed the feature/add-env-variables-to-parsedefinitions branch from 51aa75e to de223e7 Compare July 6, 2021 07:44
@JohannesZahn JohannesZahn added this to the v3.0.0 milestone Jul 6, 2021
@JohannesZahn JohannesZahn added the scanner Implement or update a security scanner label Jul 6, 2021
@JohannesZahn JohannesZahn changed the title Added Environment variables to Parsers Environment Variables can now be set for Parsers Jul 6, 2021
@JohannesZahn JohannesZahn requested a review from J12934 July 6, 2021 07:51
JohannesZahn and others added 2 commits July 6, 2021 13:51
@JohannesZahn JohannesZahn marked this pull request as ready for review July 6, 2021 14:34
@J12934 J12934 merged commit 660e8f6 into main Jul 6, 2021
@J12934 J12934 deleted the feature/add-env-variables-to-parsedefinitions branch July 6, 2021 18:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request scanner Implement or update a security scanner

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants