frost
frost copied to clipboard
mozilla
Unit testing framework for test driven security of AWS, GCP, Heroku and more.
At the moment, if you run `make setup_gsuite` or `pytest gsuite/` without having everything setup correctly, you will just get a bunch of file missing exceptions. Would be nice to...
refs: #11 Currently, we set a `__pytest_meta` value in client.py `get_aws_resource` and propagate it in `extract_key` Downsides: * doesn't work for primitive values * wastes memory and CPU propagating stuff...
Currently you can test multiple AWS accounts in one execution of `pytest`. In practice, this is pretty messy and also doesn't work for those of us who are assuming a...
Now that we have a frost CLI it might be nice to roll https://github.com/mozilla/frost/blob/master/service_report_generator.py into it.
Currently frost won't work on python 3.9 (as of 3.9.0rc1). Known issues: - [`ruamel.yaml`](https://pypi.org/project/ruamel.yaml/) at our pinned version (0.15.85) won't build under 3.9. The latest version `0.16.10` does build cleanly...
Currently, we have a little section with an example config file in the README: https://github.com/mozilla/frost#custom-test-config But we need to document how each of the sections for the specific providers (AWS,...
See comments in https://github.com/mozilla-services/pytest-services/pull/78
ATM, there is little benefit to caching, due to the small number of elements returned. However, it _should_ work. Just not an immediate priority.
Since the automation was built from prior scripts, they aren't structured the "[natural](/mozilla-services/pytest-services/pull/112#discussion_r188036079)" way yet. Getting that straightened out should be done before additional tests are added for this service.
Some suites (e.g. GitHub, Heroku) can drive automated escalation sequences. That requires some state to be maintained between runs. The existing ``config.yaml`` file would be suitable for this purpose, but...