Make profile and quotas optional for users

[amarao]

Hello.

Next improvement is a bit more intrusive and I'd like to discuss it beforehand.
I want to make profile and quota optional, by using default value (clickhouse_default_user_profile=default, and clickhouse_default_user_quota=default).

Moreover, I have two more ideas:

1. To make networks defaulting to 0.0.0.0/0 and ::/0.
2. To use clickhouse_dbs as default for clickhouse_users_custom[user].dbs.

Is it OK or it's too daring and insecure?

My goal is to have a very small config for initial use:

    clickhouse_dbs:
     - name: somedatabase
    clickhouse_users_custom:
     - name: someuser
       password: somepassword

[AlexeySetevoi]

Hi, Amarao. Thanks for your contribution. Thanks for discussing first :)
About using default profile and quota - i think this usefull, no any problem.

About defaulting 0.0.0.0/0 and ::/0:
My cons:

• Default behaviour of clickhouse(out-of-box) - listen only localhost and localhost6. This expected behaviour, and expected user expirience from main product, and addons(like this role) must not break it.

• I think this is totaly insecure. All we remember about open mysql, mongo and other unpassworded software on default ports. I think its important dont extend security impact field. Any expirienced user can redefine 1 time in playbook clickhouse_listen_host_default var and use listen 0.0.0.0/0 default behaviour.

About clickhouse_dbs - you want create on every database same user?

[amarao]

1. Thanks, I'll send PR shortly.
2. You are right. How about defaulting user.networks to clickhouse_listen_host_custom if it is defined, and to localhost (0/0, ::/0) if no?
3. After some thoughts: may be we can default to database with the name equal to username?

My goal is to make list of variables as small as possible by providing reasonable defaults.