Backport support for generic hostname to backend/remote #32610
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.
Duplicates generic hostname enhancement to backend/remote. We don't have a history of sharing code between the cloud and remote backends and this was a very small change so I basically duplicated #32571
My thinking is that this enhancement falls close to being a bug fix so it might not be worthwhile to insist on a migration to cloud backend to get it. I'm open to either a different implementation that shares code or not backporting it at all.
Target Release
1.4.0