-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
chore(elasticsearch plugin) updating es to v8.13.1 #3120
base: master
Are you sure you want to change the base?
chore(elasticsearch plugin) updating es to v8.13.1 #3120
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi, thanks for these improvements! There are a few things to modify, and then we can get this merged 👍
@@ -166,6 +167,13 @@ export class DefaultSearchPlugin implements OnApplicationBootstrap, OnApplicatio | |||
} | |||
}); | |||
|
|||
this.eventBus.ofType(StockMovementEvent).subscribe(event => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is from the other PR that got merged right? Let's clean that up to only include the actual change relating to ES version.
container_name: elasticsearch | ||
environment: | ||
- node.name=es |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you pull latest changes from the master
branch you should see that all the docker compose configs are now in a root-level compose file. Can you move these changes to there?
port: 9200, | ||
}), | ||
], | ||
// Add an instance of the plugin to the plugins array |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These docs are generated, so you should not edit them directly. Instead, you need to edit the doc block of the plugin source and add the changes there. Next time the docs are generated, these changes will be added to the md files.
Description
Please include a summary of the changes and the related issue.
Breaking changes
Does this PR include any breaking changes we should be aware of?
Screenshots
You can add screenshots here if applicable.
Checklist
📌 Always:
👍 Most of the time: