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
We were previously (on 0.x) creating the containers / buckets automatically when using adapters. This can lead to security flaws in case where the bucket is not created as the adapter's user want to.
Buckets creation is beyound Gaufrette scope and so should not be managed by Gaufrette. Buckets used by Gaufrette shoud be created by the developer (or any other way) and should be properly configured for the developer needs.
Thus, Gaufrette should not automatically create buckets when they do not exist. This will remove the create flag passed to adapters's constructor, and the usage of an adapter on an unexisting bucket should raise an exception.
The container creation is not the responsibility of Gaufrette as it
could lead to security flaws. The user should create the container on
its own (manually or by using the OpenStack SDK).
See #618 for more details.
Related to KnpLabs#618
We throw an exception when building the adapter if the specified base
directory does not exist. The write methods can still create sub
directories (eg /base/my/very/deep/dir), however the /base directory
have to be present.
The developer should create this directory on its own before using the
adapter.
Related to KnpLabs#618.
Container creation is out of Gaufrette scope. The container should be
created by the deleveloper on its own.
Thus, the multi container mode has been removed, as it was creating
containers on the fly.
Related to KnpLabs#618.
Container creation is out of Gaufrette scope. The container should be
created by the deleveloper on its own.
Thus, the multi container mode has been removed, as it was creating
containers on the fly.
We were previously (on
0.x
) creating the containers / buckets automatically when using adapters. This can lead to security flaws in case where the bucket is not created as the adapter's user want to.Buckets creation is beyound Gaufrette scope and so should not be managed by Gaufrette. Buckets used by Gaufrette shoud be created by the developer (or any other way) and should be properly configured for the developer needs.
Thus, Gaufrette should not automatically create buckets when they do not exist. This will remove the
create
flag passed to adapters's constructor, and the usage of an adapter on an unexisting bucket should raise an exception.TODO
The text was updated successfully, but these errors were encountered: