Remove deprecation warning for local runtime type #2862
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.
Fixes #2855
What changes were proposed in this pull request?
Based on some discussion related to #2855, we decided to consider lowercase
local
equivalent to uppercaseLOCAL
when checking against runtime types. This PR suppresses the warning message about using (eventually) deprecated runtime type names (kfp
,airflow
) for the local runtime only. This is the 'path of least resistance' for this issue. If we ever fully remove the ability to query with the lowercaselocal
, we'll probably want the frontend to adjust its API call to use theLOCAL
RuntimeProcessorType
Enum member.How was this pull request tested?
Queried the
elyra/pipeline/components/{runtime_type}
endpoint withlocal
as theruntime_type
, and no warning message is shown in the logs. A new test is added to cover this case as well.Developer's Certificate of Origin 1.1