[CLOUD] Add deployment data in the onboarding route #235847

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.

Sign up for GitHub

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

Jump to bottom

Merged

XavierM merged 7 commits into elastic:main from XavierM:cloud-deployment-name

Sep 30, 2025

+115 −2

Contributor

XavierM commented Sep 19, 2025 •

edited by kibanamachine

Loading

Summary

https://github.com/elastic/cloud-ui/issues/103

The data will be available via the /internal/cloud/solution API, the field is resource_data.deployment.name

Checklist

Unit or functional tests were updated or added to match the most common scenarios


          add deployment data in the onboarding route

e3e38af

XavierM requested review from a team as code owners

September 19, 2025 18:15

XavierM added Team:Cloud release_note:skip v9.2.0 v9.3.0 labels

XavierM requested a review from galaxxyz

September 19, 2025 18:15

XavierM added backport:skip backport:version and removed backport:skip labels


          [CI] Auto-commit changed files from 'node scripts/eslint_all_files --…

f977996

…no-cache --fix'

alexmarhaba mentioned this pull request

Show deployment name in breadcrumb #235938

Closed

galaxxyz approved these changes

View reviewed changes

Contributor

galaxxyz left a comment

LGTM

XavierM added 4 commits

September 23, 2025 07:18


          Merge branch 'main' into cloud-deployment-name

f3da283


          Merge branch 'main' of github.com:elastic/kibana into cloud-deploymen…

1ce559e

…t-name


          Merge branch 'cloud-deployment-name' of github.com:XavierM/kibana int…

ff93907

…o cloud-deployment-name


          fix test

70a2ff5

Dosant approved these changes

View reviewed changes

Contributor

elasticmachine commented Sep 29, 2025 •

edited

Loading

💔 Build Failed

Buildkite Build
Commit: 70a2ff5

Failed CI Steps

Test Failures

[job] [logs] Jest Tests #1 / defend_insights_loader getDefendInsightsDocsCount returns correct count
[job] [logs] Jest Tests #1 / defend_insights_loader getDefendInsightsDocsCount returns correct count
[job] [logs] Jest Tests #1 / defend_insights_loader getDefendInsightsDocsCount returns correct count

Metrics [docs]

‼️ ERROR: no builds found for mergeBase sha [14580d8]

History

💔 Build #342568 failed f3da283
💔 Build #341619 failed f977996


          Merge branch 'main' into cloud-deployment-name

95ef01f

gsoldevila approved these changes

View reviewed changes

XavierM merged commit bf1137f into elastic:main

12 checks passed

Contributor

kibanamachine commented Sep 30, 2025

Starting backport for target branches: 9.3

https://github.com/elastic/kibana/actions/runs/18130247369

Contributor

kibanamachine commented Sep 30, 2025

💔 All backports failed

Status	Branch	Result
❌	9.3	The branch "9.3" does not exist

Manual backport

To create the backport manually run:

node scripts/backport --pr 235847

Questions ?

Please refer to the Backport tool documentation

kibanamachine added the backport missing label

Contributor

kibanamachine commented Oct 2, 2025

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 235847 locally
cc: @XavierM

Dosant removed backport missing v9.3.0 labels

kibanamachine added the backport missing label

Contributor

kibanamachine commented Oct 3, 2025

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 235847 locally
cc: @XavierM

9 similar comments

Contributor

kibanamachine commented Oct 6, 2025

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 235847 locally
cc: @XavierM

Contributor

kibanamachine commented Oct 7, 2025

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 235847 locally
cc: @XavierM

Contributor

kibanamachine commented Oct 8, 2025

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 235847 locally
cc: @XavierM

Contributor

kibanamachine commented Oct 9, 2025

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 235847 locally
cc: @XavierM

Contributor

kibanamachine commented Oct 10, 2025

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 235847 locally
cc: @XavierM

Contributor

kibanamachine commented Oct 13, 2025

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 235847 locally
cc: @XavierM

Contributor

kibanamachine commented Oct 14, 2025

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 235847 locally
cc: @XavierM

Contributor

kibanamachine commented Oct 15, 2025

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 235847 locally
cc: @XavierM

Contributor

kibanamachine commented Oct 16, 2025

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 235847 locally
cc: @XavierM

rylnd pushed a commit to rylnd/kibana that referenced this pull request


          [CLOUD] Add deployment data in the onboarding route (elastic#235847)

1c4da1b

## Summary

 elastic/cloud-ui#103
 
The data will be available via the `/internal/cloud/solution` API, the
field is `resource_data.deployment.name`


### Checklist

- [x] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios

---------

Co-authored-by: kibanamachine <[email protected]>

Contributor

kibanamachine commented Oct 17, 2025

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 235847 locally
cc: @XavierM

12 similar comments

Contributor

kibanamachine commented Oct 20, 2025

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 235847 locally
cc: @XavierM

Contributor

kibanamachine commented Oct 21, 2025

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 235847 locally
cc: @XavierM

Contributor

kibanamachine commented Oct 22, 2025

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 235847 locally
cc: @XavierM

Contributor

kibanamachine commented Oct 23, 2025

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 235847 locally
cc: @XavierM

Contributor

kibanamachine commented Oct 24, 2025

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 235847 locally
cc: @XavierM

Contributor

kibanamachine commented Oct 27, 2025

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 235847 locally
cc: @XavierM

Contributor

kibanamachine commented Oct 29, 2025

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 235847 locally
cc: @XavierM

Contributor

kibanamachine commented Oct 30, 2025

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 235847 locally
cc: @XavierM

Contributor

kibanamachine commented Oct 31, 2025

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 235847 locally
cc: @XavierM

Contributor

kibanamachine commented Nov 3, 2025

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 235847 locally
cc: @XavierM

Contributor

kibanamachine commented Nov 4, 2025

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 235847 locally
cc: @XavierM

Contributor

kibanamachine commented Nov 5, 2025

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 235847 locally
cc: @XavierM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport missing backport:version release_note:skip Team:Cloud v9.2.0