Releases: flosell/trailscraper
Releases · flosell/trailscraper
0.8.1
0.8.0
0.7.0
Added
- Support for Python 3.9
Removed
- Removed official support for Python 3.5. TrailScraper might still run but we no longer actively test for it
Changed
- Moving from DockerHub to GitHub Container registry for Docker images (since DockerHub is dropping support for autobuilds and restricting it in other ways)
- Updated supporting dependencies
0.6.4
Fixed
- Fixed Docker images that threw a
ModuleNotFoundError
Changed
- Performance tweaks
trailscraper download
uses smarter directory listing to improve performance with large date ranges and little new datatrailscraper download
now downloads files in parallel- Minor performance improvements in
trailscraper select
0.6.1
0.6.0
0.5.1
0.5.0
Breaking CLI changes: split up generate-policy
into select
and generate
(#38)
Added
- New command
select
to print all CloudTrail records matching a filter to stdout - New command
generate
to take CloudTrail records from stdin and generate a policy for it
Changed
- New command
select
defaults to not filtering at all whereasgenerate-policy
filtered for recent events by default.
Changed to make filtering more explicit and predictable instead of surprising users who wonder why their events don't show up
Removed
- Removed command
generate-policy
, replaced withselect
andgenerate
. Use pipes to produce the same behavior:$ trailscraper select | trailscraper generate
0.4.4
Fixed
- Made trailscraper timezone-aware. Until now, trailscraper implicitly treated everything as UTC, meaning relative timestamps (e.g.
now
,two hours ago
) didn't work properly when filtering logfiles to download or records to generate from. (#39)
Added
- New command
trailscraper last-event-timestamp
to get the last known event timestamp. - New flag
trailscraper download --wait
to wait until events for the specified timeframe are found.
Useful if you are waiting for CloudTrail to ship logs for a recent operation.