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
The fusionauth api seems to return lists in a consistent order about 80% of the time. For example an API key gets permissions on endpoints in a list. What order they are is irrelevant to fusionauth, but this provider demands they be in the same order or it considers it needing update.
Pulumi example output below may make it more clear. If you look at the first element /api/email/send came first from fusinonauth API, and now /api/application comes first. However if you dig in you'll see that /api/email/send is now seen in # 2, and has the same perms (true/true/true) as before.
Since ordering is not important for some of these APIs the terraform should be more logical in comparing them. In this case doing a sort on endpoint of the old / new results would do the trick and eliminate false positives.
This bug throws off any sanity checking or the ability to run in cicd in check mode because we'll get false positives all the time.
The fusionauth api seems to return lists in a consistent order about 80% of the time. For example an API key gets permissions on endpoints in a list. What order they are is irrelevant to fusionauth, but this provider demands they be in the same order or it considers it needing update.
Pulumi example output below may make it more clear. If you look at the first element /api/email/send came first from fusinonauth API, and now /api/application comes first. However if you dig in you'll see that /api/email/send is now seen in # 2, and has the same perms (true/true/true) as before.
Since ordering is not important for some of these APIs the terraform should be more logical in comparing them. In this case doing a sort on
endpoint
of the old / new results would do the trick and eliminate false positives.This bug throws off any sanity checking or the ability to run in cicd in check mode because we'll get false positives all the time.
The text was updated successfully, but these errors were encountered: