We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When the Appserver has a VPCZoneIdentifier configuration, like:
VPCZoneIdentifier
VPCZoneIdentifier: Fn::FindInMap: - LoadBalancerSubnets - Ref: AWS::Region - Subnets
This should be translated to the Elastigroup create argument compute.subnetIds.
compute.subnetIds
Currently, this does not happen, resulting in instances being potentially created in the wrong subnets.
A workaround is to explicitly specify the compute.subnetIds argument in the Elastigroup configuration:
Elastigroup: compute: subnetIds: Fn::FindInMap: - LoadBalancerSubnets - Ref: AWS::Region - Subnets
The text was updated successfully, but these errors were encountered:
lmineiro
Successfully merging a pull request may close this issue.
When the Appserver has a
VPCZoneIdentifier
configuration, like:This should be translated to the Elastigroup create argument
compute.subnetIds
.Currently, this does not happen, resulting in instances being potentially created in the wrong subnets.
A workaround is to explicitly specify the
compute.subnetIds
argument in the Elastigroup configuration:The text was updated successfully, but these errors were encountered: