UNOMI-947/946: Platform hygiene, graphql-ui upgrade, and IT cluster health#812
Open
sergehuber wants to merge 4 commits into
Open
UNOMI-947/946: Platform hygiene, graphql-ui upgrade, and IT cluster health#812sergehuber wants to merge 4 commits into
sergehuber wants to merge 4 commits into
Conversation
…ealth Batch dependency and frontend upgrades for 3.1 GA: align swagger-ui feature with pom version, bump error_prone/logback/jsch, upgrade GraphiQL 5 with relative URLs, and harden IT search cluster replica enforcement.
Absorb Dependabot #804-808 security bumps (lodash, js-yaml, markdown-it, linkify-it, postcss, serialize-javascript) that the GraphiQL 5 lock refresh did not pick up automatically.
index.number_of_replicas is not a valid cluster persistent setting. Use a composable index template for new indices and _all/_settings for existing ones (migration snapshot restore path).
Split UNOMI-946 cluster prep into explicit stages: pre-Unomi baseline, post-snapshot restore, post-shell-migration, and post-Unomi health check. Apply zero-replica settings per index (ES/OS compatible) and re-enforce after migration before unomi:start.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Plain-language summary
Unomi 3.1 still shipped an old Swagger UI bundle version in Karaf while the REST module already used a newer one. The GraphQL playground also used outdated frontend libraries and hard-coded localhost URLs. Integration tests could fail on Elasticsearch because single-node clusters turned yellow when indices kept a replica count of one.
This change aligns Swagger UI with the project version, upgrades the GraphQL UI stack, bumps safe Java dependencies, and makes the IT harness enforce zero replicas on the search cluster before and after migration.
What changed
${swagger-ui.version}inunomi-rest-uiKaraf feature (5.27.1).configureSearchEngineForTesting(),fixRestoredIndexReplicas(), andassertClusterHealthy()inBaseIT; call from migration IT after snapshot restore; set ESminimalClusterState=YELLOWin IT config; teachElasticSearchHealthCheckProvideryellow tolerance like OpenSearch.error_prone_annotations2.50, logback-classic 1.2.13, router jsch 0.1.55_1 (poms + feature.xml).createRoot, webpack support for Monaco/CSS.Test plan
yarn build:productioningraphql/graphql-uimvn -pl graphql/graphql-ui,wab,kar,extensions/healthcheck -am test-compile -DskipTestsmvn -Pintegration-tests test-compileinitestsHealthCheckIT,Migrate16xToCurrentVersionIT)References
UNOMI-947, UNOMI-946