-
Task
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
-
Not defined
Context:
Since in Zeebe, the backupID has to be integer we ** decided to align all other products to this and change the backupID from string to integer.
AT:
- backupID in all hot backup API endpoints is an integer and not a string
- this change is noted in our docs
Testing Notes:
Use the hot backup API and ensure the backupID is both taken and returned as integer for all hot backup endpoints. Ensure API no longer supports a string backupID. Ensure API does not accept a negative backupID.
This is the controller panel for Smart Panels app
[OPT-6764] Make BackupID integer
Status | Original: Triage [ 10612 ] | New: Ready [ 10005 ] |
Description |
Original:
*Context:*
Since in Zeebe, the backupID has to be integer we ** decided to align all other products to this and change the backupID from string to integer. *AT:* * backupID in all hot backup API endpoints is an integer and not a string *Testing Notes:* Use the hot backup API and ensure the backupID is both taken and returned as integer for all hot backup endpoints. |
New:
*Context:*
Since in Zeebe, the backupID has to be integer we ** decided to align all other products to this and change the backupID from string to integer. *AT:* * backupID in all hot backup API endpoints is an integer and not a string * this change is noted in our docs *Testing Notes:* Use the hot backup API and ensure the backupID is both taken and returned as integer for all hot backup endpoints. |
Component/s | New: documentation [ 13751 ] |
Description |
Original:
*Context:*
Since in Zeebe, the backupID has to be integer we ** decided to align all other products to this and change the backupID from string to integer. *AT:* * backupID in all hot backup API endpoints is an integer and not a string * this change is noted in our docs *Testing Notes:* Use the hot backup API and ensure the backupID is both taken and returned as integer for all hot backup endpoints. |
New:
*Context:*
Since in Zeebe, the backupID has to be integer we ** decided to align all other products to this and change the backupID from string to integer. *AT:* * backupID in all hot backup API endpoints is an integer and not a string * this change is noted in our docs *Testing Notes:* Use the hot backup API and ensure the backupID is both taken and returned as integer for all hot backup endpoints. Ensure API no longer supports a string backupID. |
Description |
Original:
*Context:*
Since in Zeebe, the backupID has to be integer we ** decided to align all other products to this and change the backupID from string to integer. *AT:* * backupID in all hot backup API endpoints is an integer and not a string * this change is noted in our docs *Testing Notes:* Use the hot backup API and ensure the backupID is both taken and returned as integer for all hot backup endpoints. Ensure API no longer supports a string backupID. |
New:
*Context:*
Since in Zeebe, the backupID has to be integer we ** decided to align all other products to this and change the backupID from string to integer. Internally, since ES requires strings for snapshot names we can still treat the backupID as a string. *AT:* * backupID in all hot backup API endpoints is an integer and not a string * this change is noted in our docs *Testing Notes:* Use the hot backup API and ensure the backupID is both taken and returned as integer for all hot backup endpoints. Ensure API no longer supports a string backupID. |
Description |
Original:
*Context:*
Since in Zeebe, the backupID has to be integer we ** decided to align all other products to this and change the backupID from string to integer. Internally, since ES requires strings for snapshot names we can still treat the backupID as a string. *AT:* * backupID in all hot backup API endpoints is an integer and not a string * this change is noted in our docs *Testing Notes:* Use the hot backup API and ensure the backupID is both taken and returned as integer for all hot backup endpoints. Ensure API no longer supports a string backupID. |
New:
*Context:*
Since in Zeebe, the backupID has to be integer we ** decided to align all other products to this and change the backupID from string to integer. Internally, since ES requires strings for snapshot names we can still treat the backupID as a string if needed. *AT:* * backupID in all hot backup API endpoints is an integer and not a string * this change is noted in our docs *Testing Notes:* Use the hot backup API and ensure the backupID is both taken and returned as integer for all hot backup endpoints. Ensure API no longer supports a string backupID. |
Status | Original: Ready [ 10005 ] | New: In Development [ 10312 ] |
Description |
Original:
*Context:*
Since in Zeebe, the backupID has to be integer we ** decided to align all other products to this and change the backupID from string to integer. Internally, since ES requires strings for snapshot names we can still treat the backupID as a string if needed. *AT:* * backupID in all hot backup API endpoints is an integer and not a string * this change is noted in our docs *Testing Notes:* Use the hot backup API and ensure the backupID is both taken and returned as integer for all hot backup endpoints. Ensure API no longer supports a string backupID. |
New:
*Context:*
Since in Zeebe, the backupID has to be integer we ** decided to align all other products to this and change the backupID from string to integer. *AT:* * backupID in all hot backup API endpoints is an integer and not a string * this change is noted in our docs *Testing Notes:* Use the hot backup API and ensure the backupID is both taken and returned as integer for all hot backup endpoints. Ensure API no longer supports a string backupID. |
Assignee | Original: Helene Waechtler [ helene.waechtler ] | New: Giuliano Rodrigues Lima [ giuliano.rodrigues-lima ] |
Status | Original: In Development [ 10312 ] | New: In Review [ 10212 ] |
Assignee | Original: Giuliano Rodrigues Lima [ giuliano.rodrigues-lima ] | New: Helene Waechtler [ helene.waechtler ] |
Status | Original: In Review [ 10212 ] | New: Rework [ 11413 ] |