Profiles with multiple tags not working as expected

[pramodb]

Hi,

We are using Ec2Box for handling access to our AWS infrastructure and Profile seem to be behaving incorrectly. E.g.

Instances we have in EC2 are :

1. instance-1 -> Tag - {Role : DB}
2. instance-2 -> Tag - {Role : APP}

We created a Profile in Ec2Box with the following tag entry:
{Role=DB,Role=APP}

The expectation was the user who we assign the above profile will get access to both instances. However we can see that viewSystems screen shows only one instance i.e. instance-2.

When we swap the Tags in the profile configuration to {Role=APP,Role=DB}, the user starts seeing instance-1 and not instance-2.

Also, Creating multiple profiles and assigning them to user seems to be doing an AND of the tags to filter instances instead of an OR. E.g.

Instances in EC2 are :

1. instance-1 -> Tag - {Tag1 : Value1}
2. instance-2 -> Tag - {Tag2 : Value2}

Profiles we created :

1. Profile1 - {Tag1 : Value1}
2. Profile2 - {Tag2 : Value2}

When we assign both the profiles to the user the viewSystems screen shows an empty list of instances, however we expected that by assigning multiple profiles we should get a union of instances returned by each profile filter.

Thanks,
Pramod.

[skavanagh]

What version are you using?? I think this may be fixed in the latest with everything OR'd (see: #21) but I've had a bit of trouble on what I was expecting to get back from the AWS calls in the past, so it may still be an issue

[pramodb]

Hi Sean,

We were using version 0.26.02. I can see that we have newer version released on Jan 30th. Will give that a try and check if the above issues are resolved.

Thanks,
Pramod.