[Synthetics] Add multispace monitor API test suite in private location#226042
Merged
cesco-f merged 5 commits intoelastic:mainfrom Jul 7, 2025
Merged
[Synthetics] Add multispace monitor API test suite in private location#226042cesco-f merged 5 commits intoelastic:mainfrom
cesco-f merged 5 commits intoelastic:mainfrom
Conversation
Contributor
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
e7fb08d to
e2a2843
Compare
e2a2843 to
9e96c64
Compare
02fe8b6 to
e5d2225
Compare
Contributor
💚 Build Succeeded
Metrics [docs]
History
|
Contributor
|
Starting backport for target branches: 8.19, 9.1 https://github.com/elastic/kibana/actions/runs/16117968823 |
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Jul 7, 2025
elastic#226042) This PR closes elastic#225431 by running the multispace monitor API test suite in both public and private locations. Public location tests are still skipped on cloud, as they are expected to fail. How to Test 1. Run the following command: ``` TEST_CLOUD_HOST_NAME=console.qa.cld.elstc.co \ TEST_CLOUD=1 \ NODE_TLS_REJECT_UNAUTHORIZED=0 \ CLOUD_HOST="issue-serverless-uksvx-pr226042-e71759.kb.eu-west-1.aws.qa.elastic.cloud" \ CLOUD_PASS="42m8ZieD9Ld1s8lB0u99L2zg" \ CLOUD_USER="testing-internal" \ TEST_KIBANA_URL="https://${CLOUD_USER}:${CLOUD_PASS}@${CLOUD_HOST}" \ TEST_ES_URL="${TEST_KIBANA_URL}:443" \ node --no-warnings scripts/functional_test_runner \ --exclude-tag skipCloud \ --config x-pack/test/api_integration/deployment_agnostic/configs/serverless/oblt.synthetics.serverless.config.ts \ --grep "LegacyAndMultiSpaceMonitorAPI" ``` 2. Expected Result: • Only private location tests should run. • All private location tests should pass. Note: If the deployment is recreated, you may need to update the values for `CLOUD_HOST` and `CLOUD_PASS`. (cherry picked from commit 9978674)
Contributor
💔 Some backports could not be created
Note: Successful backport PRs will be merged automatically after passing CI. Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation |
kibanamachine
added a commit
that referenced
this pull request
Jul 7, 2025
…ocation (#226042) (#226813) # Backport This will backport the following commits from `main` to `9.1`: - [[Synthetics] Add multispace monitor API test suite in private location (#226042)](#226042) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Francesco Fagnani","email":"fagnani.francesco@gmail.com"},"sourceCommit":{"committedDate":"2025-07-07T13:13:46Z","message":"[Synthetics] Add multispace monitor API test suite in private location (#226042)\n\nThis PR closes #225431 by running the multispace monitor API test suite\nin both public and private locations.\n\nPublic location tests are still skipped on cloud, as they are expected\nto fail.\n\nHow to Test\n\t1.\tRun the following command:\n```\nTEST_CLOUD_HOST_NAME=console.qa.cld.elstc.co \\\nTEST_CLOUD=1 \\\nNODE_TLS_REJECT_UNAUTHORIZED=0 \\\nCLOUD_HOST=\"issue-serverless-uksvx-pr226042-e71759.kb.eu-west-1.aws.qa.elastic.cloud\" \\\nCLOUD_PASS=\"42m8ZieD9Ld1s8lB0u99L2zg\" \\\nCLOUD_USER=\"testing-internal\" \\\nTEST_KIBANA_URL=\"https://${CLOUD_USER}:${CLOUD_PASS}@${CLOUD_HOST}\" \\\nTEST_ES_URL=\"${TEST_KIBANA_URL}:443\" \\\nnode --no-warnings scripts/functional_test_runner \\\n --exclude-tag skipCloud \\\n --config x-pack/test/api_integration/deployment_agnostic/configs/serverless/oblt.synthetics.serverless.config.ts \\\n --grep \"LegacyAndMultiSpaceMonitorAPI\"\n```\n2.\tExpected Result:\n\t•\tOnly private location tests should run.\n\t•\tAll private location tests should pass.\n\nNote:\nIf the deployment is recreated, you may need to update the values for\n`CLOUD_HOST` and `CLOUD_PASS`.","sha":"9978674c232c4eb9a7a999136358a071dccb7c0a","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","ci:project-deploy-observability","backport:version","v9.1.0","v8.19.0","author:obs-ux-management","v9.2.0"],"title":"[Synthetics] Add multispace monitor API test suite in private location","number":226042,"url":"https://github.com/elastic/kibana/pull/226042","mergeCommit":{"message":"[Synthetics] Add multispace monitor API test suite in private location (#226042)\n\nThis PR closes #225431 by running the multispace monitor API test suite\nin both public and private locations.\n\nPublic location tests are still skipped on cloud, as they are expected\nto fail.\n\nHow to Test\n\t1.\tRun the following command:\n```\nTEST_CLOUD_HOST_NAME=console.qa.cld.elstc.co \\\nTEST_CLOUD=1 \\\nNODE_TLS_REJECT_UNAUTHORIZED=0 \\\nCLOUD_HOST=\"issue-serverless-uksvx-pr226042-e71759.kb.eu-west-1.aws.qa.elastic.cloud\" \\\nCLOUD_PASS=\"42m8ZieD9Ld1s8lB0u99L2zg\" \\\nCLOUD_USER=\"testing-internal\" \\\nTEST_KIBANA_URL=\"https://${CLOUD_USER}:${CLOUD_PASS}@${CLOUD_HOST}\" \\\nTEST_ES_URL=\"${TEST_KIBANA_URL}:443\" \\\nnode --no-warnings scripts/functional_test_runner \\\n --exclude-tag skipCloud \\\n --config x-pack/test/api_integration/deployment_agnostic/configs/serverless/oblt.synthetics.serverless.config.ts \\\n --grep \"LegacyAndMultiSpaceMonitorAPI\"\n```\n2.\tExpected Result:\n\t•\tOnly private location tests should run.\n\t•\tAll private location tests should pass.\n\nNote:\nIf the deployment is recreated, you may need to update the values for\n`CLOUD_HOST` and `CLOUD_PASS`.","sha":"9978674c232c4eb9a7a999136358a071dccb7c0a"}},"sourceBranch":"main","suggestedTargetBranches":["9.1","8.19"],"targetPullRequestStates":[{"branch":"9.1","label":"v9.1.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/226042","number":226042,"mergeCommit":{"message":"[Synthetics] Add multispace monitor API test suite in private location (#226042)\n\nThis PR closes #225431 by running the multispace monitor API test suite\nin both public and private locations.\n\nPublic location tests are still skipped on cloud, as they are expected\nto fail.\n\nHow to Test\n\t1.\tRun the following command:\n```\nTEST_CLOUD_HOST_NAME=console.qa.cld.elstc.co \\\nTEST_CLOUD=1 \\\nNODE_TLS_REJECT_UNAUTHORIZED=0 \\\nCLOUD_HOST=\"issue-serverless-uksvx-pr226042-e71759.kb.eu-west-1.aws.qa.elastic.cloud\" \\\nCLOUD_PASS=\"42m8ZieD9Ld1s8lB0u99L2zg\" \\\nCLOUD_USER=\"testing-internal\" \\\nTEST_KIBANA_URL=\"https://${CLOUD_USER}:${CLOUD_PASS}@${CLOUD_HOST}\" \\\nTEST_ES_URL=\"${TEST_KIBANA_URL}:443\" \\\nnode --no-warnings scripts/functional_test_runner \\\n --exclude-tag skipCloud \\\n --config x-pack/test/api_integration/deployment_agnostic/configs/serverless/oblt.synthetics.serverless.config.ts \\\n --grep \"LegacyAndMultiSpaceMonitorAPI\"\n```\n2.\tExpected Result:\n\t•\tOnly private location tests should run.\n\t•\tAll private location tests should pass.\n\nNote:\nIf the deployment is recreated, you may need to update the values for\n`CLOUD_HOST` and `CLOUD_PASS`.","sha":"9978674c232c4eb9a7a999136358a071dccb7c0a"}}]}] BACKPORT--> Co-authored-by: Francesco Fagnani <fagnani.francesco@gmail.com>
kertal
pushed a commit
to kertal/kibana
that referenced
this pull request
Jul 25, 2025
elastic#226042) This PR closes elastic#225431 by running the multispace monitor API test suite in both public and private locations. Public location tests are still skipped on cloud, as they are expected to fail. How to Test 1. Run the following command: ``` TEST_CLOUD_HOST_NAME=console.qa.cld.elstc.co \ TEST_CLOUD=1 \ NODE_TLS_REJECT_UNAUTHORIZED=0 \ CLOUD_HOST="issue-serverless-uksvx-pr226042-e71759.kb.eu-west-1.aws.qa.elastic.cloud" \ CLOUD_PASS="42m8ZieD9Ld1s8lB0u99L2zg" \ CLOUD_USER="testing-internal" \ TEST_KIBANA_URL="https://${CLOUD_USER}:${CLOUD_PASS}@${CLOUD_HOST}" \ TEST_ES_URL="${TEST_KIBANA_URL}:443" \ node --no-warnings scripts/functional_test_runner \ --exclude-tag skipCloud \ --config x-pack/test/api_integration/deployment_agnostic/configs/serverless/oblt.synthetics.serverless.config.ts \ --grep "LegacyAndMultiSpaceMonitorAPI" ``` 2. Expected Result: • Only private location tests should run. • All private location tests should pass. Note: If the deployment is recreated, you may need to update the values for `CLOUD_HOST` and `CLOUD_PASS`.
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
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.
This PR closes #225431 by running the multispace monitor API test suite in both public and private locations.
Public location tests are still skipped on cloud, as they are expected to fail.
How to Test
1. Run the following command:
• Only private location tests should run.
• All private location tests should pass.
Note:
If the deployment is recreated, you may need to update the values for
CLOUD_HOSTandCLOUD_PASS.