feat(ledger): expose rebuild-schedule on LedgerClient

robosystems_client/api/extensions_robo_ledger/op_rebuild_schedule.py

@@ -0,0 +1,330 @@
+from http import HTTPStatus
+from typing import Any
+from urllib.parse import quote
+
+import httpx
+
+from ... import errors
+from ...client import AuthenticatedClient, Client
+from ...models.error_response import ErrorResponse
+from ...models.operation_envelope_schedule_created_response import (
+  OperationEnvelopeScheduleCreatedResponse,
+)
+from ...models.rebuild_schedule_request import RebuildScheduleRequest
+from ...types import UNSET, Response, Unset
+
+
+def _get_kwargs(
+  graph_id: str,
+  *,
+  body: RebuildScheduleRequest,
+  idempotency_key: None | str | Unset = UNSET,
+) -> dict[str, Any]:
+  headers: dict[str, Any] = {}
+  if not isinstance(idempotency_key, Unset):
+    headers["Idempotency-Key"] = idempotency_key
+
+  _kwargs: dict[str, Any] = {
+    "method": "post",
+    "url": "/extensions/roboledger/{graph_id}/operations/rebuild-schedule".format(
+      graph_id=quote(str(graph_id), safe=""),
+    ),
+  }
+
+  _kwargs["json"] = body.to_dict()
+
+  headers["Content-Type"] = "application/json"
+
+  _kwargs["headers"] = headers
+  return _kwargs
+
+
+def _parse_response(
+  *, client: AuthenticatedClient | Client, response: httpx.Response
+) -> ErrorResponse | OperationEnvelopeScheduleCreatedResponse | None:
+  if response.status_code == 200:
+    response_200 = OperationEnvelopeScheduleCreatedResponse.from_dict(response.json())
+
+    return response_200
+
+  if response.status_code == 400:
+    response_400 = ErrorResponse.from_dict(response.json())
+
+    return response_400
+
+  if response.status_code == 401:
+    response_401 = ErrorResponse.from_dict(response.json())
+
+    return response_401
+
+  if response.status_code == 403:
+    response_403 = ErrorResponse.from_dict(response.json())
+
+    return response_403
+
+  if response.status_code == 404:
+    response_404 = ErrorResponse.from_dict(response.json())
+
+    return response_404
+
+  if response.status_code == 409:
+    response_409 = ErrorResponse.from_dict(response.json())
+
+    return response_409
+
+  if response.status_code == 422:
+    response_422 = ErrorResponse.from_dict(response.json())
+
+    return response_422
+
+  if response.status_code == 429:
+    response_429 = ErrorResponse.from_dict(response.json())
+
+    return response_429
+
+  if response.status_code == 500:
+    response_500 = ErrorResponse.from_dict(response.json())
+
+    return response_500
+
+  if client.raise_on_unexpected_status:
+    raise errors.UnexpectedStatus(response.status_code, response.content)
+  else:
+    return None
+
+
+def _build_response(
+  *, client: AuthenticatedClient | Client, response: httpx.Response
+) -> Response[ErrorResponse | OperationEnvelopeScheduleCreatedResponse]:
+  return Response(
+    status_code=HTTPStatus(response.status_code),
+    content=response.content,
+    headers=response.headers,
+    parsed=_parse_response(client=client, response=response),
+  )
+
+
+def sync_detailed(
+  graph_id: str,
+  *,
+  client: AuthenticatedClient,
+  body: RebuildScheduleRequest,
+  idempotency_key: None | str | Unset = UNSET,
+) -> Response[ErrorResponse | OperationEnvelopeScheduleCreatedResponse]:
+  """Rebuild Schedule In Place
+
+   Re-run the schedule generator in place on an existing schedule. Atomic alternative to delete-then-
+  recreate (which orphans pending obligations): preserves the structure id + element associations +
+  taxonomy, voids the old pending obligation chain, deletes the old facts and SumEquals rules, and
+  regenerates fresh forward facts + a fresh obligation chain from the schedule's stored definition
+  (entry_template / schedule_metadata / monthly_amount / period bounds). The historical-vs-in-scope
+  split is re-derived from the CURRENT fiscal calendar closed_through. Use this to pick up a fixed
+  generator (e.g. the roll-forward direction fix) without orphaning obligations.
+
+  **Idempotency**: supply an `Idempotency-Key` header to make safe retries; replays within 24 hours
+  return the same envelope. Reusing the key with a different body returns HTTP 409 Conflict.
+
+  Args:
+      graph_id (str):
+      idempotency_key (None | str | Unset):
+      body (RebuildScheduleRequest): Re-run the schedule generator in place on an existing
+          schedule.
+
+          Atomic alternative to delete-then-recreate: the structure id and its
+          element associations are preserved, the old pending obligation chain
+          is voided, the old facts + rules are deleted, and a fresh set of
+          forward facts + a fresh obligation chain are regenerated from the
+          schedule's stored definition (entry_template / schedule_metadata /
+          monthly_amount / period bounds on the Structure's metadata).
+
+          The historical-vs-in-scope split is re-derived from the CURRENT fiscal
+          calendar `closed_through`, so a rebuild re-scopes the schedule to
+          today's close state. Use this to pick up a fixed generator (e.g. the
+          roll-forward direction fix) without orphaning obligations.
+
+  Raises:
+      errors.UnexpectedStatus: If the server returns an undocumented status code and Client.raise_on_unexpected_status is True.
+      httpx.TimeoutException: If the request takes longer than Client.timeout.
+
+  Returns:
+      Response[ErrorResponse | OperationEnvelopeScheduleCreatedResponse]
+  """
+
+  kwargs = _get_kwargs(
+    graph_id=graph_id,
+    body=body,
+    idempotency_key=idempotency_key,
+  )
+
+  response = client.get_httpx_client().request(
+    **kwargs,
+  )
+
+  return _build_response(client=client, response=response)
+
+
+def sync(
+  graph_id: str,
+  *,
+  client: AuthenticatedClient,
+  body: RebuildScheduleRequest,
+  idempotency_key: None | str | Unset = UNSET,
+) -> ErrorResponse | OperationEnvelopeScheduleCreatedResponse | None:
+  """Rebuild Schedule In Place
+
+   Re-run the schedule generator in place on an existing schedule. Atomic alternative to delete-then-
+  recreate (which orphans pending obligations): preserves the structure id + element associations +
+  taxonomy, voids the old pending obligation chain, deletes the old facts and SumEquals rules, and
+  regenerates fresh forward facts + a fresh obligation chain from the schedule's stored definition
+  (entry_template / schedule_metadata / monthly_amount / period bounds). The historical-vs-in-scope
+  split is re-derived from the CURRENT fiscal calendar closed_through. Use this to pick up a fixed
+  generator (e.g. the roll-forward direction fix) without orphaning obligations.
+
+  **Idempotency**: supply an `Idempotency-Key` header to make safe retries; replays within 24 hours
+  return the same envelope. Reusing the key with a different body returns HTTP 409 Conflict.
+
+  Args:
+      graph_id (str):
+      idempotency_key (None | str | Unset):
+      body (RebuildScheduleRequest): Re-run the schedule generator in place on an existing
+          schedule.
+
+          Atomic alternative to delete-then-recreate: the structure id and its
+          element associations are preserved, the old pending obligation chain
+          is voided, the old facts + rules are deleted, and a fresh set of
+          forward facts + a fresh obligation chain are regenerated from the
+          schedule's stored definition (entry_template / schedule_metadata /
+          monthly_amount / period bounds on the Structure's metadata).
+
+          The historical-vs-in-scope split is re-derived from the CURRENT fiscal
+          calendar `closed_through`, so a rebuild re-scopes the schedule to
+          today's close state. Use this to pick up a fixed generator (e.g. the
+          roll-forward direction fix) without orphaning obligations.
+
+  Raises:
+      errors.UnexpectedStatus: If the server returns an undocumented status code and Client.raise_on_unexpected_status is True.
+      httpx.TimeoutException: If the request takes longer than Client.timeout.
+
+  Returns:
+      ErrorResponse | OperationEnvelopeScheduleCreatedResponse
+  """
+
+  return sync_detailed(
+    graph_id=graph_id,
+    client=client,
+    body=body,
+    idempotency_key=idempotency_key,
+  ).parsed
+
+
+async def asyncio_detailed(
+  graph_id: str,
+  *,
+  client: AuthenticatedClient,
+  body: RebuildScheduleRequest,
+  idempotency_key: None | str | Unset = UNSET,
+) -> Response[ErrorResponse | OperationEnvelopeScheduleCreatedResponse]:
+  """Rebuild Schedule In Place
+
+   Re-run the schedule generator in place on an existing schedule. Atomic alternative to delete-then-
+  recreate (which orphans pending obligations): preserves the structure id + element associations +
+  taxonomy, voids the old pending obligation chain, deletes the old facts and SumEquals rules, and
+  regenerates fresh forward facts + a fresh obligation chain from the schedule's stored definition
+  (entry_template / schedule_metadata / monthly_amount / period bounds). The historical-vs-in-scope
+  split is re-derived from the CURRENT fiscal calendar closed_through. Use this to pick up a fixed
+  generator (e.g. the roll-forward direction fix) without orphaning obligations.
+
+  **Idempotency**: supply an `Idempotency-Key` header to make safe retries; replays within 24 hours
+  return the same envelope. Reusing the key with a different body returns HTTP 409 Conflict.
+
+  Args:
+      graph_id (str):
+      idempotency_key (None | str | Unset):
+      body (RebuildScheduleRequest): Re-run the schedule generator in place on an existing
+          schedule.
+
+          Atomic alternative to delete-then-recreate: the structure id and its
+          element associations are preserved, the old pending obligation chain
+          is voided, the old facts + rules are deleted, and a fresh set of
+          forward facts + a fresh obligation chain are regenerated from the
+          schedule's stored definition (entry_template / schedule_metadata /
+          monthly_amount / period bounds on the Structure's metadata).
+
+          The historical-vs-in-scope split is re-derived from the CURRENT fiscal
+          calendar `closed_through`, so a rebuild re-scopes the schedule to
+          today's close state. Use this to pick up a fixed generator (e.g. the
+          roll-forward direction fix) without orphaning obligations.
+
+  Raises:
+      errors.UnexpectedStatus: If the server returns an undocumented status code and Client.raise_on_unexpected_status is True.
+      httpx.TimeoutException: If the request takes longer than Client.timeout.
+
+  Returns:
+      Response[ErrorResponse | OperationEnvelopeScheduleCreatedResponse]
+  """
+
+  kwargs = _get_kwargs(
+    graph_id=graph_id,
+    body=body,
+    idempotency_key=idempotency_key,
+  )
+
+  response = await client.get_async_httpx_client().request(**kwargs)
+
+  return _build_response(client=client, response=response)
+
+
+async def asyncio(
+  graph_id: str,
+  *,
+  client: AuthenticatedClient,
+  body: RebuildScheduleRequest,
+  idempotency_key: None | str | Unset = UNSET,
+) -> ErrorResponse | OperationEnvelopeScheduleCreatedResponse | None:
+  """Rebuild Schedule In Place
+
+   Re-run the schedule generator in place on an existing schedule. Atomic alternative to delete-then-
+  recreate (which orphans pending obligations): preserves the structure id + element associations +
+  taxonomy, voids the old pending obligation chain, deletes the old facts and SumEquals rules, and
+  regenerates fresh forward facts + a fresh obligation chain from the schedule's stored definition
+  (entry_template / schedule_metadata / monthly_amount / period bounds). The historical-vs-in-scope
+  split is re-derived from the CURRENT fiscal calendar closed_through. Use this to pick up a fixed
+  generator (e.g. the roll-forward direction fix) without orphaning obligations.
+
+  **Idempotency**: supply an `Idempotency-Key` header to make safe retries; replays within 24 hours
+  return the same envelope. Reusing the key with a different body returns HTTP 409 Conflict.
+
+  Args:
+      graph_id (str):
+      idempotency_key (None | str | Unset):
+      body (RebuildScheduleRequest): Re-run the schedule generator in place on an existing
+          schedule.
+
+          Atomic alternative to delete-then-recreate: the structure id and its
+          element associations are preserved, the old pending obligation chain
+          is voided, the old facts + rules are deleted, and a fresh set of
+          forward facts + a fresh obligation chain are regenerated from the
+          schedule's stored definition (entry_template / schedule_metadata /
+          monthly_amount / period bounds on the Structure's metadata).
+
+          The historical-vs-in-scope split is re-derived from the CURRENT fiscal
+          calendar `closed_through`, so a rebuild re-scopes the schedule to
+          today's close state. Use this to pick up a fixed generator (e.g. the
+          roll-forward direction fix) without orphaning obligations.
+
+  Raises:
+      errors.UnexpectedStatus: If the server returns an undocumented status code and Client.raise_on_unexpected_status is True.
+      httpx.TimeoutException: If the request takes longer than Client.timeout.
+
+  Returns:
+      ErrorResponse | OperationEnvelopeScheduleCreatedResponse
+  """
+
+  return (
+    await asyncio_detailed(
+      graph_id=graph_id,
+      client=client,
+      body=body,
+      idempotency_key=idempotency_key,
+    )
+  ).parsed

