-
-
Notifications
You must be signed in to change notification settings - Fork 745
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
EL7/U16 -> Mongo 4.0 Master Issue #4972
Comments
RE st2docs, the following documentation page will need an update too: |
@punkrokk I think I may have covered the st2docs change under this one: https://github.com/StackStorm/st2docs/pull/994/files (was amending a few other files when removing EL6 for functionality I knew we'd changed!) |
@punkrokk In the st2 repo. In the circleci config file. When it runs the integration tests it points to the docker mongo:3.4. Does that need to be altered to point to mongo 4.0 as part of this issue? |
For future reference, ideally not to mix several logically independent changes in one PR like EL6 deprecation and MongoDB 4.0 and EL8 link update and something else. |
@armab Good call, I think I lost focus on what the actual issue was !!! |
Point noted. Got carried away when noticing errors in docs. Will do separate PRs next time to make it easier to review/track. |
@punkrokk I noticed that in st2 repo the travis and circleci still refer to mongo 3.4 for their runs on python 2.7, not mongo 4.0. Do we need another checkbox to resolve those? |
… On Aug 7, 2020, at 6:26 AM, amanda11 ***@***.***> wrote:
@punkrokk I noticed that in st2 repo the travis and circleci still refer to mongo 3.4 for their runs on python 2.7, not mongo 4.0. Do we need another checkbox to resolve those?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Sure, good spotting! |
I’m not aware of any other places with mongo 3.4 |
Since Mongo 3.4 has been deprecated, we need to following Issues resolved in order to update/support Mongo
3.64.0 in ST2 v3.3.04.0
instead of3.4
The text was updated successfully, but these errors were encountered: