Asaf Kali

Sounds like the right way to go. Currently I can't validate the solution, as now I'm experiencing issue #12 too :)

As a temp solution, I implemented a [custom `filtered_archive` module](https://github.com/asaf-kali/resources/blob/main/tf/filtered_archive/main.tf) that gives this functionality. Usage: ```tf module "layer_archive" { source = "[email protected]:asaf-kali/resources//tf/filtered_archive" source_dir = "my_layer/" name = "layer" } resource...

Adding `output_file_mode = "0644"` (or any other value) to the `"archive_file"` solved this for me, as the default file mode is different on different OS, causing the file hash to...

Just faced the same issue recently, with: ```python3 from datetime import time import time ``` After isort the import order is reversed, and `time` is now `from datetime`. Of course...

Writing better code is not the point. The point is that given a certain state of **working** code, running `isort` can break it, without you knowing about it - so...