NGX-838: Ignore Object Cache flush failures #64
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
…ures - Add to the WordPress cache flush task to prevent non-zero exit codes from failing the playbook execution. This change allows the playbook to continue running even if the cache flush command encounters minor, non-critical errors, ensuring that subsequent tasks are not unjustly impacted by this step's failure status. This adjustment is made to accommodate scenarios where the wp cache flush command might return a non-zero exit code due to known, benign issues that do not affect the overall success of the operation. It improves playbook resilience and execution consistency across environments with varying cache states.
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.
Ensure task continuity by ignoring non-critical command failures
This adjustment is made to accommodate scenarios where the wp cache flush command might return a non-zero exit code due to known, benign issues that do not affect the overall success of the operation. It improves playbook resilience and execution consistency across environments with varying cache states.