[WIP] [SECURESIGN-1464] & [SECURESIGN-1193] | Adding Custom Key, Custom Config and Sharding Support for CTlog

[tommyd450]

As it stands Keys can be added as a variable in roles/tas_single_node/defaults/main.yml.
Custom Config will follow soon but will need to add custom treeId specifications.

When testing ensure the keys and or config you provide are inputed like the following:

tas_single_node_custom_ctlog_private_key: |
    <Key Here>

Update: Looking into creating a secret template so we can allow for easy management of keys within secrets removing the need to hardcode them within the config files.

[SequeI]

lgtm, thanks for fixing the issue

[SequeI]

@tommyd450 If you so wish, you could add a testdata folder and add this to our new user_provided scenario so it can be tested within our CI. Can be added in another PR once we finish up other user provisioned tickets though so no worries

[tommyd450]

@tommyd450 If you so wish, you could add a testdata folder and add this to our new user_provided scenario so it can be tested within our CI. Can be added in another PR once we finish up other user provisioned tickets though so no worries

Will do

[SequeI]

@tommyd450 Please add new ctlog config to our docs since it can get pretty confusing for users with the whole setup
(When you are done of course)
Thanks