Specified fernet token keys are not utilised

Unfortunately, despite setting the fernet tokens in an environment file used with TripleO, they're not used as expected, and therefore if using a multi-site configuration, one token issued by one site is not automatically valid in another. Inside of the configuration we use the following parameters for fernet:

    # Enable fernet tokens
    keystone::enable_fernet_setup: true
    keystone::token_provider: 'fernet'

    # Set the fernet token keys
    keystone::fernet_keys:
      '/etc/keystone/fernet-keys/0':
        content: 'pTZtu4rmWkYGVpvamj3iysQkBknw026KixVzN-ybBKI='
      '/etc/keystone/fernet-keys/1':
        content: 'IOV0IUtppYRei_B8NxWDw-RNfMGUmCeYSPofOH4QFPY='

Yet when deployed, we see the following:

[root@region-one-controller-0 ~]# cat /etc/keystone/fernet-keys/0; echo
tWmKQ_qrzVoh1er4WdkuNbYhkw26mP8rVEMuZJpzlko=

[root@region-one-controller-0 ~]# cat /etc/keystone/fernet-keys/1; echo
ir7crS67c-_sLNrsrgGjHWiuFqP1lrSpWuAr8X0pWys=

It's my belief that when the 'keystone::enable_fernet_setup: true' option is invoked, it creates new keys automatically, and potentially ignores, or even overwrites the ones that we attempt it to utilise as per the TripleO configuration. Therefore, the only workaround I've found is to either script it as a post-deployment hook, or to manually copy the key files between the resulting regions, which obviously has problems if we decide to add other regions, or other controllers to an existing region. Thanks!