You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This PR is auto-generated from hashicorp#21604 to be assessed for backporting due to the inclusion of the label backport/1.19.
🚨
Warning automatic cherry-pick of commits failed. If the first commit failed,
you will see a blank no-op commit below. If at least one commit succeeded, you
will see the cherry-picked commits up to, not including, the commit where
the merge conflict occurred.
The person who merged in the original PR is: @jm96441n
This person should manually cherry-pick the original PR into a new backport PR,
and close this one when the manual backport PR is merged in.
merge conflict error: unable to process merge commit: "373ac54c9598a3b3de80837307305ba5d2432040", automatic backport requires rebase workflow
The below text is copied from the body of the original PR.
Description
JWT clusters were previously not being created correctly, this adds the plumbing to handle this in the enterprise fork
Backport
This PR is auto-generated from hashicorp#21604 to be assessed for backporting due to the inclusion of the label backport/1.19.
🚨
The person who merged in the original PR is:
@jm96441n
This person should manually cherry-pick the original PR into a new backport PR,
and close this one when the manual backport PR is merged in.
The below text is copied from the body of the original PR.
Description
JWT clusters were previously not being created correctly, this adds the plumbing to handle this in the enterprise fork
Testing & Reproduction steps
Links
PR Checklist
Overview of commits
The text was updated successfully, but these errors were encountered: