Remove special cases from GetResourceName. #762
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@sunjayBhatia Do you mind taking a look? |
valerian-roche
approved these changes
Aug 29, 2023
sunjayBhatia
approved these changes
Aug 29, 2023
|
looks like this needs a main merge/rebase otherwise good to go |
Remove the unnecessary type checks from GetResourceName. Modern resource types should always have a `GetName` accessor, so the only real special case is for clusters. Signed-off-by: James Peach <jpeach@apache.org>
jpeach
force-pushed
the
simplify-get-resource-name
branch
from
9e558ee
to
e97d490
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Remove the unnecessary type checks from GetResourceName. Modern resource types should always have a
GetNameaccessor, so the only real special case is for clusters.