-
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
[APM] ensure rum_allow_origins setting only saves valid YAML strings #128703
Labels
apm:test-plan-done
Pull request that was successfully tested during the test plan
bug
Fixes for quality problems that affect the customer experience
Team:APM
All issues that need APM UI Team support
v8.2.0
Comments
ogupte
added a commit
to ogupte/kibana
that referenced
this issue
Mar 29, 2022
ogupte
added a commit
to ogupte/kibana
that referenced
this issue
Mar 29, 2022
ogupte
added a commit
that referenced
this issue
Mar 29, 2022
ogupte
added a commit
that referenced
this issue
Mar 29, 2022
ogupte
added a commit
to ogupte/kibana
that referenced
this issue
Mar 29, 2022
…lastic#128703) (elastic#128707) (cherry picked from commit 79039db)
ogupte
added a commit
that referenced
this issue
Mar 29, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
apm:test-plan-done
Pull request that was successfully tested during the test plan
bug
Fixes for quality problems that affect the customer experience
Team:APM
All issues that need APM UI Team support
v8.2.0
Ensures that the text values set in the
rum_allow_origins
setting (apm-server.rum.allow_origins
) will be checked if they are valid YAML strings and then wrapped in quotes if not. This fixes the bug #121934 that would fail when the user attempts to migrate from classic indices / standalong APM server to a fleet-managed APM server agent policy. The fix validates and updates the settings values only when a user attempts the migration.The text was updated successfully, but these errors were encountered: