-
Notifications
You must be signed in to change notification settings - Fork 159
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 nextUrl validation to incorporate serverBasePath (#2048) (#2050) #2102
base: 2.15
Are you sure you want to change the base?
Update nextUrl validation to incorporate serverBasePath (#2048) (#2050) #2102
Conversation
…roject#2048) (opensearch-project#2050) (cherry picked from commit fc4f6a2) Signed-off-by: Yiheng Cao <65160922+Crispy-fried-chicken@users.noreply.github.com>
9513c5e
to
6ca0e85
Compare
Hi @Crispy-fried-chicken , there are no plans for a 2.15.1 release. I would be happy to accept this backport, but you will need to manually create a zip of this dashboards plugin to get this change for an instance of OSD running 2.15.0. FYI There was a follow-up to this PR with a bugfix that should also be included: #2096 |
@cwperks What does it mean? sorry I‘m not familiar with it, maybe you can tell me how? Besides, I saw here is some unit tests don't pass, can you tell me how to fix it? Thank you! |
@Crispy-fried-chicken It means that to consume this change would require manually creating a zip of this dashboards plugin and installing it manually. To create a zip of a plugin, checkout the corresponding branch and run You can then use |
I run
I run |
You need to clone this repo within plugin folder of: https://github.com/opensearch-project/opensearch-dashboards, plugin_helpers is found within OSD repo. |
I run it, but still failed. the error is :
and I run the |
Try running |
Hi @Crispy-fried-chicken we actually usually do not check in the zip file into the code base. Instead it is built into the distribution using the opensearch-build repo. @cwperks what do you think of this PR? |
See my initial comment. I'm happy to merge this PR when there is passing CI. I just wanted to convey that there will not be an official OpenSearch 2.15.1 release so consuming the change introduced in this PR will require a user to manually create artifacts and install in their deployments. |
If 2.15.1-SNAPSHOT artifacts don't exist for all components then they need to be generated. It also looks like there are lint issues on the PR which need to be resolves with Again, official 2.15.1 artifacts will never be published so in order for anyone to consume this change requires directly building from the source which you can already do without merging this PR. |
Here is a vulnerability which is fixed in the main branch and 2.16(fc4f6a2) but is not fixed in the branch of 2.15, maybe it should be backported?