Open chumanfoo opened 4 months ago
@chumanfoo Hi, thanks for reporting this. I created internal issue #479 to track this. For the time being, you should be able to provide the AMI of the image you want to use for the bigIpCustomImageId parameter. This should bypass the AMI lookup function.
I tried to set bigIpCustomImageId to the AMI ID ami-04cb0918d5b8102a9 (BIGIP-17.1.1-0.2.6 PAYG-Best Plus 200Mbps on us-west-1) and left bigIpImage empty but I got the same error.
I have tried to set version to 3.12 in "BigIp-Failover-Existing-Network-Example-Function-16PY5IQ9HJ9TK" template and uploaded template to s3 bucket and provided S3 URl in the root template and deployed the function stack created successfully but it is failing with custom resource.
@pedrorouremalta @chumanfoo @gmallsh Please check out the new release here: https://github.com/F5Networks/f5-aws-cloudformation-v2/releases/tag/v3.3.0.0
Describe the bug
This AWS CloudFormation Template doesn't build correctly
Expected behavior
This template should build environments based on input from deployer.
Current behavior
Template tries to deploy but doesn't due to it trying to create an AWS Lambda function that uses Python 3.7, which based on the message is no longer supported.
Possible solution
The templates use nested templates, and it looks like the issue lies in this nested template here: https://github.com/F5Networks/f5-aws-cloudformation-v2/blob/main/examples/modules/function/function.yaml Line: 232ff Role !Ref amilookupRole Runtime: python3.7 ...
Steps to reproduce
Screenshots
Context
Neither I nor our customers can use this template to build HA setups.
Your Environment
Standard multiple-AZ (same region) [or was it vice-versa?]