-
Notifications
You must be signed in to change notification settings - Fork 867
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'opensearch-project:main' into memory-circuit-breaker
- Loading branch information
Showing
7 changed files
with
157 additions
and
33 deletions.
There are no files selected for viewing
This file contains 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
65 changes: 65 additions & 0 deletions
65
release-notes/opensearch-dashboards.release-notes-1.3.1.md
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,65 @@ | ||
## Version 1.3.1 Release Notes | ||
|
||
- **[Branding] Allow for SSL setup failures (#1414)(#1417)** | ||
|
||
[Kawika Avilla](mailto:kavilla414@gmail.com) | ||
|
||
Setup HTTP Agent in the render portion when it did not need to be | ||
it just needed a one time setup for the life time of the server. | ||
|
||
Also if this fails to read the keys then it would fail. But it's | ||
only used for custom branding. We shouldn't failed for custom branding | ||
just rely on default branding. | ||
|
||
Issue Resolved: | ||
https://discuss.opendistrocommunity.dev/t/is-opensearch-dashboard-server-certificate-and-key-required-to-be-reloaded-everytime-when-gui-is-accessed/9069/13 | ||
|
||
* **[CI][build] Use BUILD_NUMBER for building bundles (#1371)(#1407)** | ||
|
||
[Kawika Avilla](mailto:kavilla414@gmail.com) | ||
|
||
When running a release build for example: | ||
|
||
``` | ||
yarn build-platform --linux --skip-os-packages --release | ||
``` | ||
|
||
The build task runs through get_build_number and | ||
checks how many commits you have locally and determines the | ||
build number. From there, and this is the value that | ||
is used to as a cache busting mechanism. | ||
|
||
However, in the release build repo | ||
https://github.com/opensearch-project/opensearch-build | ||
|
||
When this gets packaged and verified it actually pulls | ||
from the specified branch and only retrieves the HEAD | ||
commit. Thus making the count of commits locally equal | ||
to `1` and get_build_number always return `1` for releases | ||
essentially breaking the cache buster. | ||
|
||
The build repo however, sets an env variable of `BUILD_NUMBER` | ||
so if this value is available it will use it instead of commit | ||
count. | ||
|
||
The CI runs the unit tests and only gets the latest commit as well | ||
so instead of setting a env build number and basically creating | ||
the same unit test only check this locally. | ||
|
||
Issues resolved: | ||
|
||
- opensearch-project/opensearch-build#1769 | ||
- #1363 | ||
|
||
* **[Improvement] node healthcheck optimization (#1386)** | ||
|
||
[Kawika Avilla](mailto:kavilla414@gmail.com) | ||
|
||
Health check when enabled checked the entire cluster to get | ||
the value set from the nodeId. Switching the health check to | ||
query /\_cluster/state/nodes should provide the same data needed | ||
for the health check without transmitting the rest of the | ||
cluster state data over the network. | ||
|
||
Issue: | ||
#1354 |
This file contains 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
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,40 @@ | ||
/* | ||
* SPDX-License-Identifier: Apache-2.0 | ||
* | ||
* The OpenSearch Contributors require contributions made to | ||
* this file be licensed under the Apache-2.0 license or a | ||
* compatible open source license. | ||
* | ||
* Any modifications Copyright OpenSearch Contributors. See | ||
* GitHub history for details. | ||
*/ | ||
|
||
import { coreMock } from '../../../../../core/server/mocks'; | ||
import { CoreSetup } from '../../../../../core/server'; | ||
import { first } from 'rxjs/operators'; | ||
import { usageProvider } from '..'; | ||
import { ConfigSchema } from '../../../config'; | ||
|
||
describe('Search usage telemetry', () => { | ||
let mockCoreSetup: MockedKeys<CoreSetup>; | ||
const initializerContext = coreMock.createPluginInitializerContext({ | ||
search: { usageTelemetry: { enabled: false } }, | ||
}); | ||
|
||
it('trackSuccess should not throw with disabled usageTelemetry', async () => { | ||
const configObject = await initializerContext.config | ||
.create<ConfigSchema>() | ||
.pipe(first()) | ||
.toPromise(); | ||
expect(configObject.search.usageTelemetry.enabled).toBe(false); | ||
|
||
const searchUsage = usageProvider(mockCoreSetup, initializerContext); | ||
expect(searchUsage.trackSuccess(1)).resolves.not.toThrow(); | ||
}); | ||
|
||
it('trackError should not throw with disabled usageTelemetry', () => { | ||
const searchUsage = usageProvider(mockCoreSetup, initializerContext); | ||
expect(searchUsage.trackError.name).toBe('trackError'); | ||
expect(searchUsage.trackError()).resolves.not.toThrow(); | ||
}); | ||
}); |
This file contains 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
This file contains 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