Timeout of CreateOrUpdateStackTask defaults to 15 minutes when OIDC is used

[zafodB]

Describe the bug

When using OIDC to authenticate the CloudFormationCreateOrUpdateStack task, the default timeout for stack creation drops to 15 minutes (instead of 60).

To reproduce

1. Configure an AWS Service connection in Azure DevOps to use OIDC
2. Run a pipeline with CloudFormationCreateOrUpdateStack task. Use a stack that takes a long time to deploy (e.g. MSK Clusters, RDS databases, DMS instances, etc., anything that takes more than 15 minutes to deploy).
3. The stack is created and begins to deploy. This takes a long time, as expected (due to the resource, which takes a long time to deploy).
4. After ~15 minutes, the task reports that the stack failed to reach completion status, throws and error and halts the pipeline.
5. The CloudFormation stack continues to deploy without issues, and eventually completes the deployment successfully (albeit after 30-40+ minutes).

Expected behavior

As per the documentation, a default timeout of 60 minutes should be used to wait until stack finishes deployment, before the pipeline task throws an error. This is the case if IAM Credentials are used in the Service Connection.

Screenshots

Not applicable

Your Environment

• On-prem or cloud based: Cloud Based Azure DevOps service
• Azure DevOps version: Version Dev19.M243.1 (AzureDevOps_M243_20240823.6)
• AWS Toolkit for Azure DevOps version: 1.15.0

Additional context

Related to #521

[shillam]

A workaround for the above is to set an Azure DevOps variable 'aws.rolecredential.maxduration' with a custom value in seconds, for a 1 hour session set it to 3600.

This is defined here:

aws-toolkit-azure-devops/src/lib/awsConnectionParameters.ts

Line 38 in 0199d6b

export const roleCredentialMaxDurationVariableName = 'aws.rolecredential.maxduration'