The system namespace is visible even when listing "User" flows

[loicmathieu]

Describe the issue

The system namespace is visible even when listing "User" flows.

This leads to an empty list of flows when selecting it.

So we had to un-check USER type of flow to list the system flows

Environment

• Kestra Version: 0.19.0-SNAPSHOT
• Operating System (OS/Docker/Kubernetes):
• Java Version (if you don't run kestra in Docker):

[Mahitej28]

@loicmathieu, can I work on this issue under hacktoberfest'24... also let me know what's need to be done for the same.

[loicmathieu]

@Mahitej28 you can work on the issue but I'm not sure what needs to be done, if you didn't find it by yourself maybe find an easier issue to work on.

[Mahitej28]

Okay will have a look

[MilosPaunovic]

@Mahitej28 But if you're up for a try, please go ahead! 🚀

[MilosPaunovic]

It's true that a current solution feels a bit weird, but it's intended behavior.

We could amend it in two ways:

1. Don't show system in the namespace filter options.
2. If selecting system namespace as a filter option, we remove the User Flows and add System Flows filter, which can lead to more confusion as that way we'd be changing filters for user in way it's not expected.

I would prefer either first option or leaving it as is now. WDYT @Ben8t?

[Ben8t]

1. Don't show system in the namespace filter options.

Seems the good solution for now. system is a "protected" namespace name (hence the filter User vs System).

Please take account that it can be configurable:

kestra:
  system-flows:
    namespace: system

So we should filter on this namespace value

[MilosPaunovic]

I have filtered out system namespace on NS selection filter component we're using throughout the project in this PR, but we definitely need to tackle this issue to have everything handled in a proper way.