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 dry-run mode for fetchers #41

Open
alfinkel opened this issue Aug 26, 2020 · 0 comments
Open

Add dry-run mode for fetchers #41

alfinkel opened this issue Aug 26, 2020 · 0 comments
Labels
enhancement New feature or request fetch Fetch related issue runners Runners related issue

Comments

@alfinkel
Copy link
Contributor

Overview

We should add a dry-run mode for fetchers that mocks out the Python request and instead returns a response containing content provided as a test file that contains production-like data typically returned by a call to an API. This will allow us to provide mocked responses and allow for Travis to validate that our fetchers and checks work as expected as part of any commit pushed or PR submitted to a compliance repo.

Requirements

  • Add a "dry-run" mode
    • Thinking --evidence dry-run, this way it can be used on a fetch and a check execution and should behave like a local execution except that data will come from a sample file.
  • dry-run mode should mock requests and replace the responses with content provided by files containing production-like data.
  • Execution should be otherwise seamless

Approach

TBD

Security and Privacy

TBD

Test Plan

TBD

@alfinkel alfinkel added enhancement New feature or request fetch Fetch related issue runners Runners related issue labels Aug 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request fetch Fetch related issue runners Runners related issue
Projects
None yet
Development

No branches or pull requests

1 participant