Add missing external_id property to the import users job

[lbalmaceda]

Changes

The endpoint was missing the external_id property.

References

Resolves SDK-1625

Testing

• This change adds unit test coverage
• This change adds integration test coverage
• This change has been tested on the latest version of the platform/language or why not

Checklist

• I have read the Auth0 general contribution guidelines
• I have read the Auth0 Code of Conduct
• All existing and new tests complete without errors

[stevehobbsdev]

The criteria for this states:

When their values are not set, they should not be sent in the request. This will keep the SDK behaving as before, not introducing breaking changes.

Is there a way to test this scenario? All the tests I'm seeing validate the call where external_id is passed in but that doesn't seem enough to validate that the property is not included in the request.

[lbalmaceda]

@stevehobbsdev the unit tests on this SDK only test the arguments passed to the networking client when starting a request. For python requests library, when you pass None you tell you don't want to include that value.

• See here where the default of None is included as part of the call args. This is tested here
• See here the library docs where it mentions the behavior of None. Quoting below:

Note that any dictionary key whose value is None will not be added to the URL’s query string.

e.g.

>>> req = requests.Request('POST', 'http://google.com', data=dict(a=None, b=1))
>>> req.prepare().body
'b=1'

[stevehobbsdev]

Thanks for clarifying!