FE: Topics: Fix connectors tab permissions

[germanosin]

…EW permission

• Breaking change? (if so, please describe the impact and migration path for existing application instances)

What changes did you make? (Give an overview)

Is there anything you'd like reviewers to focus on?

How Has This Been Tested? (put an "x" (case-sensitive!) next to an item)

• No need to
• Manually (please, describe, if necessary)
• Unit checks
• Integration checks
• Covered by existing automation

Checklist (put an "x" (case-sensitive!) next to all the items, otherwise the build will fail)

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (e.g. ENVIRONMENT VARIABLES)
• My changes generate no new warnings (e.g. Sonar is happy)
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged

Check out Contributing and Code of Conduct

A picture of a cute animal (not mandatory but encouraged)

[Copilot]

Pull Request Overview

This PR fixes issue #1511 by changing the permission requirement for the Connectors tab from ANALYSIS_VIEW to VIEW, making it accessible to users with basic view permissions rather than requiring analytics-specific permissions.

Key changes:

• Updated the Connectors tab permission from Action.ANALYSIS_VIEW to Action.VIEW in the Topics component

Comments suppressed due to low confidence (1)

frontend/src/components/Topics/Topic/Topic.tsx:248

• The Connectors tab lacks test coverage. Other tabs (Overview, Messages, Consumers, Settings, Statistics) have tests in Topic.spec.tsx, but there's no test case for the Connectors tab even though the component is imported and used. Consider adding a test similar to the other tab tests:

it('renders Connectors tab', () => {
  itExpectsCorrectPageRendered(
    clusterTopicConnectorsPath(),
    'Connectors',
    'ConnectorsMock'
  );
});

And add the corresponding mock at the top of the test file:

jest.mock('components/Topics/Topic/Connectors/Connectors', () => () => (
  <>ConnectorsMock</>
));

        {isConnectorsAvailable && (
          <ActionNavLink
            to={clusterTopicConnectorsRelativePath}
            className={({ isActive }) => (isActive ? 'is-active' : '')}
            permission={{
              resource: ResourceType.TOPIC,
              action: Action.VIEW,
              value: topicName,
            }}
          >
            Connectors
          </ActionNavLink>
        )}

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.