no issue - configuration changes and old names deprecation

[pounard]

Variant of #162

• adds a new Configuration object,
• merges both standalone and symfony bundle configuration objects,
• rationalize yaml configuration, makes it much easier to understand,
• allow specific configuration of pretty much everything on a per connection basis.

[SimonMellerin]

Seems good to me thanks 👍

[SimonMellerin]

Just may be you can update sample config file to put at the top of the file config that users will want to edit the most.

Like connections and anonymization, like all other have default values.

But, not sure about that, I let you choose if this is a good idea or not !

[SimonMellerin]

if there's only one connection, what's its name ?

does the 'connection' stage needed ? if not, may be you can omit this part and just redirect to the doc for a multiconnection setup

[SimonMellerin]

May be for the standalone version, we can simplify the anonymization declaration like this:

    my_table: 
        my_email_column: email
        my_age_column: 
            anonymizer: integer
            options: {delta: 15}
    my_table_2:
        my_firstname_column: firstname

# Or with a yaml 
anonymization: ./db_tools.anonymization.yaml

# Or multiconneciton 
anonymization: 
    connection_one: 
        my_table: 
            my_email_column: email
            my_age_column: 
                anonymizer: integer
                options: {delta: 15}
        my_table_2:
            my_firstname_column: firstname
    connection_two: 
        my_table: 
            my_email_column: email
            my_age_column: 
                anonymizer: integer
                options: {delta: 15}
        my_table_2:
            my_firstname_column: firstname

# Or multiconneciton yaml
anonymization: 
    connection_one: ./db_tools.anonymization.connection_one.yaml
    connection_two: ./db_tools.anonymization.connection_one.yaml

Seems easier to understand and to use

[pounard]

Failure was a random MySQL float error, I merged anyway.