robosystems_client/clients/ledger_client.py

@@ -103,6 +103,9 @@
 from ..api.extensions_robo_ledger.op_update_information_block import (
   sync_detailed as op_update_information_block,
 )
+from ..api.extensions_robo_ledger.op_rebuild_schedule import (
+  sync_detailed as op_rebuild_schedule,
+)
 from ..api.extensions_robo_ledger.op_add_publish_list_members import (
   sync_detailed as op_add_publish_list_members,
 )
@@ -252,6 +255,7 @@
 from ..models.delete_rollforward_arm import DeleteRollforwardArm
 from ..models.delete_schedule_arm import DeleteScheduleArm
 from ..models.delete_schedule_request import DeleteScheduleRequest
+from ..models.rebuild_schedule_request import RebuildScheduleRequest
 from ..models.update_legacy_arm import UpdateLegacyArm
 from ..models.update_rollforward_arm import UpdateRollforwardArm
 from ..models.link_entity_taxonomy_request import LinkEntityTaxonomyRequest
@@ -309,6 +313,7 @@
 from ..models.publish_list_member_response import PublishListMemberResponse
 from ..models.publish_list_response import PublishListResponse
 from ..models.report_response import ReportResponse
+from ..models.schedule_created_response import ScheduleCreatedResponse
 from ..models.share_report_response import ShareReportResponse
 from ..models.taxonomy_block_envelope import TaxonomyBlockEnvelope
 
@@ -1187,6 +1192,40 @@ def delete_schedule(
       "Delete schedule", envelope, DeleteInformationBlockResponse
     )
 
+  def rebuild_schedule(
+    self,
+    graph_id: str,
+    structure_id: str,
+    *,
+    idempotency_key: str | None = None,
+  ) -> ScheduleCreatedResponse:
+    """Rebuild a schedule in place — re-run the generator on an existing schedule.
+
+    Atomic alternative to delete-then-recreate (which orphans pending
+    obligations): preserves the structure id, element associations, and
+    taxonomy; voids the old pending obligation chain; deletes the old
+    facts + SumEquals rules; and regenerates fresh forward facts + a
+    fresh obligation chain from the schedule's stored definition
+    (``entry_template`` / ``schedule_metadata`` / ``monthly_amount`` /
+    period bounds). The historical-vs-in-scope split is re-derived from
+    the current fiscal calendar ``closed_through``, so a rebuild re-scopes
+    the schedule to today's close state. Use this to pick up a fixed
+    generator without orphaning obligations.
+
+    Supply ``idempotency_key`` to make the call safe to retry — replays
+    within 24 hours return the same envelope. Reusing the key with a
+    different body returns HTTP 409.
+    """
+    body = RebuildScheduleRequest(structure_id=structure_id)
+    response = op_rebuild_schedule(
+      graph_id=graph_id,
+      body=body,
+      client=self._get_client(),
+      idempotency_key=idempotency_key if idempotency_key is not None else UNSET,
+    )
+    envelope = self._call_op("Rebuild schedule", response)
+    return self._typed_result("Rebuild schedule", envelope, ScheduleCreatedResponse)
+
   # ── Period close ────────────────────────────────────────────────────
 
   def get_period_close_status(