Open mbloch1986 opened 6 years ago
Filter atm:
{
filters: [
{ name: 'tag:StackPrefix', values: [@descriptor.stack_prefix] },
{ name: 'tag:Component', values: [@descriptor.ec2.component] },
{ name: 'tag:Name', values: [@descriptor.ec2.name] }
]
}
Filter only by stackprefix and component
{
filters: [
{ name: 'tag:StackPrefix', values: [@descriptor.stack_prefix] },
{ name: 'tag:Component', values: [@descriptor.ec2.component] },
]
}
I'm turning this into a bug, since the consolidated ruby_aem_aws client isn't working due to this filter.
The ec2 instance filter
filter_for_descriptor
inabstract_component.rb
contains the stackprefix, component and ec2 instance name. Do we really need the ec2 instance name ? As it should be enough to filter a aem instance for stack_prefix and component?The reason is, after promoting the author standby as a author primary, the filter can't find the author-standby as a author primary instance, cause the name of the ec2 instance is still
aem author standby
.