"""
Copyright 2015 Rackspace

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
"""
import os

from tempest import config

CONF = config.CONF

# Use local tempest conf if one is available.
# This usually means we're running tests outside of devstack
if os.path.exists('./etc/dev_tempest.conf'):
    CONF.set_config_path('./etc/dev_tempest.conf')
Fix "invalid credentials" error running functional tests
Fix "invalid credentials" error running functional tests

This fixes the "invalid credentials" error that you will get
if you create a clean barbican environment and try to run the
functional tests.  It is actually a workaround for a change
to tempest (see https://review.openstack.org/#/c/147778/) which
causes a config object to be created BEFORE we get a chance to
set the path to OUR config.  When we set the path to our config
it is essentially ignored (since the config has already been
created) so the credentials in the tempest config aren't the
ones we set - hence the invalid credentials error.

This isn't an issue in devstack gate because our config
file isn't used.

This fix ensures that we will get our path update done before
tempest builds its config so our values will be used by tempest
when the real config object is created.

Change-Id: If8381aff3233934a0c733e12d64605c2dbdfe60c
