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
Currently, there are no checks to evaluate if an encryption-enabled bucket instance could be created. If the customer defines a default namespace with encryption disabled, and then creates a service instance with encryption enabled, the bucket-create operation fails without a very instructive error message.
If the default namespace has encryption disabled, but the catalog contains an encryption-enabled service, IMO we should either:
Return an error within the tile configuration (not sure how to do this)
Crash during startup with an instructive error message
The text was updated successfully, but these errors were encountered:
Currently, there are no checks to evaluate if an encryption-enabled bucket instance could be created. If the customer defines a default namespace with encryption disabled, and then creates a service instance with encryption enabled, the bucket-create operation fails without a very instructive error message.
If the default namespace has encryption disabled, but the catalog contains an encryption-enabled service, IMO we should either:
The text was updated successfully, but these errors were encountered: