Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[2/4] Deprecate api_user field in auth0_email resource #392

Merged
merged 2 commits into from
Nov 7, 2022

Conversation

sergiught
Copy link
Contributor

🔧 Changes

We're deprecating the APIUser field because this field is no longer supported and trying to include it in the payload will result in a 400:

{
  "statusCode": 400,
  "error": "Bad Request",
  "message": "Payload validation error: 'None of the valid schemas were met' on property credentials (Credentials required to use the provider). Inner errors: [ Payload validation error: 'Additional properties not allowed: api_user' on property credentials ({description}). ].",
  "errorCode": "invalid_body"
}

📚 References

🔬 Testing

📝 Checklist

  • All new/changed/fixed functionality is covered by tests (or N/A)
  • I have added documentation for all new/changed functionality (or N/A)

@sergiught sergiught self-assigned this Nov 4, 2022
@sergiught sergiught force-pushed the feature/DXCDT-255-email-provider-settings-part-2 branch from 6436bfc to 3545440 Compare November 4, 2022 08:56
@sergiught sergiught marked this pull request as ready for review November 4, 2022 09:08
@sergiught sergiught requested a review from a team as a code owner November 4, 2022 09:08
Base automatically changed from feature/DXCDT-255-email-provider-settings-part-1 to main November 7, 2022 09:09
@sergiught sergiught merged commit 7dc9126 into main Nov 7, 2022
@sergiught sergiught deleted the feature/DXCDT-255-email-provider-settings-part-2 branch November 7, 2022 09:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants