#11644 - Update migration guideline for request configuration rules#12008
Merged
allyoucanmap merged 1 commit intogeosolutions-it:masterfrom Mar 2, 2026
Merged
#11644 - Update migration guideline for request configuration rules#12008allyoucanmap merged 1 commit intogeosolutions-it:masterfrom
allyoucanmap merged 1 commit intogeosolutions-it:masterfrom
Conversation
9 tasks
allyoucanmap
approved these changes
Mar 2, 2026
Member
|
Successfully created backport PR for |
Contributor
|
@ElenaGallo please test this change on dev doc and let us know if we can backport, thanks |
tdipisa
pushed a commit
that referenced
this pull request
Mar 2, 2026
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
4 participants
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.
Description
This PR updates the migration guideline for request configuration rules for custom data directory update
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x", remove the others)
Issue
What is the current behavior?
What is the new behavior?
Migration guideline for custom data directory configuration of request configuration rules is updated
Breaking change
Does this PR introduce a breaking change? (check one with "x", remove the other)
Other useful information