-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Fleet] Fix back button when adding integration from multiple integration package #116352
[Fleet] Fix back button when adding integration from multiple integration package #116352
Conversation
Pinging @elastic/fleet (Team:Fleet) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Quick fix and works as expected. 🚀
@elasticmachine merge upstream |
That was not in scope at the time, no. |
@elasticmachine merge upstream |
@elasticmachine merge upstream |
@elasticmachine merge upstream |
@elasticmachine merge upstream |
💛 Build succeeded, but was flaky
Metrics [docs]Async chunks
History
To update your PR or re-run it, just comment with: cc @nchaulet |
The following labels were identified as gaps in your version labels and will be added automatically:
If any of these should not be on your pull request, please manually remove them. |
…tions package (#116352) (#116535) Co-authored-by: Nicolas Chaulet <[email protected]>
Looks like this PR has backport PRs but they still haven't been merged. Please merge them ASAP to keep the branches relatively in sync. |
…tions package (#116352) (#116534) Co-authored-by: Nicolas Chaulet <[email protected]>
Hi @nchaulet Observations:
Screen Recording: AWS.DynamoDB.Metrics.-.Integrations.-.Elastic.-.Google.Chrome.2021-11-11.10-35-37.mp4Build details: cc: @EricDavisX |
Description
Resolve #116244
The cancel button when adding a new integration from a package with multiple integration should redirect to the integration (AWS billing for example) and not to the main package (AWS)
How to tests
Not related
@jen-huang Did we considered saving the integration on the package policy, to allow to edit the integration and not the whole package?