Fixed issue where HTTP headers set in a ClientOptions object passed to a client builder would not be set on a client instantiated by said builder. (Azure#22462)

* Fixed issue where HTTP headers set in a `ClientOptions` object passed to a client builder would not be set on a client instantiated by said builder.

* Updated CHANGELOG.

Author: vcolin7

sdk/tables/azure-data-tables/CHANGELOG.md

@@ -2,6 +2,8 @@
 
 ## 12.1.0-beta.1 (Unreleased)
 
+### Bug Fixes
+- Fixed issue where HTTP headers set in a `ClientOptions` object passed to a client builder would not be set on a client instantiated by said builder.
 
 ## 12.0.0 (2021-06-11)
 

sdk/tables/azure-data-tables/src/main/java/com/azure/data/tables/BuilderHelper.java

@@ -69,11 +69,13 @@ static HttpPipeline buildPipeline(
             CoreUtils.getApplicationId(clientOptions, logOptions), CLIENT_NAME, CLIENT_VERSION, configuration));
         policies.add(new RequestIdPolicy());
 
-        List<HttpHeader> httpHeaderList = new ArrayList<>();
-
         if (clientOptions != null) {
+            List<HttpHeader> httpHeaderList = new ArrayList<>();
+
             clientOptions.getHeaders().forEach(header ->
                 httpHeaderList.add(new HttpHeader(header.getName(), header.getValue())));
+
+            policies.add(new AddHeadersPolicy(new HttpHeaders(httpHeaderList)));
         }
 
         // Add per call additional policies.