You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When this plugin (thx for it 😗 !) is used "as it" (just upload it) in TeamCity 2022.04.4, any build using this build feature fails with:
Unable to load region from any of the providers in the chain software.amazon.awssdk.regions.providers.DefaultAwsRegionProviderChain@62501254: [software.amazon.awssdk.regions.providers.SystemSettingsRegionProvider@6ee21c83: Unable to load region from system settings. Region must be specified either via environment variable (AWS_REGION) or system property (aws.region)., software.amazon.awssdk.regions.providers.AwsProfileRegionProvider@422105e7: No region provided in profile: default, software.amazon.awssdk.regions.providers.InstanceProfileRegionProvider@2e25e758: Unable to contact EC2 metadata service.]
Although the AWS region seems not really important for aws sts assume-role (The AccessKey/Role could be defined in another region that the given), it seems required for AWS API endpoint reachability.
Adding the AWS region as Java system property (TEAMCITY_SERVER_OPTS=-Daws.region=eu-west-3) solves the problem ; But adding some "server parameters/environment" for a plugin usage is perhaps not a nice way.
=> Adding a new Region: option (at the end of list) with us-east-1 as default could perhaps a good idea ?
Otherwise, supporting parameters coming from config/internal.properties would perhaps a better solution if this kind of new option would be considered as not relevant.
I can provide a PR, but I would like some feelings about the most sustainable way.
Thanks in advance
The text was updated successfully, but these errors were encountered:
Hi,
When this plugin (thx for it 😗 !) is used "as it" (just upload it) in TeamCity 2022.04.4, any build using this build feature fails with:
Although the AWS region seems not really important for
aws sts assume-role
(The AccessKey/Role could be defined in another region that the given), it seems required for AWS API endpoint reachability.Adding the AWS region as Java system property (
TEAMCITY_SERVER_OPTS=-Daws.region=eu-west-3
) solves the problem ; But adding some "server parameters/environment" for a plugin usage is perhaps not a nice way.=> Adding a new Region: option (at the end of list) with
us-east-1
as default could perhaps a good idea ?Otherwise, supporting parameters coming from
config/internal.properties
would perhaps a better solution if this kind of new option would be considered as not relevant.I can provide a PR, but I would like some feelings about the most sustainable way.
Thanks in advance
The text was updated successfully, but these errors were encountered: