-
Notifications
You must be signed in to change notification settings - Fork 0
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
textproc/opensearch: Update to 2.11.1 #3
Conversation
Hello, I was testing this version with wazuh-dashboard-plugins and it breaks completely (wazuh/wazuh-dashboard#113). I guess it was because 2.11.0 removed angularjs. I think the best could be create a opensearch210-dashboard port for wazuh until it can works without problems with opensearch-dashboards >= 2.11.0. |
You mean this guy was right: opensearch-project/OpenSearch-Dashboards#4993 (comment) ? 😒 And people still ask if it is acceptable to ship features in patch releases 🙄 Good news, this is not what was accepted in the end. This really gets boring… +1 for a copy with the MAJOR + MINOR version in the port name, so |
Splitting the Port at a minor version does not feel right, but theses changes break certain plugins (maybe more than just Wazuh) we should definitely go for a *210 port. It's already too late for fixing/intervening upstream... |
be0f4d4
to
e3f6bef
Compare
I inserted a commit to copy the opensearch-dashboards port. I think it make sense to do the same with opensearch itself, right? |
I see multiple new warnings after 2.10-2.11 upgrade:
IP Adress check has changed:
when using None if these looks like a major issue, but I'd like to do some more testing before pushing this commit. |
e3f6bef
to
8becccc
Compare
OpenSeach-Dashboards 2.11.0 introduce some supposed internal changes that break wazuh. Before updating OpenSeach, make the old version available with a new port. With hat: opensearch
OpenSeach-Dashboards 2.11.0 introduce some supposed internal changes that break wazuh. Before updating OpenSeach, make the old version available with a new port. With hat: opensearch
With hat: opensearch
With hat: puppet
8becccc
to
d41cca9
Compare
Sure! I also experienced some breakage related to the listen address on Linux deployments, but did not dig in (in my case OS listening on localhost was only listening on I added commits to copy the existing ports with a 210 suffix. I have not tested it since I don't use wazuh. Please report feedback if you give it a try! |
Use opensearch-dashboards like MASTER port
Use textproc/opensearch-dashboards like MASTER port
Use textproc/opensearch-dashboards like MASTERDIR
Use opensearch-dashboards like MASTERDIR
Delete obsolete file
Use textproc/opensearch like MASTERDIR
Delete obsolete file
Use textproc/opensearch like MASTEDIR
Delete obsolete file
Delete obsolete file
Delete obsolete file
Delete obsolete file
Delete obsolete file
Hello, I did some modifications to opensearch*-210 ports. Please review those changes |
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.
That looks good. I think the pkg-deinstall.in was not intended for 2.10 only?
Edit: I can't approve this PR because I opened it 🙃
#!/bin/sh | ||
|
||
case "$2" in | ||
POST-DEINSTALL) | ||
if [ -d %%WWWDIR%%/optimize ]; then | ||
/usr/bin/find %%WWWDIR%%/optimize/ -delete | ||
fi | ||
|
||
cat <<EOMSG | ||
|
||
If %%PORTNAME%%%%PKGNAMESUFFIX%% is being deleted permanently, and you do not wish to keep any | ||
data that was in the cluster, then you may wish to delete the | ||
%%WWWDIR%% directory. This can be done by with the command: | ||
|
||
# rm -rf %%WWWDIR%% | ||
|
||
Please ignore this if %%PORTNAME%%%%PKGNAMESUFFIX%% is being upgraded | ||
EOMSG | ||
;; | ||
esac |
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.
Should we not also have this for textproc/opensearch?
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.
I think this file is not being included into opensearch-dashboards port/package. I don't see any SUB_FILES entry into Makefile file
@@ -14,7 +14,7 @@ BUILD_DEPENDS= jna>0:devel/jna | |||
RUN_DEPENDS= bash>0:shells/bash \ | |||
jna>0:devel/jna | |||
|
|||
CONFLICTS= opensearch13 | |||
CONFLICTS?= opensearch13 opensearch210 |
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.
👍 Yes, I forgot to update the CONFLICTS!
|
||
MASTERDIR= ${.CURDIR}/../../textproc/opensearch | ||
|
||
.include "${MASTERDIR}/Makefile" |
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.
Good idea I think
what about remove CHROMIUM from opensearch-dashboards OPTIONS? Really it works from any browser based on chrome. I think the best is put a note into a pkg-message file or just remove the OPTION |
- Add pkg-deinstall to SUB_FILES - Define SUB_LIST - Remove CHOMIUM option
Remove obsolete file
The option is not enabled by default, so no objection to tweak this. I personally don't use this feature 🤷 |
FYI, 2.11.1 is at the corner. I guess we can wait for it before updating? |
I agree. I read it breaks logstash too if I'm not mistaken. Maybe it changes on 2.11.1 |
If I understood correctly, 2.11.1 is intended to fix the regression that break logstash when compression is used in 2.10.0. Not a user of logstash, so I am not affected by this. I guess a few more fixes will be part of the new release. |
Hello, I have committed opensearch* update and I have added 2.10.0 version too. I did some minor modifications to opensearch ports. Now it is more opensearch friendly ( right permissions to directories and config files) https://cgit.freebsd.org/ports/commit/?id=c7f140c561d4ab126286d67be6b8377a35d82f04 |
The basic features I use work as expected. Some of you use more advance features, so please report failures.