KC-1151: Add custom-field fallback for no file storage#1852
Open
amangalampalli-ks wants to merge 1 commit intoimprovement/config-file-upload-fallbackfrom
Open
Conversation
…rvice_config files
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
This update introduces a fallback mechanism to handle scenarios where file storage is unavailable.
Previously, the following attachments would fail to persist if file storage could not be accessed:
config.jsongenerated by:service-docker-setupslack-app-setupteams-app-setupservice_config.jsongenerated by:service-createWith this enhancement, when file storage is unavailable (e.g. restricted via Enforcement policies), these configuration files are stored as custom fields on the associated record instead of causing the operation to fail.