auth0.Connection::options.fieldsMap state is flaky.

[davidmdm]

Describe what happened

When running pulumi up I create an auth0.Connection with samlp strategy. On this connection object I create the saml connection's options.fieldsMap.

This is a JSON string. However the state of the field does not necessarily the same as the input I provided. I suspect this is an auth0 issue where it parse and serializes the response back, such that the final output state is an equivalent json object string but not the same exact string. This leads to an incessant diff loop for that state.

Currently the only way to correct it, is to change your input options.fieldsMap string to match the output state.

A solution would be to internally save the state as an object and check for equality of the object, not of the string representation.

Sample program

new auth.Connection('example, {
  // ...
  options: {
    fieldsMap: `{"name": "name", "email": "[email protected]"}`
  }
})

Log output

No response

Affected Resource(s)

No response

Output of pulumi about

n/a

Additional context

No response

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

[iwahbe]

Hi @davidmdm. I'm sorry you're hitting this bug and I'm glad you found a workaround. Thanks for reporting this to us.

[davidmdm]

@iwahbe ,no worries! No need to be sorry.

I suspect its more an unfortunate result of the auth0 API returning a serialized version of the object that doesn't match the the string that we provide, and not really an issue on the pulumi side. However, we can probably fix this issue permanently here if we store the state as a JS object instead of a string.