HADOOP-12520. Use XInclude in hadoop-azure test configuration to isolate Azure Storage account keys for service integration tests. Contributed by Chris Nauroth.

This commit is contained in:
cnauroth 2015-10-27 22:48:56 -07:00
parent eca51b13af
commit 73822de7c3
4 changed files with 32 additions and 13 deletions

1
.gitignore vendored
View File

@ -24,4 +24,5 @@ hadoop-yarn-project/hadoop-yarn/hadoop-yarn-registry/src/main/tla/yarnregistry.t
yarnregistry.pdf yarnregistry.pdf
hadoop-tools/hadoop-aws/src/test/resources/auth-keys.xml hadoop-tools/hadoop-aws/src/test/resources/auth-keys.xml
hadoop-tools/hadoop-aws/src/test/resources/contract-test-options.xml hadoop-tools/hadoop-aws/src/test/resources/contract-test-options.xml
hadoop-tools/hadoop-azure/src/test/resources/azure-auth-keys.xml
patchprocess/ patchprocess/

View File

@ -916,6 +916,9 @@ Release 2.8.0 - UNRELEASED
HADOOP-12472. Make GenericTestUtils.assertExceptionContains robust. HADOOP-12472. Make GenericTestUtils.assertExceptionContains robust.
(Steve Loughran via jing9) (Steve Loughran via jing9)
HADOOP-12520. Use XInclude in hadoop-azure test configuration to isolate
Azure Storage account keys for service integration tests. (cnauroth)
OPTIMIZATIONS OPTIMIZATIONS
HADOOP-11785. Reduce the number of listStatus operation in distcp HADOOP-11785. Reduce the number of listStatus operation in distcp

View File

@ -226,18 +226,25 @@ following failure message:
To resolve this, restart the Azure Emulator. Ensure it v3.2 or later. To resolve this, restart the Azure Emulator. Ensure it v3.2 or later.
It's also possible to run tests against a live Azure Storage account by adding It's also possible to run tests against a live Azure Storage account by saving a
credentials to `src/test/resources/azure-test.xml` and setting file to `src/test/resources/azure-auth-keys.xml` and setting
`fs.azure.test.account.name` to the name of the storage account. `fs.azure.test.account.name` to the name of the storage account.
For example: For example:
<property> <?xml version="1.0"?>
<name>fs.azure.account.key.youraccount.blob.core.windows.net</name> <?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
<value>YOUR ACCESS KEY</value> <configuration>
</property> <property>
<name>fs.azure.account.key.youraccount.blob.core.windows.net</name>
<value>YOUR ACCESS KEY</value>
</property>
<property> <property>
<name>fs.azure.test.account.name</name> <name>fs.azure.test.account.name</name>
<value>youraccount</value> <value>youraccount</value>
</property> </property>
</configuration>
DO NOT ADD azure-auth-keys.xml TO REVISION CONTROL. The keys to your Azure
Storage account are a secret and must not be shared.

View File

@ -15,7 +15,7 @@
<?xml-stylesheet type="text/xsl" href="configuration.xsl"?> <?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
<configuration xmlns:xi="http://www.w3.org/2001/XInclude"> <configuration xmlns:xi="http://www.w3.org/2001/XInclude">
<!-- For tests against live azure, provide the following account information --> <!-- For tests against live azure, provide the following account information -->
<!-- <!--
<property> <property>
@ -26,8 +26,16 @@
<name>fs.azure.account.key.{ACCOUNTNAME}.blob.core.windows.net</name> <name>fs.azure.account.key.{ACCOUNTNAME}.blob.core.windows.net</name>
<value>{ACCOUNTKEY}</value> <value>{ACCOUNTKEY}</value>
</property> </property>
--> -->
<!-- Save the above configuration properties in a separate file named -->
<!-- azure-auth-keys.xml in the same directory as this file. -->
<!-- DO NOT ADD azure-auth-keys.xml TO REVISION CONTROL. The keys to your -->
<!-- Azure Storage account are a secret and must not be shared. -->
<include xmlns="http://www.w3.org/2001/XInclude" href="azure-auth-keys.xml">
<fallback />
</include>
<!-- For tests against azure-emulator --> <!-- For tests against azure-emulator -->
<!-- <!--
<property> <property>