Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backport of Transit Active Tab into release/1.16.x #25628

Conversation

hc-github-team-secure-vault-core
Copy link
Collaborator

Backport

This PR is auto-generated from #25614 to be assessed for backporting due to the inclusion of the label backport/1.16.x.

The below text is copied from the body of the original PR.


This PR fixes an issue where transitioning from the transit edit route to the show route would result in none of the tabs being active.

image

After fix

Screen.Recording.2024-02-23.at.12.24.48.PM.mov

Overview of commits

@hc-github-team-secure-vault-core hc-github-team-secure-vault-core force-pushed the backport/ui/VAULT-24354/transit-tab-bug/weekly-creative-newt branch from 3ad9a3c to af0a3e2 Compare February 26, 2024 16:02
@hc-github-team-secure-vault-core hc-github-team-secure-vault-core force-pushed the backport/ui/VAULT-24354/transit-tab-bug/weekly-creative-newt branch from efe6886 to 0a5e987 Compare February 26, 2024 16:02
@github-actions github-actions bot added the hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed label Feb 26, 2024
Copy link

Build Results:
All builds succeeded! ✅

Copy link

CI Results:
All Go tests succeeded! ✅

@zofskeez zofskeez added this to the 1.16.0 milestone Feb 27, 2024
@zofskeez zofskeez merged commit 4facaf6 into release/1.16.x Feb 27, 2024
24 of 25 checks passed
@zofskeez zofskeez deleted the backport/ui/VAULT-24354/transit-tab-bug/weekly-creative-newt branch February 27, 2024 17:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants