Faithful on all four fields, including the urlsplit(...).path[1:] derivation that turns stackdriver:///airflow-tasks into airflow-tasks, and the | io_kwargs merge that legacy applies for this backend.

The guard is a genuine improvement rather than just a port:

if not log_name:
    raise ValueError(
        "Cannot derive a Stackdriver log name from "
        f"logging/remote_base_log_folder: {remote_base_log_folder!r}"
    )

Legacy had nothing here, so remote_base_log_folder = stackdriver:// with no path silently produced an empty gcp_log_name and a handler that could not work. Turning that into a startup error that names the offending config value is the right call, and parametrizing the rejection test over the bad forms is the right way to pin it.

Reviewing this alongside the sibling ports, the cluster made opposite choices on superficially similar "config is empty" cases — #70525 falls back to a class default host, this one raises. Both are correct for their situation: an empty Elasticsearch host has a sensible default, an empty Stackdriver log name does not. Worth noting only because the divergence is deliberate rather than accidental.

Adding a second entry under the existing remote-logging block alongside gs also confirms multiple schemes per provider work, which is useful to have demonstrated.

Rebased onto main before merging.

Drafted-by: Claude Code (Opus 5); reviewed by @potiuk before posting