Allow multiple overrides for delegate image version
pending feedback
O
Old lace Alligator
Customer: Dish
Current documented behaviour.
At max, there can only be two override entries corresponding to a combination of query params: accountIdentifier, orgIdentifier (if present), and projectIdentifier(if present): one with tags and one without tags. If the same combination of parameters is used with a different value of tags or delegateTag, then the existing entry will get updated.
Customer is requesting for the ability to have multiple override entries (not just two) as it becomes easier to manager multiple delegate groups with different versions.
Log In
O
Old lace Alligator
Abhishek Thamman
They have many delegate groups at account level (50+)
consider below delegate groups as example
(just using 3 and dummy version for example)
name, version
automation-non-prod, 1.3
automation-dev, 1.2
automation-prod, 1.1
currently we allow only two overrides per scope, one with tag and one without tag,
assume current overrides are
without tag, 1.1
automation-non-prod -> 1.3
customer wants to upgrade automation-non-prod to 1.4, so he sets tag override, automation-non-prod -> 1.4
now if customer adds another tag override for automation-dev
automation-dev -> 1.3
it will replace the tag override (automation-non-prod) as only one override is allowed with tag
The would like to define multiple tag overrides for auto upgrade, like
automation-non-prod -> 1.4
automation-dev -> 1.3
automation-prod -> 1.2
while keeping the default as 1.1
A
Abhishek Thamman
pending feedback
A
Abhishek Thamman
Hey Old lace Alligator, could you please elaborate the exact use case for requiring more overrides? Also, what kind of multiple overrides does the customer want to add?