8000 avoid provisioner naming collisions · Issue #80 · coder/internal · GitHub
[go: up one dir, main page]
Skip to content
< 6478 header class="HeaderMktg header-logged-out js-details-container js-header Details f4 py-3" role="banner" data-is-top="true" data-color-mode=light data-light-theme=light data-dark-theme=dark>

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Appearance settings
avoid provisioner naming collisions #80
New issue
New issue
Open
Feature
Open
avoid provisioner naming collisions#80
Feature
Milestone
 
Orgs & Custom Roles Enhancements
@Kira-Pilot

Description

@Kira-Pilot
Kira-Pilot
opened on Sep 27, 2024

Currently, any provisioners with the same name will collide on the FE, meaning only 1 provisioner will appear. This can occur more frequently than one would assume as we don't mandate that provisioners are named at all. Unnamed provisioners adopt the machine's host name; therefore collisions are fairly common and confusing. We should explore a fix so that all provisioners created are shown distinctly in the UI and CLI.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions
      0