-
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
[7.x] Ensure deprecation documentationUrl's point to correct doc branch #114263
Conversation
This was made possible via PR elastic#113600.
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.
Security plugin code changes LGTM
I got some I18n test errors because - as far as I can see - I've changed the input to I get why this can be problematic because these strings are to be translated. But in any case, I guess the right approach is to remove the URLs from these all together since they seem to just be duplicates of the URL in I've fixed this in this new commit to the PR: d21c627. |
FYI: @elastic/apm-ui + @elastic/kibana-reporting-services + @elastic/datavis I've not been able to update your deprecation messages in this PR because they do not use the same setup with access to There's a similar PR for |
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.
maps changes LGTM
code review
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.
Thanks for doing this.
@elasticmachine merge upstream |
retest |
@elasticmachine merge upstream |
💚 Build SucceededMetrics [docs]
History
To update your PR or re-run it, just comment with: cc @watson |
This was made possible via PR #113600.
This PR does not do anything about the
documenationUrl
usage in the following files as they do not currently have access toConfigDeprecationContext
:This PR goes directly into the
7.x
branch. In regards to deprecation messages there's too many differences betweenmaster
and7.x
to warrant a single PR tomaster
that's then backported to7.x
. I've made another PR specifically formaster
: #114264.