aws
Configure duvet to avoid downloading RFC spec files in CI
Problem:
Currently the duvet report command run from the project source dir but the RFC spec files are located in the compliance folder. Since duvet only looks at the current dir when searching for RFC spec files, it needs to download them again. We should fix duvet or how we call it to avoid re-downloading the RFC specs again.
The point of downloading the spec files compliance/specs is to avoid network calls to download them again each time. This is important for CI to be less flaky.
Solution:
- Add a param to duvet report to specify location of the spec files
- Move specs to the project root folder (not recommended)
Requirements / Acceptance Criteria:
Calling compliance/generate_report.sh should work without internet connection (test by turning off all internet connection).
https://github.com/aws/s2n-tls/issues/4219 represents a super rough draft which I used to test and debug the behavior.
Duvet now supports specifying a different spec file location. Next steps: we need a duvet release before using the new commands.
