1eda8f9f3e
In addition to being less confusing for devs, this lets us actually run
tempauth tests in swiftclient dsvm jobs.
The job definition (over in the swift repo) specifies test/sample.conf,
which does not exist in this repo. As a result, those tests would skip
with
SKIPPING FUNCTIONAL TESTS DUE TO NO CONFIG
Change-Id: I558dbf9a657d442e6e19468e543bbec855129eeb
33 lines
1.0 KiB
Plaintext
33 lines
1.0 KiB
Plaintext
[func_test]
|
|
# sample config
|
|
auth_host = 127.0.0.1
|
|
auth_port = 8080
|
|
auth_ssl = no
|
|
auth_prefix = /auth/
|
|
## sample config for Swift with Keystone v2 API
|
|
# For keystone v3 change auth_version to 3 and auth_prefix to /v3/
|
|
#auth_version = 2
|
|
#auth_host = localhost
|
|
#auth_port = 5000
|
|
#auth_ssl = no
|
|
#auth_prefix = /v2.0/
|
|
|
|
# Primary functional test account (needs admin access to the account).
|
|
# By default the tests use a swiftclient.client.Connection instance with user
|
|
# attribute set to 'account:username' based on the options 'account' and
|
|
# 'username' specified below. This can be overridden for auth systems that
|
|
# expect a different form of user attribute by setting the option
|
|
# 'account_username'.
|
|
# account_username = test_tester
|
|
account = test
|
|
username = tester
|
|
password = testing
|
|
|
|
# Another user is required for keystone v3 specific tests.
|
|
# Account must be in a non-default domain.
|
|
# (Suffix '4' is used to be consistent with swift functional test config).
|
|
#account4 = test4
|
|
#username4 = tester4
|
|
#password4 = testing4
|
|
#domain4 = test-domain
|