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

Check for compatibility encryption compatibility #100

Open
spiegela opened this issue Jul 8, 2018 · 0 comments
Open

Check for compatibility encryption compatibility #100

spiegela opened this issue Jul 8, 2018 · 0 comments

Comments

@spiegela
Copy link
Collaborator

spiegela commented Jul 8, 2018

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:

  1. Return an error within the tile configuration (not sure how to do this)
  2. Crash during startup with an instructive error message
@spiegela spiegela created this issue from a note in 2.1 (To Do) Jul 8, 2018
@spiegela spiegela removed this from To Do in 2.1 Aug 24, 2018
@spiegela spiegela added this to To do in 2.2 Aug 24, 2018
@rogalv rogalv removed this from To do in 2.2 Sep 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants