-
Notifications
You must be signed in to change notification settings - Fork 78
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
.ebignore doesn't strictly follow .gitignore syntax #114
Comments
There's actually some additional bizarre behavior regarding |
I am also encountering this behavior:
Results in:
But
results in:
|
I am having this exact issue, but I have permission issues on some files that should be ignored. The folder shouldn't even be entered if ignored |
Hi @ZYinMD are you still facing the issue ? I was able to do eb deploy and it seemed to work as expected . My folder structure :
.ebignore looks like :
This is part of the
zipinfo on the uploaded application file is as follows :
OS: Amazon Linux 2 Also , there seems to be an issue with Pathspec in windows cpburnz/python-pathspec#81 |
Hi @NihalM99 , I'm not currently using |
@NihalM99 I see you referenced bug cpburnz/python-pathspec#81. This is now fixed in the v0.12.0 release of pathspec. |
Description
In .gitignore (doc),
/*
means "everything, including folders, in the root path relative to the .gitignore file".This is a good starting point to construct a "whitelist" where you use
!
to include only the files you want.However, it seems
/*
in .ebignore won't ignore folders.Steps to reproduce
Create a folder structure like this:
Then construct a whitelist with .ebignore:
Then deploy with
eb deploy
, then inspect the zip file in eb console.Observed result
README.md
is successfully ignored.git
,node_modules
, andsome-other-folder
are included in the zip.Expected result
If .ebignore works the same way as .gitignore,
.git
,node_modules
, andsome-other-folder
shouldn't be zipped.(irrelevant note: Google App Engine has an equivalent
.gcloudignore
file, which behaves consistently with this "expected result")Additional environment details (Ex: Windows, Mac, Amazon Linux etc)
The text was updated successfully, but these errors were encountered: