Adding deprecation warning for data_frame_transforms roles #117521
Merged
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.
Issue - https://github.com/elastic/ml-team/issues/1389
Description
The
data_frame_transforms_user
anddata_frame_transforms_admin
roles have been marked as deprected for some time now. This change adds a critical deprecation warning that will block users from migrating to 9.0 until they update any transforms using these roles to instead use the equivalenttransforms_user
andtransforms_admin
roles. The process to do this is outlined in the documentation added in this PR. This documentation is currently not published and the location is not finalized. As such, the deprecation warning currently has an elastic URL that we can update once the documentation is published. This PR does not need to be blocked on the documentation change as we can dynamically change what it points to through the elastic links UI without need for a follow-up code review.Testing