Skip to content

bug: SSH Prefix change is not backwards compatible #18088

@bpmct

Description

@bpmct

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

It seems like the coder ssh behavior we modified to support a suffix no longer supports commands like ssh coder.<workspace name>.<agent name> despite attempts to maintain backwards compatibility.

Relevant Log Output

Expected Behavior

No response

Steps to Reproduce

Attempt it. See Slack thread

Environment

  • Host OS:
  • Coder version:

Additional Context

No response

Metadata

Metadata

Assignees

Labels

s1Bugs that break core workflows. Only humans may set this.

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

    pFad - Phonifier reborn

    Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

    Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


    Alternative Proxies:

    Alternative Proxy

    pFad Proxy

    pFad v3 Proxy

    pFad v4 Proxy