Skip to content

Fix SaaS DB lifecycle retries and stale ID recovery#157

Open
jana-selva wants to merge 3 commits into
mainfrom
fix/saas-db-lifecycle-retries
Open

Fix SaaS DB lifecycle retries and stale ID recovery#157
jana-selva wants to merge 3 commits into
mainfrom
fix/saas-db-lifecycle-retries

Conversation

@jana-selva
Copy link
Copy Markdown

@jana-selva jana-selva commented Apr 29, 2026

Summary

  • recover stale SaaS database IDs by name when startup polling hits 404 User/Database not found
  • return the effective database id from wait_until_running()
  • retry transient delete failures (429/5xx) and stale-id delete races

Why

-Notebook CI showed SaaS setup/teardown failures where the created id was not resolvable and delete returned transient internal errors.

Validation

  • PYTHONPATH=/tmp/exasol-upstream/saas-api-python poetry run pytest -q /tmp/exasol-upstream/saas-api-python/test/unit/test_api_access.py -> 9 passed

@kratz00 kratz00 force-pushed the fix/saas-db-lifecycle-retries branch from eb7f84c to 764e8dd Compare May 8, 2026 10:48
@kratz00 kratz00 requested a deployment to manual-approval May 8, 2026 10:48 — with GitHub Actions Waiting
@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud Bot commented May 8, 2026

Quality Gate Failed Quality Gate failed

Failed conditions
67.4% Coverage on New Code (required ≥ 80%)
1 New Code Smells (required ≤ 0)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants