Fix doubled border on the Users tab of the secrets permissions table

Mireya Andresrequested to merge
secrets/fix-permissions-table-border into master

What does this MR do and why?

This makes sure the class is applied to all tabs of the permissions table and fixes the rendering of the top border for all of them, and not just the first one.

References

Follow-up for !259303 (comment 3956220932).

Screenshots or screen recordings

Before After

How to set up and validate locally

Setting up the secrets manager

  1. Run gdk on SaaS: GITLAB_SIMULATE_SAAS=1 gdk start

  2. Set up the GDK with OpenBao: https://gitlab.com/gitlab-org/gitlab-development-kit/-/blob/main/doc/howto/openbao.md

  3. Enable the following feature flags: secrets_manager, group_secrets_manager, secrets_manager_paid_experience. secrets_manager_instance_enrollment.

  4. The entitlement resolver communicates with the CDot API. We will monkey-patch this and mock the results of the API so we can control the entitlement state locally. To mock the API, add these files config/secrets_manager_stub.yml and config/initializers/zz_secrets_manager_stub.rb and restart your gdk. This will mock the entitlement state returned by GraphQL (which we normally get from CDot).

    secrets_manager_stub.yml

    zz_secrets_manager_stub.rb

These will allow you to test with different entitlement states. By default, it is trial_eligible. If you need to clear/reset the cached entitlement, run SecretsManagement::Entitlement.stub_reset! from the rails console.

Verifying the feature

  1. Enable the secrets manager for a top-level group via http://gdk.test:3000/path-to-group/-/secrets
  2. Go to Settings > Secure to view the permissions table and verify the changes.

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Merge request reports