-
Notifications
You must be signed in to change notification settings - Fork 216
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
Update to python3 and elastalert v0.2.4 #174
Conversation
Are this is not need any more? it solved the bug with jira 1.0.15 plugin and there are some requirements as i remember |
@hottwister Also in this issue Yelp/elastalert#1654 they wrote that it works ;) |
@balthazar is rite. I used the following Dockerfile is my environment. I didn't go uptown 0.2.4 since I only needed some features in 0.2.2.
|
Is this after running |
docker build error
|
9c7936d
to
ea34df2
Compare
The problem is with new cryptography lib (pyca/cryptography#5771) Try now. |
I have confirmed that the problem has been resolved. |
Cryptography seems to be okay up to 3.3. The issue says alpine: 3.13 and installs rust and cargo. The docker image of node seems to be up to alpine: 3.12 so far, so I understood that it is correct to avoid the problem by installing the version before 3.0 or the version before 3.4 like this time. |
Babel Upgrade (6 → 7)
index.js require('babel-register'); → require('@babel/register');
package.json Library Update
src/common/config/server_config.js
before
after
src/common/file_system.js
before
after
src/controllers/rules/index.js
before
after
src/controllers/templates/index.js
before
after
src/handlers/test/post.js before
after
Makefile before
after
|
I found that the following method works.
Dockerfile
|
Ok I remembered - python version was other problem: #122 (comment) alpine:3.11 was also the latest version then. I checked now:
It is build successfuly but don't try does it works correctly. |
I just confirmed that the docker image was created successfully. alpine: 3.11・・・rust 1.39.0-r0 alpine: By setting 3.13, I was able to clear the condition of rust> = 1.45, so I found that no error occurred.
|
Update elastalert to v0.2.4
I've tried to make as few changes as possible.