Skip to content

bug: when adding a node to a group using the front-end node detail page the dropdown contains irrelevant groups #4872

Description

@wvandeun

h3. Component

[| #component]

API Server / GraphQL

h3. Infrahub version

[| #infrahub-version]

1.0.1

h3. Current Behavior

[| #current-behavior]

When you want to add a node to a group using the front-end node detail page, in the dropdown in which you can select the group we seem to be listing CoreAccountGroup nodes and CoreGeneratorGroup nodes (and maybe others). [!https://github.com/user-attachments/assets/c1fb9e01-83ff-4357-9b50-8d986b68bcc7!| https://github.com/user-attachments/assets/c1fb9e01-83ff-4357-9b50-8d986b68bcc7]

Should we add group_type internal to CoreAccountGroup and CoreGeneratorGroup so that hey get filtered out from the available candidates?

h3. Expected Behavior

[| #expected-behavior]

CoreAccountGroups and CoreGenerateGroup nodes should not be listed in the dropdown as available groups for users to add nodes to.

h3. Steps to Reproduce

[| #steps-to-reproduce]

  • set up an instance of infrahub
  • import the demo schema / data and demo-edge repository
  • create a new tag
  • navigate to the node detail page of the new tag
  • click the manage groups button
  • the list of available dropdowns will contain CoreAccountGroups and CoreGeneratorGroups

h3. Additional Information

[| #additional-information]

No response

Metadata

Metadata

Assignees

Labels

group/backendIssue related to the backend (API Server, Git Agent)priority/2This issue stalls work on the project or its dependents, it's a blocker for a releasetype/bugSomething isn't working as expected

Type

Fields

No fields configured for Bug.

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions