You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The assignment parameter tagvalues has type Array which consist of an object. This setup worked fine before converting to EPaC and the deployment of the policy and assignment also works fine with EPaC, however the EPaC plan always wants to update this assignment afterwards.
There is some kind of mismatch between the assignment parameters in the portal and the parameter in my code, when I have an Array with an object inside. The pictures show my parameter setup in the code and the portal, which shouldn't update. I have tried swapping positions of the keys in the object.
To Reproduce
Steps to reproduce the behavior:
To reproduce you need an assignment which has a parameter of type Array with an object inside. Then after deploying this assignment once, the plan always wants to update the assignment afterwards.
Expected behavior
I expected the assignment to deploy once and not end in a infinite loop of updates in the plan.
EPAC Version
I use the lastest EPaC version each time i run the deploy pipeline.
The text was updated successfully, but these errors were encountered:
@JCRL21 - I started experiencing this bug as well this week. Was going to open a ticket but thank you for doing so. I will figure out a path forward and try to get this resolved asap.
Describe the bug
The assignment parameter tagvalues has type Array which consist of an object. This setup worked fine before converting to EPaC and the deployment of the policy and assignment also works fine with EPaC, however the EPaC plan always wants to update this assignment afterwards.
There is some kind of mismatch between the assignment parameters in the portal and the parameter in my code, when I have an Array with an object inside. The pictures show my parameter setup in the code and the portal, which shouldn't update. I have tried swapping positions of the keys in the object.
To Reproduce
Steps to reproduce the behavior:
To reproduce you need an assignment which has a parameter of type Array with an object inside. Then after deploying this assignment once, the plan always wants to update the assignment afterwards.
Expected behavior
I expected the assignment to deploy once and not end in a infinite loop of updates in the plan.
EPAC Version
I use the lastest EPaC version each time i run the deploy pipeline.
The text was updated successfully, but these errors were encountered: