This PS moves the chart to use secrets to store potentially sensitive
config information.
Depends-On: https://review.openstack.org/#/c/593732
Change-Id: I884a68b379beefa3aa73018613ac37c0f3ee089d
Signed-off-by: Pete Birley <pete@port.direct>
This updates Deckhand to be compatible with the current
OpenStack-Helm Helm Toolkit. This includes:
- Using HTK manifest templates
- Refactoring values.yaml structure
- Some other small cleanup
Change-Id: Ib7c2451b46fab20935edb1c768ac56cc6353aa16
We are getting the following error [1] in Armada after [0]
was merged due to missing values in values.yaml
This patch set is meant to correct that
[0] https://review.gerrithub.io/#/c/398810/
[1] Error Messages
2018-02-08 07:02:54.481 1 ERROR armada grpc._channel._Rendezvous: <_Rendezvous of RPC that terminated with (StatusCode.UNKNOWN, render error in "deckhand/deployment.yaml": template: deckhand/deployment.yaml:36:62: executing "deckhand/deployment.yaml" at <include "helm-toolki...>: error calling include: template: deckhand/charts/helm-toolkit/utils/_hash.tpl:22:4: executing "helm-toolkit.utils.hash" at <include $wtf $contex...>: error calling include: template: deckhand/configmap-etc.yaml:37:20: executing "deckhand/configmap-etc.yaml" at <.Values.conf.deckhan...>: can't evaluate field api_endpoint in type interface {})>
Change-Id: Ie0aad8c2668924589fbad8865c973d86cb8779f7
Currently, openstackhelm-toolkit provides two utility methods:
.to_oslo_conf and .to_ini whose only difference at this time is
the ability to handle multistring in .to_oslo_conf as it is an
openstack concept that is not found in .ini files.
As logging.conf and paste.ini do not support multistring, they do
not need to be render by .to_oslo_conf, and while the code is not
incorrect, using .to_ini would be more appropriate.
Trivial fix
Change-Id: I20ae77842a3406ea64bf40d951adef2e519cbfcb
Bryan Strassner