This is an automated email from the ASF dual-hosted git repository.
lushiji pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/bookkeeper.git
The following commit(s) were added to refs/heads/master by this push:
new 222345f633 Proposing a new BP to delete cookie as part of decommission
API. (#4500)
222345f633 is described below
commit 222345f6339490a7d69992b97f71ce489fee1545
Author: Karthick Pitchaiah <[email protected]>
AuthorDate: Mon Sep 16 03:13:09 2024 +0530
Proposing a new BP to delete cookie as part of decommission API. (#4500)
Co-authored-by: Karthick Pitchaiah <[email protected]>
---
.../BP-68-add-cookie-delete-in-decommission-API.md | 28 ++++++++++++++++++++++
1 file changed, 28 insertions(+)
diff --git
a/site3/website/src/pages/bps/BP-68-add-cookie-delete-in-decommission-API.md
b/site3/website/src/pages/bps/BP-68-add-cookie-delete-in-decommission-API.md
new file mode 100644
index 0000000000..f4ae79b57a
--- /dev/null
+++ b/site3/website/src/pages/bps/BP-68-add-cookie-delete-in-decommission-API.md
@@ -0,0 +1,28 @@
+# BP-68: Delete cookie as part of bookkeeper decommission
+
+### Motivation
+
+_The current decommission process in Apache BookKeeper has two main
interfaces: the REST API and the command-line interface (CLI). However, there
is a discrepancy between these two methods, specifically in the handling of
cookie deletion. The CLI includes logic for deleting cookies associated with
decommissioned Bookies, while the REST API lacks this functionality. This BP
proposes enhancing the REST API to include cookie deletion logic, aligning it
with the behavior of the CLI._
+
+### Public Interfaces
+
+_api/v1/autorecovery/decommission_
+add the following in payload:
+
+```
+delete_cookie
+```
+
+default value is false, which means do not delete the Cookie.
+
+### Proposed Changes
+
+_Implement the same cookie deletion logic present in the CLI within the REST
API. This ensures that when a Bookie is decommissioned via the REST API, all
associated cookies are removed, preventing any stale or conflicting state._
+
+### Compatibility, Deprecation, and Migration Plan
+
+- The current behavior can be preserved as a default, with the cookie deletion
being an optional feature that can be toggled via request parameters.
+
+### Test Plan
+
+_Tests to make sure cookies are getting removed as part of the decommission_
