Skip to content

Proper handling of httpbins from different workspaces with the same name #106

@nexus49

Description

@nexus49

Context

Investigate if httpbin resources with the same name/namespace but from different workspaces are handled correctly. In my tests I had the impression that this is not handled correctly.

Expected Result

2 httpbin resources default/test in different workspaces should lead to:

  • 2 different httpbin resources
  • 2 different deployments

Tasks

  • Investigate current behavior when httpbins with same name/namespace exist in different workspaces
  • Fix handling if not working correctly

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions