Force default bucket plugin only if necessary

[leplatrem]

@Natim r?

[almet]

Should we issue a warning and ask for it to be included in the configuration explicitely now?

[Natim]

I don't think people should include it in the config so IMHO we can let it as it is.

[leplatrem]

I don't think people should include it in the config so IMHO we can let it as it is.

But that's the only way to have default bucket work with kinto-attachment ! And that's the main reason we put the default bucket as a plugin :) See #277

Should we issue a warning and ask for it to be included in the configuration explicitely now?

yes, I think so

[almet]

Then, how do you remove the feature?

[Natim]

As far as I know we don't aim to make it an optional feature do we?

[leplatrem]

Then, how do you remove the feature?

We cannot at this stage.

Currently the client of v1 expects the default bucket to create collections implicitly.

Being able to remove the default bucket could be part of the API v2.

[leplatrem]

Ready to review/merge!

[Natim]

It seems strange to me to add it there if it is already added automatically.

[leplatrem]

So that adding it automatically could be removed in 2.X, whereas config files can stay

[Natim]

r+