-
Notifications
You must be signed in to change notification settings - Fork 159
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
directory are listed when we use s3 as a backend for states #409
Comments
lotoussa
pushed a commit
that referenced
this issue
Apr 7, 2021
lotoussa
pushed a commit
that referenced
this issue
Apr 7, 2021
lotoussa
pushed a commit
that referenced
this issue
Apr 7, 2021
lotoussa
pushed a commit
that referenced
this issue
Apr 7, 2021
eliecharra
added a commit
that referenced
this issue
Apr 7, 2021
Fix #409 do not list directory when using s3 as state backend
LGTM
vs
|
Awesome, looking forward to taking another crack at this when it's available in a release! |
@mwarkentin 0.7.1 is just hours from being released :) |
Merged
sundowndev
pushed a commit
that referenced
this issue
Apr 13, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Sometimes directory are listed when we use s3 as a backend for states.
Reading them produce a "no state" error and stop the scan.
How to reproduce
create an empty inside a bucket using aws web console. You may add statefile in it.
Tun scan with this bucket as a backend.
The text was updated successfully, but these errors were encountered: