Add sigv4aRegionSet to Client Builder for Multi-Auth Services Supporting Sigv4a

[joviegas]

Motivation and Context

• Clients with Sigv4a Multi auth should provide API on client to set the region set
• The Sigv4aRegion Set build takes highest Precedence

Note : Even though we have RegionScope this has been not used because SRA introduced RegionSet so using the latest representation class for
Region set

Modifications

Interface

• Code gen changes that will generate API on Client Builder as below

    /**
     * Sets the {@link RegionSet} to be used for operations using Sigv4a signing requests. This is optional; if not
     * provided, the following precedence is used:
     * <ol>
     * <li>{@link software.amazon.awssdk.core.SdkSystemSetting#AWS_SIGV4A_SIGNING_REGION_SET}.</li>
     * <li>as <code>sigv4a_signing_region_set</code> in the configuration file.</li>
     * <li>The region configured for the client.</li>
     * </ol>
     */
    default B sigv4aRegionSet(RegionSet sigv4aRegionSet) {
        throw new UnsupportedOperationException();
    }

Default Builder

abstract class DefaultMultiauthBaseClientBuilder<B extends MultiauthBaseClientBuilder<B, C>, C> extends
        AwsDefaultClientBuilder<B, C> {
// ...code 
    public B sigv4aRegionSet(RegionSet sigv4aRegionSet) {
        clientConfiguration.option(AwsClientOption.AWS_SIGV4A_SIGNING_REGION_SET,
                sigv4aRegionSet == null ? Collections.emptySet() : sigv4aRegionSet.asSet());
        return thisBuilder();
    }

• Also added change to set ClientOption when builder is built

Testing

• Junit for codegen
• Test case to verify precedence of sigv4aRegionSet on Builder

Screenshots (if appropriate)

License

• I confirm that this pull request can be released under the Apache 2 license

[zoewangg]

Should this just be regionSet? I guess we can finalize it in API surface area review

[joviegas]

Sure , I have this discussion during Surface API review

[sonarqubecloud]

Quality Gate passed

Issues
3 New issues
0 Accepted issues

Measures
0 Security Hotspots
96.2% Coverage on New Code
1.3% Duplication on New Code

See analysis details on SonarQube Cloud