[bugfix] Flow Framework Bugfixes

[tkykenmt]

Overview

• Version: v2.16.0
• Category: bugfix
• Repositories: flow
• PRs: 3

Pull Requests

PR	Title	Category	Repository
#805	Handle Not Found deprovision exceptions as successful deleti	bugfix	flow
#809	Wrap CreateIndexRequest mappings in _doc key as required	bugfix	flow
#811	Have FlowFrameworkException status recognized by ExceptionsH	bugfix	flow

Tasks

• Investigate PRs
• Create release report: docs/releases/v2.16.0/features/flow/flow-framework-bugfixes.md
• Update feature report: docs/features/flow/flow-framework-bugfixes.md

[tkykenmt]

Investigation Complete

Reports Created

• Release report: docs/releases/v2.16.0/features/flow-framework/flow-framework-bugfixes.md
• Feature report: docs/features/flow-framework/flow-framework.md (updated)

Summary

Three bug fixes for the Flow Framework plugin in v2.16.0 that improve error handling during deprovisioning and index creation operations.

Key Changes in v2.16.0

• NOT_FOUND Exception Handling: DeleteModelStep and DeleteAgentStep now treat NOT_FOUND exceptions as successful deletions, allowing deprovisioning to complete when resources were manually deleted
• Index Mapping Fix: FlowFrameworkIndicesHandler now correctly wraps index mappings in the required _doc key per CreateIndexRequest javadoc
• Exception Status Code Fix: FlowFrameworkException now properly extends OpenSearchException and overrides status() so ExceptionsHelper returns correct HTTP status codes instead of 500

Resources Used

• PR: #805 - Handle Not Found deprovision exceptions
• PR: #809 - Wrap CreateIndexRequest mappings in _doc key
• PR: #811 - FlowFrameworkException status recognition
• Issue: #803 - DeleteModelStep/DeleteAgentStep NOT_FOUND handling
• Issue: #798 - System index mapping _doc wrapper
• Issue: #810 - Deprovision 500 error on workflow ID not found