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
Cannot create new streamalert install in 3.4.0 #1294
Comments
Hi @cdaniluk , thanks for reporting this issue.
We will look into this issue as soon as we get time. |
I think I have a fix for it - please standby |
I didn't try manually specifying a build dir since you had a fix so quickly. I switched over to that branch and got past it fine. So, I think that's a good fix. Thanks! |
fixed with #1295 |
Description
Fresh install does not seem to work on 3.4.0
Steps to Reproduce
Can reproduce on both macOS and Linux.
Start with a new clone of 3.4.0 and a new AWS account.
Run
python manage.py init
.When prompted to create initial TF resources, say yes. After completion, the following error occurs:
It seems to be attempting to write to the directory it has already created. This causes the created tf state to become orphanned.
The text was updated successfully, but these errors were encountered: