commit ee9cf369a64f78f5de7c0fae482c3c34547a4295
Author: Luigi Toscano <email address hidden>
Date: Mon Mar 18 18:35:31 2019 +0100
Configuration: populate the [trustee] section too
Sahara have been (mis)using few values from keystone_authtoken to set the
configuration for trust for a long while. This is not a recommended
practice as those values are for private use of keystonemiddelware.
During the queens release a new configuration section (trustee)
was introduced to collect those parameters: https://review.openstack.org/#/c/524936/
The existing parameters are still read if [trustee] is not available,
but the behavior is fragile and unsupported, so it is officially deprecated
in Sahara as well.
The trustee section is populated from the same values used for
keyston_authtoken, so the same class is re-used in order to write
the content of the section.
Reviewed: https:/ /review. openstack. org/643899 /git.openstack. org/cgit/ openstack/ puppet- sahara/ commit/ ?id=ee9cf369a64 f78f5de7c0fae48 2c3c34547a4295
Committed: https:/
Submitter: Zuul
Branch: master
commit ee9cf369a64f78f 5de7c0fae482c3c 34547a4295
Author: Luigi Toscano <email address hidden>
Date: Mon Mar 18 18:35:31 2019 +0100
Configuration: populate the [trustee] section too
Sahara have been (mis)using few values from keystone_authtoken to set the
configuration for trust for a long while. This is not a recommended
practice as those values are for private use of keystonemiddelware.
During the queens release a new configuration section (trustee) /review. openstack. org/#/c/ 524936/
was introduced to collect those parameters:
https:/
The existing parameters are still read if [trustee] is not available,
but the behavior is fragile and unsupported, so it is officially deprecated
in Sahara as well.
The trustee section is populated from the same values used for authtoken, so the same class is re-used in order to write
keyston_
the content of the section.
Closes-Bug: #1763361 4140680d826869c 25d855e77d1
Change-Id: I8c63c32d995cbe