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
There are several situation, in which the repository bucket or user may not be created properly:
The repository-service or repository-plan is not set in the broker configuration.
The selected repository-service is encrypted, but the default namespace is not.
There is a name conflict in the repository-user
If the bucket is able to be created, without the user, it can require manual intervention to put the ECS components into a rational state before the broker can be started. We should perform more extensive checks during startup, to make sure that these issues don't arise.
The text was updated successfully, but these errors were encountered:
The desire behavior is that the broker should crash any time the required repository resources can't be created. The broker also needs to validate that the settings are all create, as customers have run into partially created environments when messing around with settings. Required resources include:
Repository bucket
Repository user
Full control ACL for repository user on repository bucket
Configured base URL or object-endpoint
Replication group
Namespace
Management user and password
spiegela
changed the title
Broker doesn't crash when can't create bucket
Perform additional checks during repo bucket/user creation
Jul 8, 2018
There are several situation, in which the repository bucket or user may not be created properly:
repository-service
orrepository-plan
is not set in the broker configuration.repository-service
is encrypted, but the default namespace is not.repository-user
If the bucket is able to be created, without the user, it can require manual intervention to put the ECS components into a rational state before the broker can be started. We should perform more extensive checks during startup, to make sure that these issues don't arise.
The text was updated successfully, but these errors were encountered: