-
Notifications
You must be signed in to change notification settings - Fork 1
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
CDI-355: Favor Export Failure Warnings Over Errors #73
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
erikostien-pingidentity
commented
Jan 31, 2025
•
edited
Loading
edited
- Use option configuration environment variables for PF provider initialization
- Update HandleClientResponse to warn on client error and 403 forbidden responses.
- Implement common data extractions from PingOne SDK entity array. Handle 204 and 403 response status codes for various expected API behaviors.
- Fix error message formatting
- Implement common data extractions from PingOne SDK entity array for MFA.
- Implement common data extractions from PingOne SDK entity array for Protect
- Implement common data extractions from PingOne SDK entity array for SSO/Management
- Update dependencies and use tool directive instead of tools.go
- Use common reflect value extraction function
- Compact fields output in prints
- Pass Resource data by value to avoid nil dereference
- Add check to PF /Version API endpoint to verify valid PF client configuration
- Update WriteFiles() to warn on fail ExportAll() for a resource, and continue processing remaing resources for the service connector.
henryrecker-pingidentity
approved these changes
Jan 31, 2025
…le 204 and 403 response status codes for various expected API behaviors.
…ions back into ExportableResource type, compact fields output in prints
henryrecker-pingidentity
approved these changes
Feb 21, 2025
resolves #76 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.