On 26/06/18 06:06, Lars Kellogg-Stedman wrote:
Is there a way to refer to the `--templates` directory when writing
service templates? Existing service templates can use relative paths,
as in:
resources:
ContainersCommon:
type: ./containers-common.yaml
But if I'm write a local service template (which I often do during
testing/development), I would need to use the full path to the
corresponding file:
ContainersCommon:
type:
/usr/share/openstack-tripleo-heat-templates/docker/services/containers-common.yaml
But that breaks if I use another template directory via the
--templates option to the `openstack overcloud deploy` command. Is
there a way to refer to "the current templates directory"?
You're only choice would be to either use an absolute path, or develop
your local service template inside a checkout of tripleo-heat-templates,
which is how other new services are developed.
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
