Constraints and limitations
HCP Vault Secrets is currently in public beta. The following constraints and limitations apply during the beta phase.
- HCP Vault Secrets does not have an SLA or production-grade guarantee of availability.
- HCP Vault Secrets offers only Bronze level support.
The free tier enables you to utilize HCP Vault Secrets for your own development purposes.
The following table lists the default limits/quota.
|Resource||Limit per organization|
|Activity Logs||Last 7 days|
There is currently no way to update the configuration of an existing sync integration. Users will need to delete and create a new sync integration if they want to make changes.
Also, at the moment it is impossible to delete integrations in the UI. This means even if you disconnect an integration from your application, the integration will persist and still show up as an option when connecting a new integration to an app. To get around this for now, you will need to delete integrations via the API.
There is a known bug with the raw API where a PATCH request to edit an App's Description without also passing the
sync_integrations field will result in all sync integrations being disconnected from the Application. To get around this, edit your App's Description in the UI or CLI, or pass your App's existing integrations in as part of your PATCH request body even though you aren't changing them.
If you accidentally disconnect your App's integrations this way, you can attach them again with a second PATCH request, as the integrations were not deleted, just disconnected.
Currently, HCP Vault Secrets only shows the Force Sync event on the audit logs. Other events related to integrations won't show up on audit logs.
At this time, you can connect the GitHub app to a single HCP project. Also, installing the GitHub app via GitHub marketplace won't work. Install the GitHub app through the HCP portal since any other method won't work.