Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

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

hashicorp / vault Public

Notifications You must be signed in to change notification settings
Fork 4.3k
Star 31.8k

Code
Issues 1.1k
Pull requests 261
Actions
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Security
Insights

Correct the post-unseal meaning of the seal status type#23022

Merged

sgmiller merged 5 commits intomainhashicorp/vault:mainfrom sgm/vault-7061/correct-seal-status-typeshashicorp/vault:sgm/vault-7061/correct-seal-status-typesCopy head branch name to clipboard

Oct 9, 2023

+67-47

Conversation Commits5 (5)Checks Files changed

Commits

Commits on Sep 12, 2023

Correct the post-unseal meaning of the seal status type
sgmiller
committed
changelog
sgmiller
committed
no longer needed
sgmiller
committed
Don't need this field either, which fixes unit tests
sgmiller
committed
fix unit tests
sgmiller
committed

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.