Use known AMI in internal tests (#3620)
Moto's implementation of autoscaling:CreateLaunchConfiguration is a little too loose, allowing the ImageId parameter to be omitted and defaulting it to None, which results in dozens of deprecation warnings: `PendingDeprecationWarning: Could not find AMI with image-id:ami-123456, in the near future this will cause an error.` This commit refactors calls to CreateLaunchConfiguration to explicitly pass in a known AMI ImageId in order to avoid these warnings. The integrity of the tests is unaffected by this change.
This commit is contained in:
parent
b9b793f421
commit
9e1fcac9d4
6 changed files with 162 additions and 47 deletions
|
|
@ -1,6 +1,7 @@
|
|||
import boto3
|
||||
from moto import mock_cloudformation, mock_ecs, mock_autoscaling, mock_s3
|
||||
import json
|
||||
from tests import EXAMPLE_AMI_ID
|
||||
|
||||
depends_on_template_list = {
|
||||
"AWSTemplateFormatVersion": "2010-09-09",
|
||||
|
|
@ -23,7 +24,11 @@ depends_on_template_list = {
|
|||
},
|
||||
"LaunchConfig": {
|
||||
"Type": "AWS::AutoScaling::LaunchConfiguration",
|
||||
"Properties": {"LaunchConfigurationName": "test-launch-config",},
|
||||
"Properties": {
|
||||
"LaunchConfigurationName": "test-launch-config",
|
||||
"ImageId": EXAMPLE_AMI_ID,
|
||||
"InstanceType": "t2.medium",
|
||||
},
|
||||
},
|
||||
},
|
||||
}
|
||||
|
|
@ -45,7 +50,11 @@ depends_on_template_string = {
|
|||
},
|
||||
"LaunchConfig": {
|
||||
"Type": "AWS::AutoScaling::LaunchConfiguration",
|
||||
"Properties": {"LaunchConfigurationName": "test-launch-config",},
|
||||
"Properties": {
|
||||
"LaunchConfigurationName": "test-launch-config",
|
||||
"ImageId": EXAMPLE_AMI_ID,
|
||||
"InstanceType": "t2.medium",
|
||||
},
|
||||
},
|
||||
},
|
||||
}
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue