Domain Proxy NMS UI still active when Domain Proxy module is disabled in deployment

[xbend]

As reported, the Domain Proxy UI functionality is still active even if domain proxy has been disabled in deployment helm charts. Please note, Domain Proxy module is disabled by default, and requires manual enabling per environment deployment. However NMS UI implementation for Domain Proxy remains always present.

Suggested options are:

• There is a feature flag mechanism that we were thinking about removing because it is currently not really used. If we use that one would have to separately enable it on a per organisation basis.
• Probing if Domain Proxy is enabled by hitting some endpoint and hiding disabling the UI if we get an error.
• Somehow persisting whether Domain Proxy is enabled.

Approach: Investigate internally if suggestions can be applied and are consistent with similar cases in Magma. If not, extend discussion to Magma NMS community to figure out best approach.

[thmsschmitt]

@xbend It would be good to have this fixed before the 1.8 release otherwise everybody will constantly get those CBSD errors.

[xbend]

@thmsschmitt Is there a timeline for creating the 1.8 branch? How much time do we have to fix the issue?

[thmsschmitt]

That is a question that can be better answered by other people. Let's have this discussion in Slack, I'll raise it in the relevant channel. Imho we could also implement a simple solution first e.g. suppress the error and come up with a proper fix later.

[Neudrino]

Let's have this discussion in Slack

E.g. the #magma-releases channel with this post.

[Neudrino]

https://github.com/magma/magma/pull/13428 only provided a temporary mitigation of the problem but not a real fix.

That means, that this issue should be reopened until a proper fix is provided.