-
-
Notifications
You must be signed in to change notification settings - Fork 997
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
Added exclude_from_copy to config #3543
base: main
Are you sure you want to change the base?
Added exclude_from_copy to config #3543
Conversation
Don't know if exclude_in_copy syntactically correct, if I should rename exclude_from_copy to exclude_in_copy, or made mistakes in formatting/code let me know! |
config tests > https://gist.github.com/KabaevRoman/17cbee1e7cacb6e154d0ae18945c898f |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @KabaevRoman,
Sorry we haven't gotten around to reviewing this until now. I'll look to kick off CI later today.
In the meantime, do you mind adding documentation and testing specifically around the scenario where files are listed as both included and excluded? I would assume that the safest thing to do would be to exclude them in that circumstance.
You should be able to run most of the tests in this repository without an AWS account, etc. We've done some work fairly recently to move all tests that require external integrations to require build tags, so they shouldn't run by default.
You might want to be targeted with your tests by doing something like this anyways, though:
go test -run 'NameOfTest'
We have a goal of making it so that contributors can easily run tests locally, so any help you could provide to make that a better experience would be much appreciated.
Closing this PR for now, as it has gone stale. We can re-open it or look at a new version of the PR if you're willing to revisit it, @KabaevRoman . |
@yhakbar Hi there, missed previous message, |
No problem, @KabaevRoman ! I'll re-open the PR as you're up for picking it up. The documentation I'm looking to see here is very explicitly telling users what happens when both I see that you added this:
But as a user reading these docs, I would rather see something like this:
You don't need to run all the tests. Only run the tests that you think are relevant locally. Once you've resolved conflicts, I can re-run tests for you in CI. Note that quite a lot of work is currently underway for the code paths that you're touching here #3723, so we might need to wait a little bit to merge this so that we can keep development unblocked for Terragrunt 1.0 work. |
3ceb2d0
to
500263f
Compare
500263f
to
796e3b7
Compare
I've updated pr and changed readme as you advised, tests seems to be passing |
Thanks @KabaevRoman . I've kicked off CI. I'll coordinate with the team to see if we can merge this in earlier at the risk of increased conflicts, or if we should hold off for a bit. Either way, thanks for your patience and working with us to get this done! |
297032f
to
545a631
Compare
Some tests failed in pipeline, i was able to discover linting errors and how to run linters from makefile and fixed them, but got no luck with running integration tests properly even unit_test from config.yml. Also i have no access to pipeline logs to get more details for failing tests. And have no idea what is this shortcut you are using |
Hey @KabaevRoman ,
It's an internal tool we're using that basically just runs
That's definitely not OK! We know we can do a better job of making our tests reproducible by the community, so if you could open a bug on the unit tests that you can't run locally, we'd like to fix them. Ideally, a user would be able to run This test is failing right now:
|
Fixed test that you mentioned, it passes now. Maybe i will describe later all issues i encountered, on running tests linters etc. It seems like docs are a bit outdated https://terragrunt.gruntwork.io/docs/community/contributing/#developing-terragrunt, because they don't mention linters at all, but again i better describe all issues i encountered in separate issue or something. |
Description
Fixes #916.
Added exclude_from_copy to config, to exclude some paths via globs
TODOs
Read the Gruntwork contribution guidelines.
Release Notes (draft)
Added / Removed / Updated [X].
Migration Guide