py-serverless-kit 3.0.0__tar.gz → 3.1.1__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- py_serverless_kit-3.1.1/CHANGELOG.md +1200 -0
- py_serverless_kit-3.1.1/PKG-INFO +616 -0
- py_serverless_kit-3.1.1/aws/s3/ARCHITECTURE.md +149 -0
- py_serverless_kit-3.1.1/aws/s3/README.md +190 -0
- py_serverless_kit-3.1.1/aws/s3/nodejs/Dockerfile +18 -0
- py_serverless_kit-3.1.1/aws/s3/nodejs/lib/access.js +219 -0
- py_serverless_kit-3.1.1/aws/s3/nodejs/lib/checksums.js +134 -0
- py_serverless_kit-3.1.1/aws/s3/nodejs/lib/config.js +65 -0
- py_serverless_kit-3.1.1/aws/s3/nodejs/lib/console/api.js +599 -0
- py_serverless_kit-3.1.1/aws/s3/nodejs/lib/console/router.js +53 -0
- py_serverless_kit-3.1.1/aws/s3/nodejs/lib/console/session.js +113 -0
- py_serverless_kit-3.1.1/aws/s3/nodejs/lib/console/static.js +77 -0
- py_serverless_kit-3.1.1/aws/s3/nodejs/lib/cors.js +77 -0
- py_serverless_kit-3.1.1/aws/s3/nodejs/lib/errors.js +30 -0
- py_serverless_kit-3.1.1/aws/s3/nodejs/lib/http.js +287 -0
- py_serverless_kit-3.1.1/aws/s3/nodejs/lib/lifecycle.js +199 -0
- py_serverless_kit-3.1.1/aws/s3/nodejs/lib/main.js +57 -0
- py_serverless_kit-3.1.1/aws/s3/nodejs/lib/objectlock.js +40 -0
- py_serverless_kit-3.1.1/aws/s3/nodejs/lib/policy.js +273 -0
- py_serverless_kit-3.1.1/aws/s3/nodejs/lib/py.js +149 -0
- py_serverless_kit-3.1.1/aws/s3/nodejs/lib/routes/bucket.js +322 -0
- py_serverless_kit-3.1.1/aws/s3/nodejs/lib/routes/config.js +265 -0
- py_serverless_kit-3.1.1/aws/s3/nodejs/lib/routes/index.js +91 -0
- py_serverless_kit-3.1.1/aws/s3/nodejs/lib/routes/multipart.js +242 -0
- py_serverless_kit-3.1.1/aws/s3/nodejs/lib/routes/objects.js +399 -0
- py_serverless_kit-3.1.1/aws/s3/nodejs/lib/routes/post.js +208 -0
- py_serverless_kit-3.1.1/aws/s3/nodejs/lib/routes/service.js +32 -0
- py_serverless_kit-3.1.1/aws/s3/nodejs/lib/routes/website.js +86 -0
- py_serverless_kit-3.1.1/aws/s3/nodejs/lib/sigv4.js +405 -0
- py_serverless_kit-3.1.1/aws/s3/nodejs/lib/store.js +220 -0
- py_serverless_kit-3.1.1/aws/s3/nodejs/lib/util.js +240 -0
- py_serverless_kit-3.1.1/aws/s3/nodejs/lib/versions.js +497 -0
- py_serverless_kit-3.1.1/aws/s3/nodejs/server.js +41 -0
- py_serverless_kit-3.1.1/aws/s3/python/Dockerfile +18 -0
- py_serverless_kit-3.1.1/aws/s3/python/s3server/__init__.py +50 -0
- py_serverless_kit-3.1.1/aws/s3/python/s3server/access.py +218 -0
- py_serverless_kit-3.1.1/aws/s3/python/s3server/checksums.py +77 -0
- py_serverless_kit-3.1.1/aws/s3/python/s3server/config.py +188 -0
- py_serverless_kit-3.1.1/aws/s3/python/s3server/console/__init__.py +1 -0
- py_serverless_kit-3.1.1/aws/s3/python/s3server/console/api.py +661 -0
- py_serverless_kit-3.1.1/aws/s3/python/s3server/console/router.py +111 -0
- py_serverless_kit-3.1.1/aws/s3/python/s3server/console/session.py +62 -0
- py_serverless_kit-3.1.1/aws/s3/python/s3server/console/static.py +61 -0
- py_serverless_kit-3.1.1/aws/s3/python/s3server/cors.py +84 -0
- py_serverless_kit-3.1.1/aws/s3/python/s3server/errors.py +35 -0
- py_serverless_kit-3.1.1/aws/s3/python/s3server/http.py +199 -0
- py_serverless_kit-3.1.1/aws/s3/python/s3server/lifecycle.py +200 -0
- py_serverless_kit-3.1.1/aws/s3/python/s3server/listing.py +101 -0
- py_serverless_kit-3.1.1/aws/s3/python/s3server/main.py +64 -0
- py_serverless_kit-3.1.1/aws/s3/python/s3server/objectlock.py +41 -0
- py_serverless_kit-3.1.1/aws/s3/python/s3server/objects.py +303 -0
- py_serverless_kit-3.1.1/aws/s3/python/s3server/payload.py +272 -0
- py_serverless_kit-3.1.1/aws/s3/python/s3server/policy.py +281 -0
- py_serverless_kit-3.1.1/aws/s3/python/s3server/request.py +210 -0
- py_serverless_kit-3.1.1/aws/s3/python/s3server/routes/__init__.py +1 -0
- py_serverless_kit-3.1.1/aws/s3/python/s3server/routes/bucket.py +377 -0
- py_serverless_kit-3.1.1/aws/s3/python/s3server/routes/config.py +245 -0
- py_serverless_kit-3.1.1/aws/s3/python/s3server/routes/multipart.py +313 -0
- py_serverless_kit-3.1.1/aws/s3/python/s3server/routes/objects.py +475 -0
- py_serverless_kit-3.1.1/aws/s3/python/s3server/routes/post.py +214 -0
- py_serverless_kit-3.1.1/aws/s3/python/s3server/routes/service.py +39 -0
- py_serverless_kit-3.1.1/aws/s3/python/s3server/routes/website.py +113 -0
- py_serverless_kit-3.1.1/aws/s3/python/s3server/sigv4.py +238 -0
- py_serverless_kit-3.1.1/aws/s3/python/s3server/store.py +250 -0
- py_serverless_kit-3.1.1/aws/s3/python/s3server/util.py +126 -0
- py_serverless_kit-3.1.1/aws/s3/python/s3server/versions.py +105 -0
- py_serverless_kit-3.1.1/aws/s3/python/server.py +11 -0
- py_serverless_kit-3.1.1/aws/s3/ui/assets/css/components.css +546 -0
- py_serverless_kit-3.1.1/aws/s3/ui/assets/css/layout.css +275 -0
- py_serverless_kit-3.1.1/aws/s3/ui/assets/css/theme.css +245 -0
- py_serverless_kit-3.1.1/aws/s3/ui/assets/favicon.svg +1 -0
- py_serverless_kit-3.1.1/aws/s3/ui/assets/js/app.js +79 -0
- py_serverless_kit-3.1.1/aws/s3/ui/assets/js/components/alert.js +45 -0
- py_serverless_kit-3.1.1/aws/s3/ui/assets/js/components/badge.js +17 -0
- py_serverless_kit-3.1.1/aws/s3/ui/assets/js/components/breadcrumbs.js +24 -0
- py_serverless_kit-3.1.1/aws/s3/ui/assets/js/components/button.js +79 -0
- py_serverless_kit-3.1.1/aws/s3/ui/assets/js/components/confirm-page.js +44 -0
- py_serverless_kit-3.1.1/aws/s3/ui/assets/js/components/container.js +55 -0
- py_serverless_kit-3.1.1/aws/s3/ui/assets/js/components/copy-button.js +68 -0
- py_serverless_kit-3.1.1/aws/s3/ui/assets/js/components/dropdown.js +101 -0
- py_serverless_kit-3.1.1/aws/s3/ui/assets/js/components/field.js +124 -0
- py_serverless_kit-3.1.1/aws/s3/ui/assets/js/components/icons.js +71 -0
- py_serverless_kit-3.1.1/aws/s3/ui/assets/js/components/json-editor.js +118 -0
- py_serverless_kit-3.1.1/aws/s3/ui/assets/js/components/kv-list.js +27 -0
- py_serverless_kit-3.1.1/aws/s3/ui/assets/js/components/modal.js +112 -0
- py_serverless_kit-3.1.1/aws/s3/ui/assets/js/components/page-header.js +19 -0
- py_serverless_kit-3.1.1/aws/s3/ui/assets/js/components/table.js +287 -0
- py_serverless_kit-3.1.1/aws/s3/ui/assets/js/components/tabs.js +31 -0
- py_serverless_kit-3.1.1/aws/s3/ui/assets/js/components/tag-editor.js +84 -0
- py_serverless_kit-3.1.1/aws/s3/ui/assets/js/components/toast.js +73 -0
- py_serverless_kit-3.1.1/aws/s3/ui/assets/js/components/toggle.js +16 -0
- py_serverless_kit-3.1.1/aws/s3/ui/assets/js/core/api.js +162 -0
- py_serverless_kit-3.1.1/aws/s3/ui/assets/js/core/dom.js +72 -0
- py_serverless_kit-3.1.1/aws/s3/ui/assets/js/core/format.js +89 -0
- py_serverless_kit-3.1.1/aws/s3/ui/assets/js/core/router.js +107 -0
- py_serverless_kit-3.1.1/aws/s3/ui/assets/js/core/s3.js +404 -0
- py_serverless_kit-3.1.1/aws/s3/ui/assets/js/core/state.js +39 -0
- py_serverless_kit-3.1.1/aws/s3/ui/assets/js/core/theme.js +36 -0
- py_serverless_kit-3.1.1/aws/s3/ui/assets/js/examples/cors-examples.js +46 -0
- py_serverless_kit-3.1.1/aws/s3/ui/assets/js/examples/policy-examples.js +203 -0
- py_serverless_kit-3.1.1/aws/s3/ui/assets/js/views/bucket-danger.js +173 -0
- py_serverless_kit-3.1.1/aws/s3/ui/assets/js/views/bucket-settings.js +504 -0
- py_serverless_kit-3.1.1/aws/s3/ui/assets/js/views/bucket.js +64 -0
- py_serverless_kit-3.1.1/aws/s3/ui/assets/js/views/buckets.js +104 -0
- py_serverless_kit-3.1.1/aws/s3/ui/assets/js/views/common.js +76 -0
- py_serverless_kit-3.1.1/aws/s3/ui/assets/js/views/create-bucket.js +246 -0
- py_serverless_kit-3.1.1/aws/s3/ui/assets/js/views/delete-objects.js +174 -0
- py_serverless_kit-3.1.1/aws/s3/ui/assets/js/views/forms.js +98 -0
- py_serverless_kit-3.1.1/aws/s3/ui/assets/js/views/lifecycle-rule.js +326 -0
- py_serverless_kit-3.1.1/aws/s3/ui/assets/js/views/login.js +61 -0
- py_serverless_kit-3.1.1/aws/s3/ui/assets/js/views/management.js +126 -0
- py_serverless_kit-3.1.1/aws/s3/ui/assets/js/views/object-actions.js +269 -0
- py_serverless_kit-3.1.1/aws/s3/ui/assets/js/views/object-edit.js +173 -0
- py_serverless_kit-3.1.1/aws/s3/ui/assets/js/views/object.js +512 -0
- py_serverless_kit-3.1.1/aws/s3/ui/assets/js/views/objects.js +328 -0
- py_serverless_kit-3.1.1/aws/s3/ui/assets/js/views/permissions.js +137 -0
- py_serverless_kit-3.1.1/aws/s3/ui/assets/js/views/policy-editor.js +119 -0
- py_serverless_kit-3.1.1/aws/s3/ui/assets/js/views/properties.js +120 -0
- py_serverless_kit-3.1.1/aws/s3/ui/assets/js/views/shell.js +179 -0
- py_serverless_kit-3.1.1/aws/s3/ui/assets/js/views/upload.js +351 -0
- py_serverless_kit-3.1.1/aws/s3/ui/index.html +20 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/ARCHITECTURE.md +93 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/README.md +176 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/nodejs/Dockerfile +18 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/nodejs/lib/config.js +47 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/nodejs/lib/console.js +133 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/nodejs/lib/crypto.js +63 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/nodejs/lib/errors.js +16 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/nodejs/lib/http.js +155 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/nodejs/lib/keyring.js +99 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/nodejs/lib/main.js +58 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/nodejs/lib/operations.js +300 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/nodejs/lib/sigv4.js +79 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/nodejs/lib/store.js +117 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/nodejs/lib/util.js +37 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/nodejs/lib/values.js +197 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/nodejs/package.json +19 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/nodejs/server.js +24 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/python/Dockerfile +18 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/python/server.py +25 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/python/smserver/__init__.py +19 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/python/smserver/ciphers.py +354 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/python/smserver/config.py +67 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/python/smserver/console.py +131 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/python/smserver/errors.py +21 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/python/smserver/handler.py +161 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/python/smserver/keyring.py +112 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/python/smserver/main.py +64 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/python/smserver/operations.py +359 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/python/smserver/sigv4.py +72 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/python/smserver/store.py +129 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/python/smserver/util.py +14 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/python/smserver/values.py +208 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/ui/assets/css/components.css +242 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/ui/assets/css/layout.css +63 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/ui/assets/css/theme.css +130 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/ui/assets/js/app.js +52 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/ui/assets/js/components/alert.js +13 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/ui/assets/js/components/badge.js +13 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/ui/assets/js/components/breadcrumbs.js +15 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/ui/assets/js/components/button.js +55 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/ui/assets/js/components/code-samples.js +26 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/ui/assets/js/components/container.js +19 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/ui/assets/js/components/copy-button.js +40 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/ui/assets/js/components/dropdown.js +57 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/ui/assets/js/components/flash.js +42 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/ui/assets/js/components/form-field.js +47 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/ui/assets/js/components/json-editor.js +68 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/ui/assets/js/components/key-value.js +19 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/ui/assets/js/components/kv-editor.js +127 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/ui/assets/js/components/modal.js +61 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/ui/assets/js/components/page-header.js +11 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/ui/assets/js/components/segmented.js +30 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/ui/assets/js/components/table.js +175 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/ui/assets/js/components/tabs.js +39 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/ui/assets/js/components/tag-editor.js +56 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/ui/assets/js/components/toggle.js +9 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/ui/assets/js/components/wizard.js +75 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/ui/assets/js/core/api.js +80 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/ui/assets/js/core/dom.js +70 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/ui/assets/js/core/format.js +62 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/ui/assets/js/core/icons.js +59 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/ui/assets/js/core/password.js +9 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/ui/assets/js/core/router.js +67 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/ui/assets/js/core/snippets.js +64 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/ui/assets/js/core/state.js +47 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/ui/assets/js/core/theme.js +27 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/ui/assets/js/views/delete-secret.js +83 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/ui/assets/js/views/login.js +72 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/ui/assets/js/views/not-found.js +15 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/ui/assets/js/views/quick-start.js +36 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/ui/assets/js/views/secret/permissions-tab.js +110 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/ui/assets/js/views/secret/tags-tab.js +66 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/ui/assets/js/views/secret/value-panel.js +124 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/ui/assets/js/views/secret/versions-tab.js +75 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/ui/assets/js/views/secret-detail.js +133 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/ui/assets/js/views/secrets-list.js +99 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/ui/assets/js/views/shell.js +108 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/ui/assets/js/views/store-secret.js +156 -0
- py_serverless_kit-3.1.1/aws/secretsmanager/ui/index.html +16 -0
- py_serverless_kit-3.1.1/dashboard-ui/src/studio/api.ts +576 -0
- py_serverless_kit-3.1.1/dashboard-ui/src/studio/mock.ts +593 -0
- py_serverless_kit-3.1.1/dashboard-ui/src/studio/studio.css +967 -0
- py_serverless_kit-3.1.1/dashboard-ui/src/studio/views/WorkflowTest.tsx +272 -0
- py_serverless_kit-3.1.1/dashboard-ui/src/studio/views/Workflows.tsx +917 -0
- py_serverless_kit-3.1.1/docs/deployment/workflows.md +239 -0
- py_serverless_kit-3.1.1/docs/onprem/aws-compatible/README.md +175 -0
- py_serverless_kit-3.1.1/docs/onprem/aws-compatible/s3-api-reference.md +183 -0
- py_serverless_kit-3.1.1/docs/onprem/aws-compatible/s3.md +366 -0
- py_serverless_kit-3.1.1/docs/onprem/aws-compatible/secretsmanager.md +336 -0
- py_serverless_kit-3.1.1/docs/studio-guide/deploy.md +148 -0
- py_serverless_kit-3.1.1/docs/studio-guide/workflows.md +137 -0
- py_serverless_kit-3.1.1/docs/studio.md +232 -0
- py_serverless_kit-3.1.1/docs/workflow-executions.md +156 -0
- py_serverless_kit-3.1.1/src/py_serverless_kit/_version.py +2 -0
- py_serverless_kit-3.1.1/src/py_serverless_kit/core/executions.py +548 -0
- py_serverless_kit-3.1.1/src/py_serverless_kit/core/onprem_s3.py +170 -0
- py_serverless_kit-3.1.1/src/py_serverless_kit/core/onprem_secretsmanager.py +213 -0
- py_serverless_kit-3.1.1/src/py_serverless_kit/local/runner.py +328 -0
- py_serverless_kit-3.1.1/src/py_serverless_kit/runtime/executions.py +481 -0
- py_serverless_kit-3.1.1/src/py_serverless_kit/runtime/workflow.py +480 -0
- py_serverless_kit-3.1.1/src/py_serverless_kit/runtime_js/package.json +12 -0
- py_serverless_kit-3.1.1/src/py_serverless_kit/runtime_js/workflow.js +643 -0
- py_serverless_kit-3.1.1/src/py_serverless_kit/studio/server.py +1191 -0
- py_serverless_kit-3.1.1/src/py_serverless_kit/studio/studio.html +139 -0
- py_serverless_kit-3.1.1/src/py_serverless_kit/studio/workflow_test.py +554 -0
- py_serverless_kit-3.1.1/src/py_serverless_kit/vault/permissions.py +388 -0
- py_serverless_kit-3.1.1/tests/core/test_onprem_s3.py +743 -0
- py_serverless_kit-3.1.1/tests/core/test_onprem_secretsmanager.py +544 -0
- py_serverless_kit-3.1.1/tests/runtime/test_executions.py +247 -0
- py_serverless_kit-3.1.1/tests/runtime/test_workflow_engine.py +199 -0
- py_serverless_kit-3.1.1/tests/runtime_js/workflow.test.js +257 -0
- py_serverless_kit-3.1.1/tests/studio/test_studio.py +692 -0
- py_serverless_kit-3.1.1/tests/test_executions_backends.py +353 -0
- py_serverless_kit-3.1.1/tests/vault/test_vault.py +667 -0
- py_serverless_kit-3.0.0/CHANGELOG.md +0 -1150
- py_serverless_kit-3.0.0/PKG-INFO +0 -616
- py_serverless_kit-3.0.0/aws/s3/README.md +0 -172
- py_serverless_kit-3.0.0/aws/s3/nodejs/Dockerfile +0 -16
- py_serverless_kit-3.0.0/aws/s3/nodejs/server.js +0 -4624
- py_serverless_kit-3.0.0/aws/s3/python/Dockerfile +0 -16
- py_serverless_kit-3.0.0/aws/s3/python/server.py +0 -4827
- py_serverless_kit-3.0.0/aws/s3/ui/index.html +0 -925
- py_serverless_kit-3.0.0/aws/secretsmanager/README.md +0 -172
- py_serverless_kit-3.0.0/aws/secretsmanager/nodejs/Dockerfile +0 -16
- py_serverless_kit-3.0.0/aws/secretsmanager/nodejs/package.json +0 -15
- py_serverless_kit-3.0.0/aws/secretsmanager/nodejs/server.js +0 -1158
- py_serverless_kit-3.0.0/aws/secretsmanager/python/Dockerfile +0 -16
- py_serverless_kit-3.0.0/aws/secretsmanager/python/server.py +0 -1527
- py_serverless_kit-3.0.0/aws/secretsmanager/ui/index.html +0 -440
- py_serverless_kit-3.0.0/dashboard-ui/src/studio/api.ts +0 -514
- py_serverless_kit-3.0.0/dashboard-ui/src/studio/mock.ts +0 -407
- py_serverless_kit-3.0.0/dashboard-ui/src/studio/studio.css +0 -952
- py_serverless_kit-3.0.0/dashboard-ui/src/studio/views/Workflows.tsx +0 -882
- py_serverless_kit-3.0.0/docs/deployment/workflows.md +0 -235
- py_serverless_kit-3.0.0/docs/onprem/aws-compatible/README.md +0 -175
- py_serverless_kit-3.0.0/docs/onprem/aws-compatible/s3-api-reference.md +0 -165
- py_serverless_kit-3.0.0/docs/onprem/aws-compatible/s3.md +0 -353
- py_serverless_kit-3.0.0/docs/onprem/aws-compatible/secretsmanager.md +0 -336
- py_serverless_kit-3.0.0/docs/studio-guide/deploy.md +0 -147
- py_serverless_kit-3.0.0/docs/studio-guide/workflows.md +0 -132
- py_serverless_kit-3.0.0/docs/studio.md +0 -232
- py_serverless_kit-3.0.0/docs/workflow-executions.md +0 -156
- py_serverless_kit-3.0.0/src/py_serverless_kit/_version.py +0 -2
- py_serverless_kit-3.0.0/src/py_serverless_kit/core/executions.py +0 -542
- py_serverless_kit-3.0.0/src/py_serverless_kit/core/onprem_s3.py +0 -153
- py_serverless_kit-3.0.0/src/py_serverless_kit/core/onprem_secretsmanager.py +0 -189
- py_serverless_kit-3.0.0/src/py_serverless_kit/local/runner.py +0 -318
- py_serverless_kit-3.0.0/src/py_serverless_kit/runtime/executions.py +0 -480
- py_serverless_kit-3.0.0/src/py_serverless_kit/runtime/workflow.py +0 -434
- py_serverless_kit-3.0.0/src/py_serverless_kit/runtime_js/package.json +0 -12
- py_serverless_kit-3.0.0/src/py_serverless_kit/runtime_js/workflow.js +0 -604
- py_serverless_kit-3.0.0/src/py_serverless_kit/studio/server.py +0 -1175
- py_serverless_kit-3.0.0/src/py_serverless_kit/studio/studio.html +0 -139
- py_serverless_kit-3.0.0/src/py_serverless_kit/vault/permissions.py +0 -380
- py_serverless_kit-3.0.0/tests/core/test_onprem_s3.py +0 -560
- py_serverless_kit-3.0.0/tests/core/test_onprem_secretsmanager.py +0 -538
- py_serverless_kit-3.0.0/tests/runtime/test_executions.py +0 -246
- py_serverless_kit-3.0.0/tests/runtime/test_workflow_engine.py +0 -174
- py_serverless_kit-3.0.0/tests/runtime_js/workflow.test.js +0 -253
- py_serverless_kit-3.0.0/tests/studio/test_studio.py +0 -628
- py_serverless_kit-3.0.0/tests/test_executions_backends.py +0 -348
- py_serverless_kit-3.0.0/tests/vault/test_vault.py +0 -663
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/.gitignore +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/CONTRIBUTING.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/LICENSE +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/ai-agent/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/aws/.gitignore +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/aws/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/aws/s3/.dockerignore +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/aws/s3/docker-compose.yml +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/aws/s3/nodejs/package.json +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/aws/secretsmanager/.dockerignore +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/aws/secretsmanager/docker-compose.yml +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/App.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/api.ts +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/components/Badge.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/components/Card.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/components/CopyButton.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/components/DataTable.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/components/Drawer.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/components/Feedback.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/components/Inputs.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/components/JsonView.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/components/Link.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/components/LogStreams.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/components/LogViewer.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/components/Pagination.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/components/Tabs.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/components/Timeline.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/format.ts +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/hooks.ts +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/main.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/App.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/__tests__/deployLog.test.ts +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/__tests__/node-test.d.ts +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/__tests__/permissions.test.ts +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/__tests__/placement.test.ts +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/auth.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/compat.ts +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/components/AlgorithmPicker.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/components/CloudResources.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/components/CodeEditor.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/components/Console.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/components/DeploySteps.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/components/EnableControl.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/components/Feedback.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/components/FilePicker.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/components/FirewallPanel.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/components/Forms.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/components/Markdown.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/components/Misc.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/components/Monitoring.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/components/OnPremMachines.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/components/OnPremServices.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/components/Placement.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/components/ProviderCard.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/components/Replication.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/components/ReplicationDiagram.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/components/ResourceData.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/components/ResourceGuides.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/components/ResourceTester.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/components/ServerPicker.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/components/ServerUsage.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/components/ServiceBrowser.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/deployLog.ts +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/hana/HanaCards.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/hana/HanaPanel.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/jobs.ts +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/main.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/permissions.ts +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/placement.ts +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/route.ts +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/shadow.ts +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/store.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/stubs.ts +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/types.ts +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/util.ts +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/views/Cluster.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/views/Code.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/views/Deploy.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/views/Functions.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/views/LoadBalancers.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/views/Logs.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/views/Network.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/views/NewProject.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/views/Overview.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/views/Resources.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/views/Security.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/views/Setup.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/views/Test.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/views/TriggerForms.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/views/Yaml.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/studio/views/flow.ts +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/styles.css +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/types.ts +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/views/DeploymentView.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/views/ExecutionsTab.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/views/FunctionsTab.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/views/MiscTabs.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/views/Overview.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/views/StartDialog.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/dashboard-ui/src/views/WorkflowsTab.tsx +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/deploy_docs/CONTRIBUTING.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/architecture.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/assistant.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/cli.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/client.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/cluster.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/configuration.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/dashboard.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/dead-letter-queues.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/deployment/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/deployment/deploy-remove-info.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/deployment/logs.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/deployment/monitoring-and-dashboard.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/deployment/settings-and-config.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/deployment/stages.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/events.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/functions/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/functions/configuration.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/functions/create.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/functions/invoke-and-test.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/getting-started.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/guide/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/guide/concepts.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/guide/end-to-end-cli.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/guide/end-to-end-onprem-cluster.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/guide/end-to-end-studio.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/handlers.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/diagrams/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/diagrams/architecture-deploy-pipeline.mmd +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/diagrams/architecture-deploy-pipeline.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/diagrams/architecture-nodejs.mmd +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/diagrams/architecture-nodejs.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/diagrams/architecture-onprem-host.mmd +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/diagrams/architecture-onprem-host.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/diagrams/architecture-overview.mmd +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/diagrams/architecture-overview.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/diagrams/architecture-runtime-flow.mmd +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/diagrams/architecture-runtime-flow.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/diagrams/architecture-studio-hana.mmd +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/diagrams/architecture-studio-hana.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/diagrams/architecture-vault.mmd +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/diagrams/architecture-vault.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/diagrams/architecture-workflow-engines.mmd +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/diagrams/architecture-workflow-engines.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/diagrams/cluster-load-balancer.mmd +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/diagrams/cluster-load-balancer.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/diagrams/cluster-replicas.mmd +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/diagrams/cluster-replicas.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/diagrams/contributing-deploy.mmd +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/diagrams/contributing-deploy.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/diagrams/contributing-runtime.mmd +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/diagrams/contributing-runtime.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/diagrams/example-migrate-lambda.mmd +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/diagrams/example-migrate-lambda.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/diagrams/example-workflow-orders.mmd +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/diagrams/example-workflow-orders.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/diagrams/guide-cluster-layout.mmd +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/diagrams/guide-cluster-layout.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/diagrams/load-balancer-paths.mmd +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/diagrams/load-balancer-paths.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/diagrams/load-balancer-shared.mmd +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/diagrams/load-balancer-shared.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/diagrams/login-chain.mmd +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/diagrams/login-chain.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/diagrams/network-function-groups.mmd +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/diagrams/network-function-groups.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/diagrams/network-map-example.mmd +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/diagrams/network-map-example.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/diagrams/readme-deploy.mmd +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/diagrams/readme-deploy.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/diagrams/readme-runtime.mmd +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/diagrams/readme-runtime.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/diagrams/smtp-flow.mmd +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/diagrams/smtp-flow.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/admin-create.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/audit.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/balancer.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/cluster-alert.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/cluster-card.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/cluster-new.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/code.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/dashboard.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/database-form.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/database-listed.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/deploy-done.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/deploy.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/firewall.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/first-start.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/function-basics.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/function-review.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/function-trigger-cards.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/function-trigger-http.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/functions.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/hana-chat.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/hana-setup.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/install.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/keys.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/login.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/logs.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/network-machine.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/network.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/new-project.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/overview.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/permissions.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/placement.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/provider-switch.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/replication.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/resource-add.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/server-add.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/service-catalog-databases.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/service-catalog.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/service-details.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/service-how-to-use.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/service-monitor.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/services/apache-kafka.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/services/azurite.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/services/clickhouse.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/services/dragonfly.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/services/elasticmq.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/services/fake-gcs.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/services/gitea.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/services/grafana.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/services/infisical.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/services/jaeger.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/services/kafka.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/services/keycloak.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/services/keydb.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/services/lavinmq.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/services/localemu.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/services/localstack.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/services/mailpit.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/services/mariadb.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/services/meilisearch.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/services/memcached.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/services/minio.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/services/mongodb.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/services/mosquitto.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/services/mysql.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/services/n8n.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/services/nats.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/services/neo4j.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/services/nginx-proxy-manager.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/services/openbao.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/services/portainer.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/services/postgres.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/services/prometheus.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/services/qdrant.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/services/rabbitmq.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/services/redis.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/services/rustfs.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/services/s3.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/services/secretsmanager.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/services/smtp.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/services/typesense.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/services/uptime-kuma.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/services/valkey.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/setup.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/smtp-form.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/test-result.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/test.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/trigger-queue.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/trigger-schedule.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/trigger-smtp.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/trigger-storage.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/trigger-topic.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/workflow-create.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/workflow-state.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/workflow.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/workflows.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/images/studio/yaml.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/load-balancers.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/local-development.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/migrating-from-aws.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/nodejs.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/cloud-resources.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/database-scaling.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/firewall.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/load-balancers.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/network-map.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/placement.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/resources.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/scaling/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/scaling/docker-swarm.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/scaling/kubernetes-k3s.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/scaling/nomad.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/scaling/replicas-and-alerts.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/servers.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/services/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/services/apache-kafka.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/services/azurite.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/services/clickhouse.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/services/dragonfly.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/services/elasticmq.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/services/fake-gcs.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/services/gitea.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/services/grafana.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/services/infisical.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/services/jaeger.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/services/kafka.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/services/keycloak.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/services/keydb.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/services/lavinmq.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/services/localemu.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/services/localstack.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/services/mailpit.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/services/mariadb.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/services/meilisearch.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/services/memcached.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/services/minio.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/services/mongodb.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/services/mosquitto.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/services/mysql.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/services/n8n.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/services/nats.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/services/neo4j.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/services/nginx-proxy-manager.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/services/openbao.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/services/portainer.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/services/postgres.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/services/prometheus.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/services/qdrant.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/services/rabbitmq.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/services/redis.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/services/rustfs.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/services/s3.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/services/secretsmanager.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/services/smtp.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/services/typesense.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/services/uptime-kuma.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/services/valkey.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem/terminal-and-software.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/onprem-network.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/placement.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/providers/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/providers/alibaba/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/providers/aws/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/providers/aws/triggers-and-resources.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/providers/azure/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/providers/azure/triggers-and-resources.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/providers/cloudflare/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/providers/digitalocean/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/providers/gcp/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/providers/gcp/triggers-and-resources.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/providers/huawei/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/providers/ibm/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/providers/onprem/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/providers/onprem/deploy-methods.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/providers/onprem/host-api.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/providers/oracle/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/providers/tencent/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/providers.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/requirements.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/alibaba/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/alibaba/cache.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/alibaba/custom.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/alibaba/database.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/alibaba/queue.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/alibaba/storage.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/alibaba/topic.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/aws/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/aws/cache.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/aws/custom.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/aws/database.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/aws/queue.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/aws/storage.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/aws/topic.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/azure/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/azure/cache.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/azure/custom.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/azure/database.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/azure/queue.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/azure/storage.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/azure/topic.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/cloudflare/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/cloudflare/cache.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/cloudflare/custom.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/cloudflare/database.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/cloudflare/queue.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/cloudflare/storage.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/cloudflare/topic.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/compatibility.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/digitalocean/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/digitalocean/cache.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/digitalocean/custom.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/digitalocean/database.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/digitalocean/queue.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/digitalocean/storage.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/digitalocean/topic.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/gcp/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/gcp/cache.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/gcp/custom.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/gcp/database.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/gcp/queue.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/gcp/storage.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/gcp/topic.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/huawei/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/huawei/cache.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/huawei/custom.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/huawei/database.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/huawei/queue.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/huawei/storage.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/huawei/topic.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/ibm/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/ibm/cache.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/ibm/custom.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/ibm/database.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/ibm/queue.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/ibm/storage.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/ibm/topic.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/onprem/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/onprem/cache.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/onprem/custom.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/onprem/database.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/onprem/queue.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/onprem/secrets.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/onprem/services.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/onprem/storage.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/onprem/topic.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/oracle/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/oracle/cache.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/oracle/custom.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/oracle/database.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/oracle/queue.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/oracle/storage.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/oracle/topic.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/tencent/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/tencent/cache.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/tencent/custom.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/tencent/database.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/tencent/queue.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/tencent/storage.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-guides/tencent/topic.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resource-usage.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/resources.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/scenarios.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/security-vault.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/smtp/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/smtp/smtp_flow.jpg +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/studio-guide/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/studio-guide/accounts-and-team.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/studio-guide/cluster.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/studio-guide/code.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/studio-guide/firewall.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/studio-guide/functions.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/studio-guide/hana.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/studio-guide/load-balancers.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/studio-guide/logs.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/studio-guide/monitoring.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/studio-guide/network.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/studio-guide/new-project.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/studio-guide/onprem-services.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/studio-guide/overview.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/studio-guide/placement.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/studio-guide/replication.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/studio-guide/resources.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/studio-guide/servers.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/studio-guide/setup.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/studio-guide/test.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/studio-guide/trigger-forms.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/studio-guide/yaml.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/triggers/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/triggers/http.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/triggers/queue.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/triggers/schedule.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/triggers/smtp.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/triggers/storage.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/triggers/topic.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/troubleshooting.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/docs/workflows.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/01-hello-http/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/01-hello-http/app/__init__.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/01-hello-http/app/handlers.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/01-hello-http/pskit.yml +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/01-hello-http/requirements.txt +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/02-rest-api/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/02-rest-api/app/__init__.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/02-rest-api/app/handlers.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/02-rest-api/app/store.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/02-rest-api/pskit.yml +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/02-rest-api/requirements.txt +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/03-scheduled-jobs/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/03-scheduled-jobs/app/__init__.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/03-scheduled-jobs/app/jobs.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/03-scheduled-jobs/pskit.yml +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/03-scheduled-jobs/requirements.txt +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/04-queue-worker/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/04-queue-worker/app/__init__.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/04-queue-worker/app/worker.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/04-queue-worker/pskit.yml +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/04-queue-worker/requirements.txt +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/05-storage-events/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/05-storage-events/app/__init__.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/05-storage-events/app/files.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/05-storage-events/pskit.yml +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/05-storage-events/requirements.txt +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/06-pubsub-topic/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/06-pubsub-topic/app/__init__.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/06-pubsub-topic/app/subscribers.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/06-pubsub-topic/pskit.yml +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/06-pubsub-topic/requirements.txt +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/07-workflow-orders/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/07-workflow-orders/app/__init__.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/07-workflow-orders/app/orders.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/07-workflow-orders/events/b2b.json +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/07-workflow-orders/events/declined.json +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/07-workflow-orders/events/happy.json +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/07-workflow-orders/pskit.yml +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/07-workflow-orders/requirements.txt +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/08-multi-cloud/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/08-multi-cloud/app/__init__.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/08-multi-cloud/app/handlers.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/08-multi-cloud/pskit.aws.yml +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/08-multi-cloud/pskit.azure.yml +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/08-multi-cloud/pskit.gcp.yml +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/08-multi-cloud/pskit.yml +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/08-multi-cloud/requirements.txt +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/09-function-invoke/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/09-function-invoke/app/__init__.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/09-function-invoke/app/quotes.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/09-function-invoke/pskit.yml +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/09-function-invoke/requirements.txt +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/10-stages-and-config/.env.example +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/10-stages-and-config/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/10-stages-and-config/app/__init__.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/10-stages-and-config/app/handlers.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/10-stages-and-config/app/settings.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/10-stages-and-config/config/limits.json +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/10-stages-and-config/pskit.yml +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/10-stages-and-config/requirements.txt +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/11-custom-terraform/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/11-custom-terraform/app/__init__.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/11-custom-terraform/app/handlers.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/11-custom-terraform/app/repository.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/11-custom-terraform/pskit.yml +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/11-custom-terraform/requirements.txt +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/11-custom-terraform/scripts/smoke_test.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/11-custom-terraform/tests/test_orders.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/12-async-and-context/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/12-async-and-context/app/__init__.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/12-async-and-context/app/handlers.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/12-async-and-context/pskit.yml +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/12-async-and-context/requirements.txt +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/13-migrate-from-aws-lambda/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/13-migrate-from-aws-lambda/after/app/__init__.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/13-migrate-from-aws-lambda/after/app/orders.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/13-migrate-from-aws-lambda/after/pskit.yml +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/13-migrate-from-aws-lambda/after/requirements.txt +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/13-migrate-from-aws-lambda/before/lambda_function.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/13-migrate-from-aws-lambda/before/state_machine.asl.json +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/13-migrate-from-aws-lambda/before/template.yaml +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/14-testing/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/14-testing/app/__init__.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/14-testing/app/handlers.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/14-testing/ci.github-workflow.yml +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/14-testing/pskit.yml +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/14-testing/requirements.txt +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/14-testing/tests/conftest.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/14-testing/tests/test_handlers.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/14-testing/tests/test_workflow.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/15-ci-cd-deploy/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/15-ci-cd-deploy/app/__init__.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/15-ci-cd-deploy/app/handlers.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/15-ci-cd-deploy/deploy.github-workflow.yml +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/15-ci-cd-deploy/pskit.yml +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/15-ci-cd-deploy/requirements.txt +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/16-on-premises/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/16-on-premises/app/__init__.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/16-on-premises/app/handlers.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/16-on-premises/pskit.yml +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/16-on-premises/requirements.txt +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/17-on-premises-remote/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/17-on-premises-remote/app/__init__.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/17-on-premises-remote/app/handlers.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/17-on-premises-remote/pskit.yml +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/17-on-premises-remote/requirements.txt +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/18-resources/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/18-resources/app/__init__.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/18-resources/app/handlers.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/18-resources/pskit.yml +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/18-resources/requirements.txt +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/19-custom-drivers/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/19-custom-drivers/app/__init__.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/19-custom-drivers/app/backends.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/19-custom-drivers/app/handlers.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/19-custom-drivers/app/kafka_queue.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/19-custom-drivers/app/rabbitmq_queue.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/19-custom-drivers/pskit.yml +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/19-custom-drivers/requirements.txt +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/20-onprem-external-clouds/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/20-onprem-external-clouds/app/__init__.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/20-onprem-external-clouds/app/handlers.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/20-onprem-external-clouds/pskit.yml +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/20-onprem-external-clouds/requirements.txt +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/21-nodejs-typescript/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/21-nodejs-typescript/events/bad-order.json +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/21-nodejs-typescript/events/order.json +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/21-nodejs-typescript/package.json +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/21-nodejs-typescript/pskit.yml +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/21-nodejs-typescript/src/http.ts +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/21-nodejs-typescript/src/jobs.ts +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/21-nodejs-typescript/src/orders.ts +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/21-nodejs-typescript/src/workflow.ts +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/21-nodejs-typescript/tsconfig.json +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/examples/README.md +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/pyproject.toml +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/__init__.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/__main__.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/cli/__init__.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/cli/main.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/cli/templates.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/cli/vault_commands.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/client.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/config/__init__.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/config/loader.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/config/schema.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/core/__init__.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/core/client_examples.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/core/client_guide.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/core/cloud_logs.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/core/deployer.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/core/describe.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/core/dlq.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/core/function_split.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/core/onprem_apps.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/core/onprem_balancers.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/core/onprem_browser.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/core/onprem_clients.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/core/onprem_cluster.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/core/onprem_cluster_scripts.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/core/onprem_console.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/core/onprem_control.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/core/onprem_follow.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/core/onprem_lb.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/core/onprem_monitor.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/core/onprem_network.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/core/onprem_placement.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/core/onprem_replication.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/core/onprem_runtimes.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/core/onprem_servers.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/core/onprem_services.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/core/onprem_smtp.js +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/core/onprem_smtp.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/core/onprem_templates/kafka_queue.py.txt +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/core/onprem_templates/nats_queue.py.txt +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/core/onprem_templates/rabbitmq_queue.py.txt +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/core/onprem_terminal.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/core/onprem_usage.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/core/project.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/core/resource_code.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/core/resource_usage.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/core/retain.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/core/settings_bundle.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/core/setup_check.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/core/ssh_keys.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/core/testing.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/dashboard/__init__.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/dashboard/generator.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/dashboard/server.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/dashboard/template.html +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/local/__init__.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/local/server.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/packaging/__init__.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/packaging/builder.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/packaging/node.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/packaging/subprojects.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/providers/__init__.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/providers/alibaba.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/providers/aws.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/providers/azure.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/providers/base.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/providers/cloudflare.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/providers/digitalocean.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/providers/gcp.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/providers/huawei.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/providers/ibm.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/providers/onprem.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/providers/onprem_catalog.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/providers/onprem_remote.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/providers/onprem_spec.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/providers/oracle.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/providers/regions.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/providers/registry.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/providers/schedule.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/providers/tencent.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/providers/terraform_doc.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime/__init__.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime/adapters/__init__.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime/adapters/_httpfn.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime/adapters/alibaba.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime/adapters/aws.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime/adapters/azure.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime/adapters/base.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime/adapters/cloudflare.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime/adapters/digitalocean.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime/adapters/gcp.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime/adapters/huawei.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime/adapters/ibm.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime/adapters/onprem.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime/adapters/oracle.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime/adapters/tencent.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime/batch.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime/context.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime/cron.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime/dead_letters.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime/dispatch.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime/drivers/__init__.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime/drivers/_aws.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime/drivers/_http.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime/drivers/azure.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime/drivers/cloudflare.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime/drivers/gcp.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime/drivers/mns.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime/drivers/probe.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime/drivers/pskit_host.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime/drivers/redis.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime/drivers/redis_stream.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime/drivers/s3.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime/drivers/sqs.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime/errors.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime/event.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime/hostlog.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime/invoke.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime/log.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime/manifest.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime/node_worker.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime/onprem_host.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime/peers.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime/resources.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime/response.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime/routing.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime/secrets.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime_js/adapters/alibaba.js +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime_js/adapters/aws.js +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime_js/adapters/azure.js +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime_js/adapters/base.js +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime_js/adapters/cloudflare.js +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime_js/adapters/digitalocean.js +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime_js/adapters/gcp.js +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime_js/adapters/httpfn.js +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime_js/adapters/huawei.js +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime_js/adapters/ibm.js +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime_js/adapters/oracle.js +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime_js/adapters/tencent.js +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime_js/batch.js +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime_js/client.js +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime_js/context.js +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime_js/dispatch.js +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime_js/errors.js +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime_js/event.js +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime_js/index.d.ts +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime_js/index.js +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime_js/invoke.js +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime_js/log.js +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime_js/manifest.js +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime_js/onprem.js +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime_js/resources.js +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime_js/response.js +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime_js/routing.js +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime_js/secrets.js +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime_js/util.js +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/runtime_js/worker.js +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/studio/__init__.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/studio/auth.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/studio/devenv.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/studio/discover.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/studio/files.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/studio/guides.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/studio/hana/__init__.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/studio/hana/actions.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/studio/hana/ailog.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/studio/hana/docs.jsonl.gz +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/studio/hana/docs_index.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/studio/hana/edits.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/studio/hana/knowledge.jsonl.gz +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/studio/hana/knowledge.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/studio/hana/model.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/studio/hana/prompt.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/studio/hana/router.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/studio/hana/runtime.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/studio/hana/session.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/studio/hana/terminal.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/studio/hana/tools.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/studio/jobs.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/studio/meta.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/studio/node_stubs.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/studio/project.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/studio/screencapture-127-0-0-1-8770-2026-10-28-11_47_23.png +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/studio/system.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/studio/vscode.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/terraform/__init__.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/terraform/runner.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/vault/__init__.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/vault/audit.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/vault/cli_gate.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/vault/crypto.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/vault/errors.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/vault/store.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/vault/workspace.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/workflows/__init__.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/workflows/asl.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/workflows/azure_logic.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/src/py_serverless_kit/workflows/gcp.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/__init__.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/config/__init__.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/config/test_loader.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/config/test_schema.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/conftest.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/core/__init__.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/core/test_dlq.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/core/test_function_split.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/core/test_kept_resources.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/core/test_onprem_balancers.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/core/test_onprem_browser_and_apps.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/core/test_onprem_cluster.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/core/test_onprem_deploy_target.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/core/test_onprem_follow.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/core/test_onprem_gui_ssh.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/core/test_onprem_lb.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/core/test_onprem_machines.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/core/test_onprem_monitor.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/core/test_onprem_network.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/core/test_onprem_placement.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/core/test_onprem_replication.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/core/test_onprem_server_keys.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/core/test_onprem_services.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/core/test_onprem_smtp.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/core/test_onprem_usage.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/core/test_resource_usage.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/core/test_retain.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/core/test_settings_bundle.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/core/test_setup_check.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/core/test_testing.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/local/__init__.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/local/test_server.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/node_support.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/providers/__init__.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/providers/test_alibaba.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/providers/test_aws.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/providers/test_azure.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/providers/test_cloudflare.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/providers/test_digitalocean.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/providers/test_gcp.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/providers/test_huawei.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/providers/test_ibm.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/providers/test_node_regional.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/providers/test_onprem.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/providers/test_onprem_node.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/providers/test_onprem_remote.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/providers/test_onprem_security.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/providers/test_oracle.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/providers/test_resources.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/providers/test_schedule.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/providers/test_tencent.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/runtime/__init__.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/runtime/test_adapter_alibaba.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/runtime/test_adapter_aws.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/runtime/test_adapter_azure.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/runtime/test_adapter_cloudflare.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/runtime/test_adapter_digitalocean.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/runtime/test_adapter_gcp.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/runtime/test_adapter_huawei.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/runtime/test_adapter_ibm.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/runtime/test_adapter_onprem.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/runtime/test_adapter_oracle.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/runtime/test_adapter_tencent.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/runtime/test_cron.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/runtime/test_dispatch.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/runtime/test_drivers.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/runtime/test_drivers_cloud.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/runtime/test_drivers_custom_host.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/runtime/test_drivers_docs_example.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/runtime/test_hostlog.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/runtime/test_models.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/runtime/test_onprem_aws_compat.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/runtime/test_onprem_entry_workflow.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/runtime/test_onprem_host.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/runtime/test_onprem_host_cluster.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/runtime/test_onprem_host_drivers.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/runtime/test_onprem_host_node.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/runtime/test_onprem_host_resources.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/runtime/test_onprem_host_security.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/runtime/test_onprem_host_smtp.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/runtime/test_peers.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/runtime/test_pskit_client.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/runtime/test_resources.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/runtime/test_secrets_infisical.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/runtime_js/__init__.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/runtime_js/_regional.js +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/runtime_js/adapter_alibaba.test.js +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/runtime_js/adapter_aws.test.js +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/runtime_js/adapter_azure.test.js +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/runtime_js/adapter_cloudflare.test.js +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/runtime_js/adapter_digitalocean.test.js +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/runtime_js/adapter_gcp.test.js +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/runtime_js/adapter_huawei.test.js +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/runtime_js/adapter_ibm.test.js +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/runtime_js/adapter_oracle.test.js +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/runtime_js/adapter_tencent.test.js +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/runtime_js/dispatch.test.js +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/runtime_js/helpers.js +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/runtime_js/models.test.js +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/runtime_js/no_filesystem.test.js +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/runtime_js/test_node_runtime.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/runtime_js/test_regional_adapters.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/runtime_js/worker.test.js +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/studio/__init__.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/studio/test_hana.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/studio/test_studio_auth.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/studio/test_studio_env.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/studio/test_studio_no_accounts.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/studio/test_studio_permissions.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/studio/test_studio_system.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/test_cli.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/test_cloud_logs.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/test_dashboard.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/test_dashboard_server.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/test_examples.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/test_packaging.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/test_packaging_node.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/vault/__init__.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/workflows/__init__.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/workflows/test_azure_logic.py +0 -0
- {py_serverless_kit-3.0.0 → py_serverless_kit-3.1.1}/tests/workflows/test_compilers.py +0 -0
|
@@ -0,0 +1,1200 @@
|
|
|
1
|
+
# Changelog
|
|
2
|
+
|
|
3
|
+
All notable changes to this project are documented here. The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) and the project uses [Semantic Versioning](https://semver.org/).
|
|
4
|
+
|
|
5
|
+
> The function runtime is bundled into every deployment. After upgrading `py-serverless-kit`, run `pskit deploy` again to pick up runtime fixes.
|
|
6
|
+
|
|
7
|
+
## [Unreleased]
|
|
8
|
+
|
|
9
|
+
## [3.1.1] - 2026-11-12
|
|
10
|
+
|
|
11
|
+
### Changed
|
|
12
|
+
- **S3 console: same look as the Secrets Manager console.** The S3 console now uses the Secrets Manager palette and
|
|
13
|
+
layout: a violet theme with matching dark colors, a light / dark / automatic theme button, a top bar with
|
|
14
|
+
*Signed in as …* and **Sign out**, a side navigation with the server endpoint and region, Secrets Manager style
|
|
15
|
+
buttons, containers, tabs, alerts and notifications, and a centered sign-in card. Pages and features are unchanged.
|
|
16
|
+
Re-create a running `s3` / `s3-node` service to get the new look.
|
|
17
|
+
|
|
18
|
+
### Fixed
|
|
19
|
+
- **S3 console stuck on "Loading the S3 console…".** The policy and CORS example modules lived in
|
|
20
|
+
`ui/assets/js/data/`, a folder name that the container copy, `.gitignore` and `.dockerignore` skip (it is reserved
|
|
21
|
+
for the server's storage). The browser got 404s for `policy-examples.js` and `cors-examples.js` and the console
|
|
22
|
+
never started. The folder is now `ui/assets/js/examples/`.
|
|
23
|
+
|
|
24
|
+
## [3.1.0] - 2026-11-11
|
|
25
|
+
|
|
26
|
+
### Changed
|
|
27
|
+
- **Secrets Manager server: split into modules, new console.** `aws/secretsmanager` is no longer one file per
|
|
28
|
+
server: `python/server.py` runs the `smserver/` package and `nodejs/server.js` runs `lib/` (same API, data file and
|
|
29
|
+
settings). The web console is rebuilt from reusable components (`ui/assets/`, ES modules, no inline scripts) and
|
|
30
|
+
laid out like the AWS console with its own colors, light and dark: a secrets table, a *Store a new secret* wizard,
|
|
31
|
+
and per-secret tabs for versions, tags and resource permissions. `SM_UI_FILE` is replaced by `SM_UI_DIR`. pskit
|
|
32
|
+
copies the whole tree into the container; re-create a running `secretsmanager` service to get the new console.
|
|
33
|
+
- **S3 server: split into modules, AWS-style console, bucket policies like AWS.** `aws/s3` now runs
|
|
34
|
+
`python/server.py` → `s3server/` and `nodejs/server.js` → `lib/` (same API, data layout and settings; see
|
|
35
|
+
`aws/s3/ARCHITECTURE.md`). The console is rebuilt from reusable components (`ui/assets/`, ES modules, no inline
|
|
36
|
+
scripts) and laid out like the AWS S3 console with its own colors: bucket list with access status, create / empty /
|
|
37
|
+
delete pages, Objects / Properties / Permissions / Management tabs, upload page, object page, versions, static
|
|
38
|
+
website hosting, a lifecycle rule form, CORS as JSON, and a bucket policy editor with a list of policy examples.
|
|
39
|
+
Settings the server only stored (acceleration, requester pays, default encryption, replication, notifications,
|
|
40
|
+
logging) are no longer in the console. `S3_UI_FILE` is replaced by `S3_UI_DIR`; re-create a running `s3` / `s3-node`
|
|
41
|
+
service to get the new console.
|
|
42
|
+
|
|
43
|
+
### Fixed
|
|
44
|
+
- **S3 server: Open and Download no longer use the console's own link.** They now use 5-minute presigned S3 URLs
|
|
45
|
+
(signed `response-content-disposition`), like the AWS console, so the address only works while it is valid and a
|
|
46
|
+
bucket policy `Deny` stops it. HTML, XML and SVG objects fetched path-style on the console's address get a
|
|
47
|
+
`sandbox` Content-Security-Policy so they cannot use the console session.
|
|
48
|
+
- **S3 server: bucket policies are evaluated like Amazon S3.** A `Deny` now applies to signed requests and presigned
|
|
49
|
+
URLs too, and to bucket settings and object tagging / ACL / retention / legal hold / restore. Principals (account,
|
|
50
|
+
access key, user ARN), `NotPrincipal`, `NotAction`, `NotResource` and conditions (`aws:SourceIp`,
|
|
51
|
+
`aws:SecureTransport`, `aws:Referer`, `aws:UserAgent`, `aws:CurrentTime`, `s3:x-amz-acl`, ... with `IfExists` and
|
|
52
|
+
`ForAnyValue` / `ForAllValues`) are supported. Before, policies only applied to anonymous requests and statements
|
|
53
|
+
with a `Condition` were ignored. A signed request can always replace the policy.
|
|
54
|
+
|
|
55
|
+
### Added
|
|
56
|
+
- **Studio Workflows: Test.** On the workflow list and in the editor, **Test** runs the workflow and shows a live trace: which state ran, which function it called, what that function returned, and which state runs next. **This machine** always uses the embedded engine and the handlers on disk. A deployed stage can be tested too, as far as that engine reports: on premises and AWS Step Functions follow the run live (AWS includes each state's output when Step Functions returns it; on premises includes each function's output after you redeploy this runtime); Google Cloud Workflows shows the current step and the final output; other clouds return the final result. After you redeploy this runtime, an embedded cloud orchestrator also returns the step history in that response. Older deployments still return only the final result.
|
|
57
|
+
- Workflow history `exit` events now include the function (for a task), a clipped output (2048 characters) and the next state or `end`. Choice states record the branch they took. Cloud orchestrator responses include `history`. On-premises hosts and already deployed functions pick this up after `pskit deploy`.
|
|
58
|
+
|
|
59
|
+
## [3.0.0] - 2026-11-10
|
|
60
|
+
|
|
61
|
+
### Added
|
|
62
|
+
- **Queue trigger: name a queue on a queue service.** On premises, a queue event may set both `resource` (the queue
|
|
63
|
+
service) and `name` (the queue on it: Redis key, SQS queue, Azure queue, and the other queue drivers). Studio shows
|
|
64
|
+
**Queue name** on that form. `pskit resources onprem create --attach` takes `--queue`. Other clouds still reject a
|
|
65
|
+
name that is not the resource's own queue.
|
|
66
|
+
- **Storage trigger actions follow the cloud.** AWS, GCP, Alibaba, Tencent and Huawei fire on `created` and `deleted`.
|
|
67
|
+
Azure fires on `created` and `updated` (one blob trigger for either; deletes are rejected). Oracle fires on
|
|
68
|
+
`created`, `updated` and `deleted`. On premises, a file change is `updated` only when that function lists `updated`.
|
|
69
|
+
Studio **Fire on** lists the actions for the selected provider. `--storage-events` sets them when attaching an
|
|
70
|
+
on-prem storage service.
|
|
71
|
+
- **On-prem database failover and several primaries.** `topology.failover: auto` (studio **If the primary dies**,
|
|
72
|
+
CLI `--failover auto`) promotes a replica when the primary stops answering. PostgreSQL with pgpool-II promotes
|
|
73
|
+
inside the load balancer; MySQL and MariaDB run a watcher. MongoDB already elects a primary. `topology.write: multi`
|
|
74
|
+
(studio **Writers**, CLI `--write multi`) is MySQL and MariaDB: every member accepts writes. PostgreSQL and MongoDB
|
|
75
|
+
keep a single primary.
|
|
76
|
+
|
|
77
|
+
## [2.13.2] - 2026-11-06
|
|
78
|
+
|
|
79
|
+
### Changed
|
|
80
|
+
- **Studio Resources: on-prem servers and services are now two separate cards.** With the on-prem provider the page shows **On-prem servers** (**+ Add server**) first, then **On-prem services** (**+ Create service**), then the resource list. Other providers keep the resource list on top. The services card has a note: to use a service in a function, first add it to Resources. The row button **Add to pskit.yml** is now **Add to resources**.
|
|
81
|
+
- **Studio Overview & provider no longer has On-premises deployment, Built-in services, Host tuning or Packaging.** The settings still work: edit `provider.options` and `package:` on the **YAML** page, and pick a machine on **Deploy**. Problems reported on them now open the **YAML** page.
|
|
82
|
+
- **Setup & credentials is no longer in the studio sidebar.** Add `#/setup` to the studio URL, or use `pskit doctor`.
|
|
83
|
+
|
|
84
|
+
### Added
|
|
85
|
+
- **Pick the dead-letter queue from a list** on a queue trigger in the studio, or type a new name.
|
|
86
|
+
- **Plain help with an example** on every trigger type and its fields, and on the function's basics, environment variables,
|
|
87
|
+
concurrency, tags and permissions in the studio.
|
|
88
|
+
|
|
89
|
+
### Fixed
|
|
90
|
+
- `dead_letter` naming a `type: queue` resource now means that resource's queue on every provider. On AWS and GCP, a resource
|
|
91
|
+
with its own `name` used to get a second queue called after the resource key.
|
|
92
|
+
|
|
93
|
+
## [2.13.1] - 2026-11-05
|
|
94
|
+
|
|
95
|
+
### Changed
|
|
96
|
+
- **The studio header no longer shows the provider.** Choose it on **Overview & provider**; the stage stays in the top bar. To
|
|
97
|
+
deploy to another provider for one run, use `pskit deploy -p <provider>`.
|
|
98
|
+
|
|
99
|
+
- **An account decrypts only what it has read on.** Create, update or delete on **Deployments** used to hold every key,
|
|
100
|
+
including SSH keys, env files and service passwords. It now holds Terraform state and tokens only. **Check your
|
|
101
|
+
deployers:** a deploy that needs a saved server, an env file or a service now also needs read on that feature, and
|
|
102
|
+
prints which ones it cannot decrypt. In an existing vault the extra keys stop working at once, and the next admin login
|
|
103
|
+
replaces them, which re-encrypts those areas: commit `.pskit-vault/` afterwards.
|
|
104
|
+
|
|
105
|
+
### Fixed
|
|
106
|
+
- **Permission changes apply to accounts that are logged in.** A new permission is decrypted, and a revoked one's files
|
|
107
|
+
are deleted, within a few seconds in the studio and at the next CLI command. Revoked SSH keys and other decrypted files
|
|
108
|
+
used to stay on disk until logout, even after logging in again. Files with unsealed edits stay, and so do files another
|
|
109
|
+
account logged in to that folder may read.
|
|
110
|
+
|
|
111
|
+
## [2.13.0] - 2026-11-05
|
|
112
|
+
|
|
113
|
+
### Added
|
|
114
|
+
- **Dead-letter queues and replay.** `dlq` on a function in `pskit.yml` moves messages that keep failing to a dead-letter
|
|
115
|
+
queue after `max_retries`, on AWS, Azure, GCP and on premises. New commands: `pskit dlq list`, `inspect` and `replay`
|
|
116
|
+
(one message, or `--all`). See [dead-letter queues](docs/dead-letter-queues.md).
|
|
117
|
+
- **Paste an SSH private key when adding a server**, in the studio or with `pskit resources onprem servers add
|
|
118
|
+
--ssh-key-env` / `--ssh-key-stdin`, instead of pointing at a file. It is checked and saved in `.pskit/ssh/keys/`. In a
|
|
119
|
+
project with a vault it is encrypted, and only accounts with read on Servers, or a deploy permission, can decrypt it.
|
|
120
|
+
- **The audit log has pages**: in **Users & audit**, with `--offset` on `pskit vault audit`, and `offset` on the API.
|
|
121
|
+
|
|
122
|
+
### Changed
|
|
123
|
+
- **New servers start with the SSH user's home and every interface**: home path and data directory `/home/<user>` (`/root`
|
|
124
|
+
for root) and bind address `0.0.0.0`, in the studio and in `servers add`. Change them, or pass `""` to leave one unset.
|
|
125
|
+
**Check the server's firewall:** `0.0.0.0` makes the functions and services reachable from the network. Servers already
|
|
126
|
+
saved keep their settings.
|
|
127
|
+
|
|
128
|
+
### Fixed
|
|
129
|
+
- Saved SSH passwords and keys work in a teammate's clone at another path: `.pskit/onprem-servers.json` stores files under
|
|
130
|
+
`.pskit/ssh` relative to the project, and absolute paths written by another clone are corrected when read.
|
|
131
|
+
- Changing how a server logs in, or removing it, deletes the password or key pskit saved for it once nothing else uses it.
|
|
132
|
+
|
|
133
|
+
## [2.12.2] - 2026-11-05
|
|
134
|
+
|
|
135
|
+
### Fixed
|
|
136
|
+
- Screenshots and diagrams show in the description on PyPI. The README keeps relative image paths for GitHub and editors,
|
|
137
|
+
and the build turns them into full URLs for the package.
|
|
138
|
+
|
|
139
|
+
## [2.12.1] - 2026-11-05
|
|
140
|
+
|
|
141
|
+
### Changed
|
|
142
|
+
- **`pskit doctor` and Setup & credentials check Node.js and npm** for Node.js projects, including the version, and warn
|
|
143
|
+
when this Python has no pip. Terraform on Linux now shows real commands. A deploy that fails because pip is missing says
|
|
144
|
+
so and how to fix it. New [requirements page](docs/requirements.md) with install steps for Windows, macOS and Linux.
|
|
145
|
+
- **Documentation:** the README now walks through studio step by step. Every studio guide page and every on-prem service
|
|
146
|
+
page has screenshots, and the diagrams are images with Mermaid sources in `docs/images/diagrams/`.
|
|
147
|
+
|
|
148
|
+
### Security
|
|
149
|
+
- **The recovery code can be replaced**: `pskit vault rotate-recovery-code` or **Users & audit**. All encrypted data gets
|
|
150
|
+
new keys, so the old code stops working.
|
|
151
|
+
- **The `viewer` preset no longer decrypts anything.** It included read on Deployments, which opens Terraform state and
|
|
152
|
+
tokens. Accounts already created keep the permissions they have.
|
|
153
|
+
|
|
154
|
+
### Fixed
|
|
155
|
+
- `pskit --help` lists `pskit vault rotate-recovery-code`.
|
|
156
|
+
|
|
157
|
+
## [2.12.0] - 2026-11-05
|
|
158
|
+
|
|
159
|
+
### Added
|
|
160
|
+
- **Accounts, encrypted project data and an audit log** ([docs](docs/security-vault.md)), optional per project. The first
|
|
161
|
+
`pskit studio` start asks who will use the project. **Just me** (or `pskit studio --no-auth`) works as before: no login
|
|
162
|
+
and nothing encrypted. **A team** asks for an admin account and shows a master key and a recovery code once. `.env` files and `.pskit` settings are
|
|
163
|
+
encrypted (AES-256-GCM) into `.pskit-vault/`, which is safe to commit; they are re-encrypted after each save and the
|
|
164
|
+
plaintext is removed at logout. A new developer clones, enters the master key, username and password, and gets only
|
|
165
|
+
the areas their account may read. Admins set create, read, update and delete per feature. Every change, refusal,
|
|
166
|
+
login and deploy is logged. Saving `pskit.yml` is judged by what changes: creating, changing and deleting a function
|
|
167
|
+
(or workflow, or resource) are separate permissions. New commands: `pskit login`, `logout`, `whoami`, `pskit vault ...`.
|
|
168
|
+
|
|
169
|
+
### Changed
|
|
170
|
+
- In a project with a vault, `pskit studio` requires a login and CLI commands need `pskit login`, or `PSKIT_MASTER_KEY`,
|
|
171
|
+
`PSKIT_USER` and `PSKIT_PASSWORD` in scripts. Projects without a vault keep working from the CLI as before.
|
|
172
|
+
- `cryptography` is now a required dependency.
|
|
173
|
+
- Studio: **Where functions run** on the Deploy page lists every function with its deploy switch (enabled, disabled on
|
|
174
|
+
on premises, disabled everywhere), both with all functions on one target and split across servers. The section now
|
|
175
|
+
starts open.
|
|
176
|
+
- New projects also ignore `.env.*` in their `.gitignore`.
|
|
177
|
+
|
|
178
|
+
### Security
|
|
179
|
+
- **The master key is no longer saved on the computer.** It was kept as plaintext in `~/.pskit/vault-keys/`, so a username
|
|
180
|
+
and password were enough to decrypt everything on that computer. Every login now asks for the master key, and
|
|
181
|
+
`--no-remember` is gone. The old file is deleted at your next login. **Action needed:** keep the master key in a
|
|
182
|
+
password manager, because a lost key cannot be replaced by the recovery code.
|
|
183
|
+
- **On-prem admin API no longer open on the network.** With no `admin_token`, a host on `0.0.0.0` (set by hand, by
|
|
184
|
+
`method: docker` or by placement groups) accepted anyone. pskit now generates a token for these hosts
|
|
185
|
+
(`.pskit/onprem-<stage>/admin-token`), and a host started on a network address with no token refuses to start.
|
|
186
|
+
**Action needed:** callers outside pskit must send the token as `x-pskit-token` / `PSKIT_ADMIN_TOKEN`
|
|
187
|
+
(`pskit client info` prints it). Re-create SMTP servers so they send it too.
|
|
188
|
+
- **On-prem object keys could leave the bucket folder.** A double-encoded key (`%252E%252E%252F...`) wrote outside the
|
|
189
|
+
bucket, and the host's own code lives under the data directory. Keys are now decoded once and the resolved path is
|
|
190
|
+
checked. A key containing `%` is now stored literally, instead of being decoded a second time.
|
|
191
|
+
- A loopback host without a token refuses requests from web pages on other sites and DNS rebinding.
|
|
192
|
+
- `GET /__pskit/health` returns only `{"ok": true}` without the token.
|
|
193
|
+
- `pskit_host.json`, `host.env` and the deploy record are mode `0600` (they were `0644`).
|
|
194
|
+
- Browser terminals no longer discard SSH host keys, so a changed key (a man in the middle) is refused.
|
|
195
|
+
- Tokens are compared in constant time, and the AWS access key id must equal the token rather than merely appear in
|
|
196
|
+
the header. The SigV4 signature is still not verified; this is now documented.
|
|
197
|
+
- The Python Secrets Manager uses the `cryptography` package for AES-GCM and ChaCha20-Poly1305 when it is installed.
|
|
198
|
+
|
|
199
|
+
### Fixed
|
|
200
|
+
- On premises: disabling a function listed in a placement group no longer fails validation with `no function`. It stays
|
|
201
|
+
listed, is not deployed, and returns to its group when enabled again.
|
|
202
|
+
- `test_docs_index_is_up_to_date` and `build_hana_docs_index.py --check` compare content, not gzip bytes, which differ
|
|
203
|
+
between zlib builds.
|
|
204
|
+
|
|
205
|
+
### CI
|
|
206
|
+
- Python 3.9 runs on `ubuntu-24.04` (`ubuntu-latest` is 26.04, which has no 3.9 build). Pushes to `dev` run CI. Actions
|
|
207
|
+
moved to their Node 24 releases.
|
|
208
|
+
|
|
209
|
+
## [2.11.1] - 2026-11-03
|
|
210
|
+
|
|
211
|
+
### Added
|
|
212
|
+
- **Structured end-to-end documentation** (about 125 new pages, every task both in studio and as terminal commands):
|
|
213
|
+
`docs/guide/` (concepts and one full application built from the terminal, in studio, and on premises with a
|
|
214
|
+
cluster, load balancer and replicated database), `docs/studio-guide/` (every studio page, button and dialog),
|
|
215
|
+
`docs/functions/`, `docs/triggers/` (one page per trigger), `docs/deployment/` (deployment types, stages, deploy /
|
|
216
|
+
remove, workflows, logs, monitoring, settings), `docs/onprem/` (servers, software, every catalog service, resources,
|
|
217
|
+
cloud resources on premises, the AWS-compatible S3 and Secrets Manager servers in Python and Node.js, Swarm / k3s /
|
|
218
|
+
Nomad scaling, load balancers, database replication, network map, firewall, placement) and `docs/providers/<cloud>/`.
|
|
219
|
+
- **Hana answers from the docs**: before the model answers, studio runs `search_docs` with the message and passes the
|
|
220
|
+
3 best sections; a new system-message line (also in the training data) tells her to answer from them, cite them and
|
|
221
|
+
say when the docs don't cover it. The search now covers every `docs/` section (`studio/hana/docs.jsonl.gz`, rebuilt
|
|
222
|
+
with `python scripts/build_hana_docs_index.py`; a test fails when it is out of date).
|
|
223
|
+
|
|
224
|
+
### Changed
|
|
225
|
+
- The repository moved to https://github.com/kavion-ai/py-serverless-kit: project URLs, README links, the security
|
|
226
|
+
advisory link, the `pskit.yml` header studio writes and the PyPI trusted-publisher settings now use it.
|
|
227
|
+
- The README and the docs index no longer link the PyPI release guides; they stay in `deploy_docs/`.
|
|
228
|
+
|
|
229
|
+
- Hana now starts with **Studio actions answer first (then the model)** checked. Choosing *Hana's model answers
|
|
230
|
+
first* in the menu is remembered in the browser.
|
|
231
|
+
|
|
232
|
+
### Fixed
|
|
233
|
+
- Hana searched the docs before every answer, even for "hi" or "thanks". A router (`studio/hana/router.py`) now
|
|
234
|
+
decides first: small talk skips the search, pskit questions search at once, and only messages the rules cannot
|
|
235
|
+
place get a tiny DOCS/CHAT call to the model (on failure it searches to be safe). The `ROUTER` log line says
|
|
236
|
+
which way it went and why.
|
|
237
|
+
- Hana's *Create on-prem service* card had no user or password fields, so a database always got the default user
|
|
238
|
+
and a generated password. The card now has optional **User** and **Password** fields, as in Resources > On-prem
|
|
239
|
+
services (empty: the default user and a strong random password; services without a login say so instead).
|
|
240
|
+
- Hana's *Deploy this project* card (on premises) could only pick one machine. It now has the Deploy page's
|
|
241
|
+
**Where functions run** editor: *All functions on one target* or *Split functions across servers* (groups of
|
|
242
|
+
functions, or one function per group, each on its own server or cluster). Pending edits are saved to `pskit.yml`
|
|
243
|
+
before the deploy starts, and with every group on its own target the card shows the groups instead of *Run on*.
|
|
244
|
+
|
|
245
|
+
## [2.11.0] - 2026-11-02
|
|
246
|
+
|
|
247
|
+
### Added
|
|
248
|
+
- **Hana asks before she creates**: new functions can each be **their own app** (`functions/<name>/` with its own
|
|
249
|
+
`requirements.txt`) or go into an existing module, and Hana asks which. A name that is already taken gets
|
|
250
|
+
update / another name / skip (functions), replace / another name (resources), or a free name and a note
|
|
251
|
+
(services, clusters, load balancers), instead of being skipped or renamed silently. "make step01 and step02
|
|
252
|
+
separate apps" moves existing functions into their own apps and deletes the shared file once nothing uses it.
|
|
253
|
+
Studio answers first when it has a card that changes the project, a short answer to studio's own question
|
|
254
|
+
("Which function should I remove?" → "step01, step02") is understood, and a model answer that claims a change
|
|
255
|
+
with no file written is marked as such.
|
|
256
|
+
- **Hana runs terminal commands** (`run_command`): in the project folder or on a saved server over SSH, after you
|
|
257
|
+
click **Run** on each command (also in Auto-approve); the output goes back to her and she answers from it.
|
|
258
|
+
Commands that wipe or stop a machine are refused. The tool and a system-prompt rule are in the runtime prompt and
|
|
259
|
+
the training data (`ai-agent/training/tools/task_common.py`); until the model is retrained, studio turns a
|
|
260
|
+
command she writes in a code block into the same **Run** card when you asked for a result. Studio's answers from
|
|
261
|
+
your real settings (servers, services, clusters, load balancers, functions) now come before the model's. The end
|
|
262
|
+
of the system message tells her she has a terminal and names the saved servers. Studio proposes the command
|
|
263
|
+
itself for "install docker on VM_01_2cpu" (any catalog runtime; part of a server's name is enough), "run
|
|
264
|
+
`docker ps` on app-2", "execute pskit validate" and "can you execute it", and the model answers from the output.
|
|
265
|
+
- **Hana, the studio's AI assistant** (the avatar at the bottom right of every page, Ctrl+I): a floating chat.
|
|
266
|
+
Hana answers pskit questions with how-to steps for studio, the terminal and code, and changes the project: she
|
|
267
|
+
reads it, shows a plan to **Approve** / **Reject** (or runs it at once in *Auto-approve*), edits `pskit.yml`
|
|
268
|
+
(backed up first) and handler files, and checks the result with `pskit validate` and a local invoke. She never
|
|
269
|
+
deploys or removes. The model (1.5B, fine-tuned on pskit, by Asif Khan) runs locally: studio installs the
|
|
270
|
+
`ak2311581/hana-pskit` Docker image on this machine or on a saved server (through an SSH tunnel), or connects to
|
|
271
|
+
any OpenAI-compatible URL. Servers and on-prem services: from what you paste (IP, user, `.pem` path, `ssh`
|
|
272
|
+
command) the chat fills in an **Add server** or **Create on-prem service** card, and studio runs it when you click.
|
|
273
|
+
Chats are saved in `.pskit/studio/hana/`. See [docs/assistant.md](docs/assistant.md).
|
|
274
|
+
- `pskit studio --ailogs[=true]` (or `PSKIT_HANA_AILOGS=1`) prints every step of Hana's chats in the terminal:
|
|
275
|
+
messages, model requests and answers, tool calls and results, plans and cards (passwords stay hidden).
|
|
276
|
+
|
|
277
|
+
## [2.10.0] - 2026-10-30
|
|
278
|
+
|
|
279
|
+
### Added
|
|
280
|
+
- On-prem **server usage**: the *Servers* list has a **Used in** column. For each saved server it lists every place
|
|
281
|
+
that names it, with the functions behind each: the deploy target in `pskit.yml`, the stage last deployed there, a
|
|
282
|
+
function group (`placement`), a cluster (master / joined server) and the cluster's load balancer, a named load
|
|
283
|
+
balancer, a service or a replicated database member (primary, read replica, its load balancer), and installed
|
|
284
|
+
software. Servers nothing names say *not used anywhere*. **Forget** shows the list before asking (and says when a
|
|
285
|
+
cluster still holds the server). CLI: `pskit resources onprem servers usage [NAME] [--json]`.
|
|
286
|
+
- A **Network map** page in the studio sidebar: an SVG diagram of every server and the connections it accepts
|
|
287
|
+
(inbound) and opens (outbound), with the port, why it is needed and whether it is required, needed for a feature
|
|
288
|
+
or optional. Click a server for its inbound / outbound table and where it is used; filter by level and hide
|
|
289
|
+
unused servers. Built from the same rules as `pskit firewall`, from local files only (no SSH).
|
|
290
|
+
- `GET /api/onprem-usage` and `GET /api/resource-bindings` in the studio API; new module `core/onprem_usage.py`.
|
|
291
|
+
|
|
292
|
+
### Fixed
|
|
293
|
+
- *Resources → Bound to* always said "all functions" for a resource without a `functions:` list. It now shows the
|
|
294
|
+
functions that really use it: a trigger on it (⚡) or handler code that calls `resource("key")` / reads
|
|
295
|
+
`PSKIT_RESOURCE_<KEY>_*`, plus how many functions get its variables. With `functions:` the listed ones show, the
|
|
296
|
+
ones that use it highlighted.
|
|
297
|
+
|
|
298
|
+
## [2.9.0] - 2026-10-30
|
|
299
|
+
|
|
300
|
+
### Added
|
|
301
|
+
- On-prem **live monitoring**: a service's *Details* has a *Live monitoring* switch. While it is on, the studio shows
|
|
302
|
+
every 5 seconds each container's CPU, memory and the disk holding its data (primary, replicas and load balancer of
|
|
303
|
+
a replicated database), the open connections, the data size and each replica's lag. Nothing is measured while it
|
|
304
|
+
is off. CLI: `pskit resources onprem monitor KEY [--watch N]`.
|
|
305
|
+
- **Alerts** for on-prem services (optional when creating a database, editable in *Details*): CPU, memory and disk
|
|
306
|
+
percent, replica lag, a container down. They run a function of the project through the deployed host and / or
|
|
307
|
+
POST a webhook (Slack, Teams, any URL), at most once per cooldown. *Create a new function* adds `<key>-alert` to
|
|
308
|
+
`pskit.yml` with a handler stub. The studio checks every minute while it runs; `pskit resources onprem alerts KEY
|
|
309
|
+
--check` does it from cron, `--test` sends a test alert, and the history is kept per service.
|
|
310
|
+
- **Import data** when creating a database: a `.sql`, `.sql.gz`, `.dump` (PostgreSQL) or `.archive` (MongoDB) file
|
|
311
|
+
from this machine is loaded once it is up (into the primary before the replicas copy it). CLI `--import FILE`.
|
|
312
|
+
- **Servers**: a check mark per saved server (its SSH port is probed in parallel when the list opens, *Re-check*
|
|
313
|
+
again) and a **Live** switch with CPU, RAM and disk use. CLI `pskit resources onprem servers check` and
|
|
314
|
+
`servers top NAME [--watch N]`.
|
|
315
|
+
- **Backup** asks where to save: `.pskit/backups` or any folder picked on this machine (remembered). CLI `--dir`.
|
|
316
|
+
- A **⇅ Settings** button in the studio header imports and exports the project's `.pskit` settings, now optionally
|
|
317
|
+
with `pskit.yml` (on by default there; CLI `pskit settings export --with-config`). An import that brings
|
|
318
|
+
`pskit.yml` reloads the studio.
|
|
319
|
+
|
|
320
|
+
### Fixed
|
|
321
|
+
- `runtime_js/package.json` still said 2.7.0 in the 2.8.0 release; both version files now agree again.
|
|
322
|
+
|
|
323
|
+
## [2.8.0] - 2026-10-30
|
|
324
|
+
|
|
325
|
+
### Added
|
|
326
|
+
- On premises, a scaling cluster can be **removed together with what pskit installed**, master included:
|
|
327
|
+
`pskit cluster remove NAME --uninstall` (studio: **Remove** on the master's row, which used to have no button)
|
|
328
|
+
stops the deployments, removes the cluster's load balancer and its routes on named load balancers, uninstalls the
|
|
329
|
+
agent from every joined server and then Docker Swarm / k3s / Nomad from the master, deletes the deployments'
|
|
330
|
+
images and the `pskit-cluster` scripts folder, and forgets the cluster. Docker and the saved servers stay; the main
|
|
331
|
+
replicas' data stays too unless `--delete-data` (*Uninstall and delete data*) is given. An unreachable server only
|
|
332
|
+
warns. Plain `pskit cluster remove` still only forgets the cluster, and `pskit cluster leave` on the master now
|
|
333
|
+
points to `--uninstall`.
|
|
334
|
+
|
|
335
|
+
## [2.7.0] - 2026-10-30
|
|
336
|
+
|
|
337
|
+
### Added
|
|
338
|
+
- On premises, a database is created on a **single server** or as a **primary with read replicas** (horizontal
|
|
339
|
+
scaling): pick the server that takes the writes, the servers that serve reads, *asynchronous* or *synchronous*
|
|
340
|
+
replication, and optionally a server for a load balancer that gives the functions one address. PostgreSQL uses
|
|
341
|
+
streaming replication behind pgpool-II, MySQL and MariaDB use GTID replication (semi-synchronous for *sync*) behind
|
|
342
|
+
ProxySQL, and MongoDB runs as a replica set (write concern `majority` for *sync*) that the driver routes itself.
|
|
343
|
+
The studio's create form draws the topology (an SVG) as you pick, and **Details** shows each member's state and
|
|
344
|
+
lag with **+ Add read replica** / **Remove**. CLI: `pskit resources onprem create KEY --service postgres
|
|
345
|
+
--primary db1 --replica db2 --replica db3 --balancer lb1 --sync sync` and `pskit resources onprem replicas
|
|
346
|
+
list | add | remove`. `.env.onprem` gets `PSKIT_<KEY>_WRITE_URL` and `PSKIT_<KEY>_READ_URLS` next to `URL`, and the
|
|
347
|
+
job prints the firewall rules between the members. `--primary local --replica local` runs every member on this
|
|
348
|
+
machine to try it out.
|
|
349
|
+
|
|
350
|
+
### Changed
|
|
351
|
+
- The studio no longer offers *Scaling cluster* as a place for a database; *Scaling → Primary + read replicas*
|
|
352
|
+
replaces it (databases created on a cluster server before keep working).
|
|
353
|
+
|
|
354
|
+
## [2.6.1] - 2026-10-30
|
|
355
|
+
|
|
356
|
+
### Fixed
|
|
357
|
+
- On premises, a load balancer attached to one cluster also served the project's functions placed on other clusters
|
|
358
|
+
and servers: attaching it turned the placement gateway on for every group, so the attached cluster's servers passed
|
|
359
|
+
every other group's routes on. Now a group's servers pass on only the routes of groups behind the same load
|
|
360
|
+
balancer (`options.balancer` and an explicit `placement.gateway` keep their behaviour). Run `pskit deploy` again.
|
|
361
|
+
|
|
362
|
+
## [2.6.0] - 2026-10-28
|
|
363
|
+
|
|
364
|
+
### Added
|
|
365
|
+
- Share links with a custom expiry: the S3 compatible server's console (`aws/s3/ui`) and the pskit studio's bucket
|
|
366
|
+
browser take any time from 1 second to 7 days (seconds, minutes, hours or days) next to the presets, and show when
|
|
367
|
+
the link expires. A time outside that range is refused with a clear message instead of being silently changed.
|
|
368
|
+
- The S3 console's *Block public access* card has a *Block all (make private)* button.
|
|
369
|
+
|
|
370
|
+
### Fixed
|
|
371
|
+
- Studio *Make private* left a bucket readable without keys: it only deleted the bucket policy, so objects uploaded
|
|
372
|
+
with a `public-read` ACL (or a public bucket ACL) were still served, and the badge said "private". It now also
|
|
373
|
+
resets the bucket ACL to `private` and turns on all four *block public access* settings, which ignore public
|
|
374
|
+
object ACLs and policies; services without these APIs (MinIO) keep the policy-only behaviour. The badge reads
|
|
375
|
+
"private (public access blocked)" once nothing is public. *Make public (read)* turns the block off first so the
|
|
376
|
+
public policy is accepted.
|
|
377
|
+
- The S3 compatible server (Python) answered a non-numeric console share expiry with a server error; it is now a
|
|
378
|
+
`400 InvalidArgument`.
|
|
379
|
+
- On premises, a load balancer sent every request of a Kubernetes (k3s) cluster to one server, while a Swarm cluster
|
|
380
|
+
on the same load balancer was spread correctly. Two causes:
|
|
381
|
+
- The load balancer reused its connections to the servers (`keepalive`), and a k3s node picks a pod once per
|
|
382
|
+
connection (ServiceLB / kube-proxy), so every request stuck to the pod those few connections first reached.
|
|
383
|
+
Routes to Kubernetes servers now open a new connection per request, so each one is balanced again. Swarm and
|
|
384
|
+
Nomad routes keep reusing connections.
|
|
385
|
+
- Kubernetes could put both web replicas on one server (its default lets up to 3 share one). Web pods now spread
|
|
386
|
+
one per server first (`topologySpreadConstraints`, `maxSkew: 1`).
|
|
387
|
+
|
|
388
|
+
Run `pskit deploy` again on the Kubernetes cluster (or `pskit lb sync <name>`) to rewrite its routes and spread
|
|
389
|
+
its pods.
|
|
390
|
+
|
|
391
|
+
## [2.5.0] - 2026-10-28
|
|
392
|
+
|
|
393
|
+
### Fixed
|
|
394
|
+
- On premises, events stopped once the functions moved: after their server was removed, or they were deployed to
|
|
395
|
+
another server or cluster, the services kept the address of the old place. Now every `pskit deploy` (CLI and
|
|
396
|
+
studio) makes the services the functions use follow them:
|
|
397
|
+
- **SMTP**: an `smtp` service sends each mail to the functions at the URL it was created with, so mail still
|
|
398
|
+
arrived but no function ran (senders got `451` and kept retrying). After the deploy, every SMTP server the
|
|
399
|
+
deployed functions have `smtp` triggers on is pointed at where they run now: its container starts again with
|
|
400
|
+
the new URL (the installed packages stay in the volume), and mail the senders retry is delivered.
|
|
401
|
+
- **Queues, streams, topics, buckets, databases, caches, secret stores**: a service on a cluster server was reached
|
|
402
|
+
at its cluster address, which only works from that cluster. Before the deploy, pskit switches the address in the
|
|
403
|
+
env file (and the services state) to the server's own address when the functions left the cluster, or back to
|
|
404
|
+
the cluster address when they run on it, so the deploy ships the right one.
|
|
405
|
+
- The deploy warns, naming the fix, when a service cannot be reached from the functions' new place: its server
|
|
406
|
+
was removed, it runs on this machine or listens on `127.0.0.1` only, or its container has the address built in
|
|
407
|
+
(Kafka, Redpanda, fake-gcs: create it again with the same key). It also prints the firewall rules the new
|
|
408
|
+
function servers need to reach each service.
|
|
409
|
+
- An address or `functions_url` typed in when creating a service is never changed. Services created before this
|
|
410
|
+
release follow the functions when their address is one pskit picks. Run `pskit deploy` again to fix an existing
|
|
411
|
+
project.
|
|
412
|
+
|
|
413
|
+
## [2.4.0] - 2026-10-28
|
|
414
|
+
|
|
415
|
+
### Added
|
|
416
|
+
- The AWS Secrets Manager compatible servers (`aws/secretsmanager`, Python and Node.js) encrypt secret values at
|
|
417
|
+
rest with envelope encryption: each version gets its own data key, wrapped by a master key (`SM_MASTER_KEY`,
|
|
418
|
+
more with `SM_MASTER_KEYS`, picked per secret by `KmsKeyId`). `SM_ENCRYPTION` chooses AES-256-GCM (default),
|
|
419
|
+
ChaCha20-Poly1305 or AES-256-CBC + HMAC-SHA256. Clients (boto3, the AWS SDKs, the CLI, `get_secret()`) don't
|
|
420
|
+
change. A plain data file is encrypted on the first start with a key; `SM_MASTER_KEY_ID` rotates the master key
|
|
421
|
+
(rewraps the data keys on start, or with `--rewrap`). The Python server stays standard-library only.
|
|
422
|
+
- On premises, the `secretsmanager` / `secretsmanager-node` services generate a master key when created, keep it in
|
|
423
|
+
the env file as `<PREFIX>_MASTER_KEY` and reuse it on re-create. Re-create an existing service to encrypt its data.
|
|
424
|
+
|
|
425
|
+
## [2.3.6] - 2026-10-28
|
|
426
|
+
|
|
427
|
+
### Fixed
|
|
428
|
+
- On premises, a project whose placement groups run on two scaling clusters (Swarm, Kubernetes / k3s or Nomad)
|
|
429
|
+
attached to one load balancer got a route only to the first cluster: the second cluster's deployment
|
|
430
|
+
(`pskit-<service>-<stage>-<group>`) was skipped as if the project had set its own route, and requests for its
|
|
431
|
+
functions reached the first cluster's servers, which answered `404 ... runs on group X, not on this server`.
|
|
432
|
+
Now the project gets one route, `/<service>/`, to the servers of every attached cluster that runs one of its
|
|
433
|
+
groups (each on its own port), kept up to date on deploy, remove, join, leave, attach and detach. The same
|
|
434
|
+
applies to a project's own `options.balancer` route.
|
|
435
|
+
- `placement.gateway` is now on by default when a group's cluster has a load balancer or is attached to one, and
|
|
436
|
+
turns it on for **every** group (not only the default one): a server passes the routes of the other groups'
|
|
437
|
+
functions on to them, so any server behind the load balancer answers every route. Run `pskit deploy` again.
|
|
438
|
+
- Studio, **Logs**: a stage on a scaling cluster, or split over placement groups, no longer shows a *Server* picker
|
|
439
|
+
(it read as if the logs came from that one server). It shows the source instead, every replica of the cluster or
|
|
440
|
+
every group and where it runs, and explains that a line's `group` / `node` fields say where it ran.
|
|
441
|
+
- Studio, **Deploy**: with placement whose default group has its own *Runs on*, the *Run on* picker at the top is
|
|
442
|
+
replaced by a summary of each group and its target. Before, it showed a machine or cluster that could differ from
|
|
443
|
+
the groups below, and deploying passed it as `--server` / `--cluster`, moving the default group there.
|
|
444
|
+
- Studio: the *One URL* (`placement.gateway`) checkbox says every group passes routes on and shows it on by default
|
|
445
|
+
when a group's cluster is behind a load balancer.
|
|
446
|
+
|
|
447
|
+
## [2.3.5] - 2026-10-27
|
|
448
|
+
|
|
449
|
+
### Added
|
|
450
|
+
- On premises, scaling clusters have a **Master serves requests** switch (studio: *New cluster* form and the cluster
|
|
451
|
+
page; CLI: `pskit cluster create ... --master-serves|--no-master-serves`, `pskit cluster set NAME
|
|
452
|
+
--master-serves|--no-master-serves`). On, load balancers spread requests over every server, the master included.
|
|
453
|
+
Off, the master is only a `backup` there, used while every other server is down, and Swarm / k3s keep web
|
|
454
|
+
replicas off it while another server can run them. Before, a Nomad cluster's master stayed idle until every
|
|
455
|
+
joined server was down. Defaults keep the old behaviour (off on Nomad, on on Swarm and k3s). Changing it updates
|
|
456
|
+
the load balancers at once; Swarm / k3s web replicas follow at the next `pskit deploy`.
|
|
457
|
+
- On premises, a storage event can set both `resource` and `bucket`: the resource is the storage service (driver,
|
|
458
|
+
endpoint, keys) and `bucket` is any bucket on it, e.g. `storage: {resource: minio, bucket: invoices}`. The studio's
|
|
459
|
+
storage trigger form picks the *Storage service* and takes the bucket name. Cloud providers reject the combination.
|
|
460
|
+
- S3 presets `wasabi`, `b2` (Backblaze), `linode` (Akamai) and `scaleway`.
|
|
461
|
+
|
|
462
|
+
### Fixed
|
|
463
|
+
- S3-compatible storage: the driver follows a bucket that lives in another region (AWS's 301 / 400), falls back to
|
|
464
|
+
ListObjects on stores without ListObjectsV2, uses path-style for dotted bucket names over HTTPS, and with
|
|
465
|
+
`create_bucket` sends the region as `LocationConstraint` outside us-east-1 and accepts a bucket the keys may use
|
|
466
|
+
but not create.
|
|
467
|
+
|
|
468
|
+
## [2.3.4] - 2026-10-27
|
|
469
|
+
|
|
470
|
+
### Fixed
|
|
471
|
+
- On premises, calling a workflow's first task function on its own did not run the workflow. A workflow such as
|
|
472
|
+
`step01 -> step02 -> step3` now starts when `step01` runs from any trigger (its HTTP route, `invoke()`,
|
|
473
|
+
`pskit trigger`, a schedule, a queue, ...). The run takes the call's input as the workflow input and `step01`'s
|
|
474
|
+
result as the first state's result, so `step01` does not run twice. The run is tracked like any other execution,
|
|
475
|
+
and an HTTP answer carries its id in `x-pskit-execution-id`. A failed call (an exception, or HTTP status >= 400)
|
|
476
|
+
starts nothing. When placement puts the function on another group's server, the run still starts and runs on
|
|
477
|
+
the default group. Set `options.start_on_entry: false` on a workflow to turn this off.
|
|
478
|
+
|
|
479
|
+
## [2.3.3] - 2026-10-27
|
|
480
|
+
|
|
481
|
+
### Fixed
|
|
482
|
+
- Workflows failed at a step whose function was created in the studio as an HTTP function: its stub read
|
|
483
|
+
`event.http.query`, and a workflow step (or `invoke()`) has no HTTP request (`AttributeError: 'NoneType' object
|
|
484
|
+
has no attribute 'query'`). New HTTP stubs also work as a workflow step or `invoke()` (`event.data` is the input).
|
|
485
|
+
- The studio's **Test** and `pskit trigger` sent the HTTP test of a function placed on another group to the
|
|
486
|
+
default group's server, which answers only its own routes (404). It now goes to the server of the function's
|
|
487
|
+
group.
|
|
488
|
+
- `pskit trigger --direct` and the studio's direct invoke on premises gave the function
|
|
489
|
+
`{"__pskit": "invoke", "data": ...}` instead of the data.
|
|
490
|
+
- A function that raised during `pskit trigger --direct` was reported as `HostUnavailable ... answered HTTP 500`;
|
|
491
|
+
it now says the function raised `<ErrorType>: <message>` and that the host is up.
|
|
492
|
+
|
|
493
|
+
## [2.3.2] - 2026-10-27
|
|
494
|
+
|
|
495
|
+
### Fixed
|
|
496
|
+
- Placement: a function's code was on every server. Functions whose handlers share a code file
|
|
497
|
+
(`app/handlers.py`) each got the whole file on every group's server. Each group's copy now holds only its own
|
|
498
|
+
functions' handlers (the others, and the imports only they used, are removed from that group's bundle; the
|
|
499
|
+
source is not changed). `pskit_host.json` lists what was removed (`stripped`).
|
|
500
|
+
- Placement: every server answered every route by passing other groups' routes on, so
|
|
501
|
+
`http://<any server>/items/1` worked. Each server now answers only the routes of the functions it runs, and a
|
|
502
|
+
route of another group gets a `404` naming that group and its URL.
|
|
503
|
+
|
|
504
|
+
### Added
|
|
505
|
+
- `provider.options.placement.gateway: true`: the default group answers every route and passes other groups'
|
|
506
|
+
routes on (one URL for the project). On by default with `options.balancer`, whose route now points at the
|
|
507
|
+
default group only.
|
|
508
|
+
- The studio's "Where functions run": every function can be unticked (unticking in the default group moves it to a
|
|
509
|
+
group you pick), All here / None buttons, and the default group is explained.
|
|
510
|
+
|
|
511
|
+
### Changed
|
|
512
|
+
- Requirements with placement are documented as global plus per function: each server installs the project's
|
|
513
|
+
`requirements.txt` and those of its own functions' folders only.
|
|
514
|
+
|
|
515
|
+
## [2.3.1] - 2026-10-27
|
|
516
|
+
|
|
517
|
+
### Fixed
|
|
518
|
+
- Placement: a group other than the default one kept its data beside the server's `data_dir`
|
|
519
|
+
(`/home/azureuser-test-02`), which the SSH user cannot create when `data_dir` is the home folder, so its host
|
|
520
|
+
crashed at start-up ("on-prem host did not become healthy"). Groups now keep their data inside it
|
|
521
|
+
(`<data_dir>/groups/<group>`).
|
|
522
|
+
|
|
523
|
+
### Added
|
|
524
|
+
- `pskit function split NAME... | --all [--dry-run]` (and the studio's **Own folder** action) moves a function
|
|
525
|
+
out of a code file it shares with others into `functions/<name>/handler.py` with its own `requirements.txt`: the
|
|
526
|
+
helpers and imports it uses are copied, relative imports made absolute, the project requirements its imports name
|
|
527
|
+
copied, and its handler in `pskit.yml` updated (comments kept). Validation warns when functions of different
|
|
528
|
+
placement groups share a code file.
|
|
529
|
+
- The studio's function editor picks the group a function runs on, or creates one (server, cluster or this
|
|
530
|
+
machine, and port). On-prem deploys show their output as steps with one card per group host (its own lines, the
|
|
531
|
+
error and the host's log), then the load balancer, firewall rules and endpoints. The raw log stays one tab away.
|
|
532
|
+
- dashboard-ui unit tests (`npm test`: deploy log parser, placement edits), run in CI.
|
|
533
|
+
|
|
534
|
+
### Changed
|
|
535
|
+
- A host that fails at start-up fails the deploy as soon as it exits (not after 30 s), and the deploy output shows
|
|
536
|
+
the end of its `host.log`.
|
|
537
|
+
|
|
538
|
+
## [2.3.0] - 2026-10-27
|
|
539
|
+
|
|
540
|
+
### Added
|
|
541
|
+
- **Six load balancing algorithms** on premises: round robin, sticky round robin (cookie), weighted round robin,
|
|
542
|
+
IP hash (static) and least connections, least time (dynamic). Load balancers now run OpenResty, which provides
|
|
543
|
+
sticky sessions (a hashed first-request cookie) and least time (`balancer_by_lua` with a moving average of each
|
|
544
|
+
server's response time) that open-source nginx lacks. `pskit lb algorithms` and the studio explain each one, with
|
|
545
|
+
pros, cons and an animation. Upstreams share state across worker processes (`zone`), so round robin and least
|
|
546
|
+
connections are exact.
|
|
547
|
+
- **Named load balancers shared by projects and clusters**: `pskit lb create edge --server lb1`, then
|
|
548
|
+
`provider.options.balancer: edge` in any project (`http://lb1/<service>/`, or `{name, path, algorithm, weights}`)
|
|
549
|
+
or `pskit lb attach edge --cluster prod`. Routes are kept on the load balancer server, so projects in other
|
|
550
|
+
folders or on other machines share it without overwriting each other (`flock`, `nginx -t` before every reload).
|
|
551
|
+
New studio page **Load balancers**. See `docs/load-balancers.md`.
|
|
552
|
+
- **Placement**: `provider.options.placement` runs groups of functions on different servers, clusters or this
|
|
553
|
+
machine. Each group is its own host with only its functions; `invoke()`, HTTP routes, workflow steps, built-in
|
|
554
|
+
queues, buckets, topics and SMTP triggers reach the group that owns them, workflows run on the default group and
|
|
555
|
+
every group's logs reach it. See `docs/placement.md`.
|
|
556
|
+
- **Function sub-projects**: a function in its own folder with its own `requirements.txt` / `package.json`
|
|
557
|
+
(`functions/<name>/`). Its requirements go into the bundle on every cloud; with placement each server installs
|
|
558
|
+
only those of its functions. Node.js sub-projects get their own `node_modules`. The studio creates new functions
|
|
559
|
+
this way.
|
|
560
|
+
- `pskit cluster balancer set` takes `--algorithm` and `--weight SERVER=N`.
|
|
561
|
+
- **Firewall rules, live**: every on-prem step (cluster create / join, deploy, `pskit lb create` / `attach`, a
|
|
562
|
+
project's load balancer route, `pskit resources onprem create`) prints the inbound / outbound ports it needs on
|
|
563
|
+
each server, by name and address, with `ufw` commands. `pskit firewall` (and the studio's Firewall panel) lists
|
|
564
|
+
them for the whole project. Every role and port: `docs/onprem-network.md`.
|
|
565
|
+
|
|
566
|
+
### Changed
|
|
567
|
+
- A cluster's own load balancer runs `openresty/openresty:1.27.1.2-alpine` instead of `nginx:1.27-alpine`; it is
|
|
568
|
+
replaced on its next update (deploy, join, leave or `pskit cluster balancer sync`).
|
|
569
|
+
|
|
570
|
+
### Fixed
|
|
571
|
+
- The generated `onprem_ctl.py` swaps `staging` into `app` with extended paths on Windows, so a redeploy no longer
|
|
572
|
+
fails on deep vendored paths (260-character limit).
|
|
573
|
+
|
|
574
|
+
## [2.2.1] - 2026-10-26
|
|
575
|
+
|
|
576
|
+
### Fixed
|
|
577
|
+
- **TypeScript 7**: the generated `tsconfig.pskit.json`, the `pskit init` template and `examples/21-nodejs-typescript`
|
|
578
|
+
no longer set `baseUrl` or `moduleResolution: "node"`, which TypeScript 7 removed (`TS5102`, `TS5108`, `TS5090`).
|
|
579
|
+
- **On-premises scripts** add `/usr/local/bin`, `/usr/bin` and the other system dirs *after* the server's `PATH`
|
|
580
|
+
instead of before it, so a `docker` (or other tool) the server's `PATH` chooses is no longer overridden.
|
|
581
|
+
- **Workflow timeouts**: a `wait` cut short by the workflow's `timeout` could wake a moment before the deadline
|
|
582
|
+
(timers fire early) and then finish the wait instead of failing with `States.Timeout`. The Node.js and Python
|
|
583
|
+
engines now keep waiting until the end has really passed.
|
|
584
|
+
- **Swarm join** counts the other nodes and services without the padding BSD `wc` adds, so the "manages another
|
|
585
|
+
swarm" message shows plain numbers.
|
|
586
|
+
- **CI**: `pytest-timeout` (dev dependency) fails a hung test after 5 minutes with its stack trace, and test jobs
|
|
587
|
+
stop after 30 minutes.
|
|
588
|
+
- **CI**: the macOS tests run weekly and from the "Run workflow" button instead of on every push / PR (macOS
|
|
589
|
+
runners are often queued), and a new push cancels the older run of the same branch.
|
|
590
|
+
|
|
591
|
+
## [2.2.0] - 2026-10-26
|
|
592
|
+
|
|
593
|
+
### Added
|
|
594
|
+
- **Amazon S3 compatible server** in `aws/s3`, in Python (standard library only) and Node.js (no npm packages), with
|
|
595
|
+
a Dockerfile for each, a `docker-compose.yml` and one shared web console (`ui/index.html`, served at `/ui/`).
|
|
596
|
+
boto3, the AWS SDKs, the AWS CLI (`aws s3` and `s3api`), rclone, s3cmd and pskit's `s3` driver work unchanged
|
|
597
|
+
through the endpoint. Every request is checked with AWS Signature Version 4 (header, presigned URLs,
|
|
598
|
+
`aws-chunked` streaming uploads with chunk and trailer signatures, browser POST policies) or Version 2.
|
|
599
|
+
- Buckets: create / delete / head / list (paging), location, versioning (Enabled / Suspended, `null` versions,
|
|
600
|
+
delete markers), tags, bucket policies (statements for `Principal: "*"` decide what unsigned requests may do),
|
|
601
|
+
canned and grant ACLs, block public access, ownership controls, policy status, CORS (applied to preflight and
|
|
602
|
+
responses), lifecycle rules (applied every hour: expiration by days or date, noncurrent versions, expired delete
|
|
603
|
+
markers, incomplete multipart uploads, transitions), static website hosting (`/-/website/<bucket>/` and
|
|
604
|
+
`<bucket>.s3-website.<domain>`: index and error documents, redirects, routing rules), object lock (default
|
|
605
|
+
retention, GOVERNANCE / COMPLIANCE, legal hold), default encryption; logging, notification, replication,
|
|
606
|
+
accelerate, request payment, metrics, analytics, inventory and intelligent-tiering configurations are stored.
|
|
607
|
+
- Objects: put / get / head / delete / copy (metadata and tagging directives), ranges, part numbers, conditional
|
|
608
|
+
reads and writes, user metadata and standard headers, `response-*` overrides, tags, ACLs, storage classes
|
|
609
|
+
(archive classes need RestoreObject), checksums CRC32, CRC32C, CRC64NVME, SHA1, SHA256 and `Content-MD5`,
|
|
610
|
+
DeleteObjects, GetObjectAttributes, ListObjects / ListObjectsV2 / ListObjectVersions (delimiters, markers,
|
|
611
|
+
`encoding-type=url`), multipart uploads (UploadPartCopy, ListParts, ListMultipartUploads, composite and
|
|
612
|
+
full-object checksums), path-style and virtual-hosted requests. Not supported: S3 Select, torrents, directory
|
|
613
|
+
buckets; SSE headers are returned but objects are not encrypted at rest.
|
|
614
|
+
- Both servers keep the same data layout (one JSON record per key, one file per version, atomic writes, mode
|
|
615
|
+
600), so they are interchangeable on one volume.
|
|
616
|
+
- Console: sign in with an access key and its secret key (or `S3_UI_PASSWORD`); buckets with every setting, folder
|
|
617
|
+
browsing and search, drag-and-drop upload of files and folders with progress, downloads, previews, share links
|
|
618
|
+
(presigned GET / PUT), copy / move / rename, delete, versions (download, delete, make current, show deleted),
|
|
619
|
+
metadata, tags, ACLs, object lock, unfinished uploads, *Run lifecycle now*. HttpOnly SameSite=Strict session,
|
|
620
|
+
per-session request token, lock-out after 10 failed sign-ins, strict CSP.
|
|
621
|
+
- **On-prem services `s3` (Python) and `s3-node` (Node.js)**, under *Object storage*: the stock
|
|
622
|
+
`python:3.12-alpine` / `node:22-alpine` image gets the server and the console with `docker create` + `docker cp`
|
|
623
|
+
(scp first on SSH servers) + `docker start`, so nothing is built or pushed. User = access key ID, password =
|
|
624
|
+
secret key. The resource is a `storage` bucket on the `s3` driver (storage triggers work); the env file gets
|
|
625
|
+
`PSKIT_<KEY>_URL`, `_ACCESS_KEY` and `_SECRET_KEY`. Port 9000, data volume and *Backup*, *Web UI → S3 console*,
|
|
626
|
+
*Browse → Buckets (S3)*, an `aws s3` console and a *How to use* page (boto3, AWS SDK for JavaScript, AWS CLI).
|
|
627
|
+
|
|
628
|
+
## [2.1.0] - 2026-10-26
|
|
629
|
+
|
|
630
|
+
### Added
|
|
631
|
+
- **Move a project's local settings to another machine**: `pskit settings export [-o FILE]` and
|
|
632
|
+
`pskit settings import FILE [--dry-run] [--replace] [--yes]`, and in the studio *Setup & credentials → Move
|
|
633
|
+
settings to another machine* (export with a passphrase and download; pick a file, preview, import). `.pskit`
|
|
634
|
+
stays out of git; the file carries what a fresh clone lacks: saved servers, scaling clusters with their load
|
|
635
|
+
balancers, on-prem services with their passwords and tokens, SSH passwords, the SSH key files the servers use
|
|
636
|
+
(also from `~/.ssh`, written to `.pskit/ssh/keys/` on import), where each on-prem stage was last deployed (so
|
|
637
|
+
logs, test and info work at once), the studio's test events, and env files named by `env_file` in `pskit.yml`.
|
|
638
|
+
Paths inside the project are stored relative to it, so the project can live in another folder or OS.
|
|
639
|
+
- The file is always encrypted with a passphrase (at least 8 characters): scrypt key derivation, HMAC-SHA256
|
|
640
|
+
counter-mode encryption and an HMAC-SHA256 tag (encrypt-then-MAC), standard library only. A wrong passphrase,
|
|
641
|
+
a changed file or a path that would leave the project is refused before anything is written.
|
|
642
|
+
- Import merges saved servers, clusters and services by name (the file's entries win, others stay); `--replace`
|
|
643
|
+
drops local entries the file lacks. The current settings are backed up to `.pskit/backups/settings-<time>.json`
|
|
644
|
+
first. Terraform state is not included. `PSKIT_SETTINGS_PASSPHRASE` skips the prompt in scripts.
|
|
645
|
+
- Studio API: `POST /api/settings-bundle/export`, `/preview` and `/import`.
|
|
646
|
+
|
|
647
|
+
## [2.0.0] - 2026-10-26
|
|
648
|
+
|
|
649
|
+
### Added
|
|
650
|
+
- **Load balancer for scaling clusters** (Swarm, k3s and Nomad): `pskit cluster balancer set NAME SERVER [--port 80]`
|
|
651
|
+
runs nginx in Docker (`pskit-lb`) on a saved server outside the cluster and spreads each deployment's HTTP over
|
|
652
|
+
the cluster's servers (fewest connections, failed servers rest 10 s, retries on another server). On Nomad the
|
|
653
|
+
web replicas share the requests and the master's main replica is only a backup. `pskit deploy`, `pskit remove`,
|
|
654
|
+
`cluster join` and `cluster leave` update it: a leaving server and a removed deployment come off it before they
|
|
655
|
+
stop. Every change passes `nginx -t` first and reloads without dropping connections; an offline load balancer
|
|
656
|
+
only warns (`pskit cluster balancer sync NAME` catches up). `cluster balancer logs` shows one line per request
|
|
657
|
+
with the server that answered; `cluster status` and `cluster list` show it and each deployment's URL. Logs,
|
|
658
|
+
tests and the admin API keep using the master. `options.cluster.balancer_port` gives a second deployment on the
|
|
659
|
+
same cluster its own port. Studio API: `POST /api/onprem-clusters/NAME/balancer-set|balancer-sync|balancer-remove`
|
|
660
|
+
and `GET .../balancer-logs`.
|
|
661
|
+
- **Studio: Load balancer card** on the *Scaling cluster* page: set it up (pick or add a server, port, address),
|
|
662
|
+
move it to another server, *Sync now*, *Remove*, nginx state and the server's CPU / memory / disk, each
|
|
663
|
+
deployment's public URL, and the access log. *Deployed functions* shows the public URL above the master's
|
|
664
|
+
address, *Live requests* marks which servers share requests and which is the backup, and the project's cluster
|
|
665
|
+
settings get *Port on the load balancer* (`options.cluster.balancer_port`). A load balancer server is no longer
|
|
666
|
+
offered as a master or joined server.
|
|
667
|
+
|
|
668
|
+
## [1.11.0] - 2026-10-26
|
|
669
|
+
|
|
670
|
+
### Added
|
|
671
|
+
- **AWS Secrets Manager compatible server** in `aws/secretsmanager`, in Python (`python/server.py`, standard library
|
|
672
|
+
only) and Node.js (`nodejs/server.js`, no npm packages), with a Dockerfile for each and a `docker-compose.yml`.
|
|
673
|
+
boto3, the AWS SDKs, the AWS CLI and `get_secret()` / `getSecret()` work with it unchanged through
|
|
674
|
+
`endpoint_url`. Every request is checked with AWS Signature Version 4 (wrong secret key, unknown access key and
|
|
675
|
+
requests older than 15 minutes are refused). It supports CreateSecret, GetSecretValue, BatchGetSecretValue,
|
|
676
|
+
PutSecretValue, UpdateSecret, DescribeSecret, ListSecrets (filters, paging), DeleteSecret (recovery window or
|
|
677
|
+
force), RestoreSecret, ListSecretVersionIds, UpdateSecretVersionStage (AWSCURRENT / AWSPREVIOUS), tags,
|
|
678
|
+
GetRandomPassword and resource policies (stored). Rotation and replica regions are not supported. Both servers
|
|
679
|
+
keep the same JSON data file (mode 600, written atomically), so they are interchangeable.
|
|
680
|
+
- **Its own web console** at `/ui/` (`aws/secretsmanager/ui/index.html`), signed in with the access key ID and
|
|
681
|
+
secret key (or `SM_UI_PASSWORD`): list and filter, create (key/value or plaintext, generate a password), show and
|
|
682
|
+
copy values, new versions, make an old version current, description and tags, delete with a recovery window,
|
|
683
|
+
restore. HttpOnly `SameSite=Strict` session cookie, a per-session request token, a lock-out after ten failed
|
|
684
|
+
sign-ins and a strict Content-Security-Policy.
|
|
685
|
+
- **On-prem services `secretsmanager` (Python) and `secretsmanager-node` (Node.js)** under *Secret managers*
|
|
686
|
+
(`pskit resources onprem create secrets --service secretsmanager --user AKIAPROD`). They run on the stock
|
|
687
|
+
`python:3.12-alpine` / `node:22-alpine` image: pskit copies the server and the console into the container with
|
|
688
|
+
`docker cp` (with scp first on an SSH server), so nothing is built or pushed. The user is the access key ID and
|
|
689
|
+
the password the secret key; the env file gets `PSKIT_<KEY>_DRIVER=aws`, `_URL`, `_REGION`, `_ACCESS_KEY` and
|
|
690
|
+
`_SECRET_KEY`. Port 4584, data volume and *Backup*, *Web UI → Secrets console*, pskit's *Browse secrets*, an AWS
|
|
691
|
+
CLI console and a *How to use* page with boto3, AWS SDK for JavaScript v3, AWS CLI and `get_secret()` examples.
|
|
692
|
+
The wheel ships the `aws/` folder as `py_serverless_kit/aws`.
|
|
693
|
+
|
|
694
|
+
## [1.10.5] - 2026-10-24
|
|
695
|
+
|
|
696
|
+
### Fixed
|
|
697
|
+
- **MinIO and RustFS did not become ready** (`did not become ready within 90 s`). The data directory on the server
|
|
698
|
+
is created as the SSH user, and these images run as their own user (MinIO uid 1001, RustFS uid 10001), so the
|
|
699
|
+
process cannot write it and exits with `Permission denied`. pskit now gives that directory to the container user
|
|
700
|
+
before start (other images that do not run as root get the same, from the image's user). A container that keeps
|
|
701
|
+
restarting fails at once and the error includes its last log lines. On an SSH server, an HTTP readiness check
|
|
702
|
+
runs on the server (`127.0.0.1`), so a firewall in front of the service port is not reported as a failed start.
|
|
703
|
+
|
|
704
|
+
## [1.10.4] - 2026-10-24
|
|
705
|
+
|
|
706
|
+
### Added
|
|
707
|
+
- **Live balance for one deployment**: `pskit cluster requests NAME --follow` and the studio cluster page's
|
|
708
|
+
*Live requests* card list every server, its URL, whether that URL is the main replica or a web replica, and
|
|
709
|
+
its share of HTTP. Servers with no traffic yet are included. Swarm and k3s spread HTTP from any server's
|
|
710
|
+
port. On Nomad the master's URL is the main replica and each other server's URL is one web replica.
|
|
711
|
+
- **Live logs for a cluster deployment**: `pskit logs -f`, the studio **Logs** view and the cluster page's
|
|
712
|
+
*Live logs* card follow a cluster the same way they follow one machine. On Nomad each server is read
|
|
713
|
+
directly, so a web replica's lines show together with the main replica.
|
|
714
|
+
|
|
715
|
+
### Fixed
|
|
716
|
+
- **Nomad cluster deploy failed after the job was accepted** (`pskit: no answer on
|
|
717
|
+
http://127.0.0.1:8080/__pskit/health`). The job asked Nomad for host networking, but Docker stayed on its own
|
|
718
|
+
bridge, so the functions' port never opened on the server's loopback. The task now uses Docker host networking
|
|
719
|
+
and binds that port on the server. The previous job is stopped first so the port is free. While the deploy
|
|
720
|
+
waits it prints each allocation and the main replica's logs every 10 seconds, and that output is shown as it
|
|
721
|
+
happens. Nomad does not load-balance: the master's port is the main replica, and each other server answers on
|
|
722
|
+
the same port. A load balancer is optional.
|
|
723
|
+
|
|
724
|
+
## [1.10.3] - 2026-10-24
|
|
725
|
+
|
|
726
|
+
### Fixed
|
|
727
|
+
- **Cluster deploys copied the image several times and could fail after it had loaded** (`copy interrupted
|
|
728
|
+
(command failed (1): Loaded image: ...)`). When no older copy of the image was left on the server, the cleanup at
|
|
729
|
+
the end of the load script exited 1, even though the image was already loaded. The script now exits 0 once
|
|
730
|
+
the image is loaded. Before each retry pskit also checks whether the server already has the image, and stops
|
|
731
|
+
copying if it does.
|
|
732
|
+
- **Creating an SMTP server when the functions are not set in pskit.yml** (`the functions run on this machine,
|
|
733
|
+
which the SMTP server cannot reach`). The functions' address now comes from where the stage was last deployed
|
|
734
|
+
(`pskit deploy --cluster` / `--server`, or the studio's machine picker) when pskit.yml names no target. If the
|
|
735
|
+
functions are not deployed anywhere yet, an SMTP server on a node of a scaling cluster sends mail to that
|
|
736
|
+
cluster. On Swarm it uses `127.0.0.1` (Swarm publishes the port on every node); on k3s and Nomad it uses the
|
|
737
|
+
master's cluster address. In any other case the error now says that the functions need to be deployed first.
|
|
738
|
+
|
|
739
|
+
## [1.10.2] - 2026-10-24
|
|
740
|
+
|
|
741
|
+
### Fixed
|
|
742
|
+
- **Copying the function image to cluster servers**: a dropped connection (`scp: Couldn't send packet: Broken
|
|
743
|
+
pipe`) no longer fails the whole deploy. The image is gzip-compressed, often to a third of its size or less,
|
|
744
|
+
and sent in 16 MB parts with checksums. Each retry sends only the parts that are missing, up to 6 attempts with
|
|
745
|
+
growing pauses, and parts already copied stay on the server, so the next `pskit deploy` resumes the copy. The
|
|
746
|
+
joined image is checked against its checksum before it is loaded, and a damaged copy is sent again. Progress is
|
|
747
|
+
shown per server. Only a failure on the master stops the deploy; a worker that fails gets a warning instead.
|
|
748
|
+
- **A saved server that was removed or renamed** (pskit.yml still saying `deploy.server: VM_01` after it became
|
|
749
|
+
`VM_01_2cpu`):
|
|
750
|
+
- The studio's *Create service* dialog no longer pre-selects a server that is not saved. Before, the picker
|
|
751
|
+
showed *New connection…* but the request still sent the old name. The dialog now explains what is wrong.
|
|
752
|
+
- Every *"no saved SSH server"* error says where the name came from (pskit.yml, the last deploy) and suggests
|
|
753
|
+
close matches (*Did you mean VM_01_2cpu or VM_01_4cpu?*).
|
|
754
|
+
- Creating an SMTP server with a stale functions server suggests `functions_url`.
|
|
755
|
+
- `pskit resources onprem servers remove` (and the studio's *Forget*) refuses a server that is still in a
|
|
756
|
+
cluster, and warns when pskit.yml or a created resource still names it.
|
|
757
|
+
|
|
758
|
+
## [1.10.1] - 2026-10-24
|
|
759
|
+
|
|
760
|
+
### Fixed
|
|
761
|
+
- **Re-adding a server to a cluster**: `pskit cluster join` no longer fails with *"This node is already part of a
|
|
762
|
+
swarm"*. A server that a failed join left in `pending`/`error`, that was removed while it was off, or that belongs
|
|
763
|
+
to a swarm that was set up again now leaves the old swarm and joins. It is skipped if it is already a member,
|
|
764
|
+
checked by node id instead of by manager address, which used to break when the master had both public and
|
|
765
|
+
private IPs. Pskit still refuses to take over a server that manages another swarm with nodes or services, or
|
|
766
|
+
whose swarm is locked. Older *down* entries for the same host are removed from the master after the rejoin. The
|
|
767
|
+
swarm master setup also recovers from a half-joined state. Kubernetes (k3s) agents are reinstalled when they
|
|
768
|
+
point at a different master or token, and a server running its own k3s server is refused with a clear message.
|
|
769
|
+
## [1.10.0] - 2026-10-24
|
|
770
|
+
|
|
771
|
+
### Added
|
|
772
|
+
- **Live requests on a cluster**: the cluster page's *Live requests* card and `pskit cluster requests NAME --follow`
|
|
773
|
+
show each request as it happens with the server and replica that handled it (plus requests per server). The
|
|
774
|
+
studio polls every 2 s only while the card is on screen and the tab is visible. Replicas get `PSKIT_NODE` from
|
|
775
|
+
the orchestrator (Swarm, k3s, Nomad); the host serves `GET /__pskit/requests?since=N`.
|
|
776
|
+
- **Saved servers: home path, bind address, data directory** (studio *Add a server*, `servers add --home --bind
|
|
777
|
+
--data-dir`). Defaults for what runs there: functions deploy to `<home>/<service>-<stage>`, listen on the bind
|
|
778
|
+
address and keep data in the data directory; services publish their port on the bind address and keep data in
|
|
779
|
+
`<data>/<container>` (bind mount); a cluster keeps its files in `<home>/pskit-cluster`, uses a specific bind IP
|
|
780
|
+
as the server's cluster address, and keeps the main replica's data in `<data>/<stack>` on the master.
|
|
781
|
+
|
|
782
|
+
### Changed
|
|
783
|
+
- The *New scaling cluster* dialog: the name field is labelled *Cluster name*, focused, always pre-filled with a
|
|
784
|
+
free name (`prod`, `prod-2`, ...) and lower-cased as you type.
|
|
785
|
+
|
|
786
|
+
## [1.9.0] - 2026-10-24
|
|
787
|
+
|
|
788
|
+
### Added
|
|
789
|
+
- **One server or a scaling cluster, per deploy**: `pskit deploy | package | plan | remove | info --cluster NAME`, and
|
|
790
|
+
in the studio *Deploy → Run on: One machine / Scaling cluster*. The stage remembers the cluster of its last deploy
|
|
791
|
+
like a server (`deployed on: cluster prod (master edge1 (...))`); `--server NAME` moves it back to one machine.
|
|
792
|
+
- **Resources on a cluster**: `pskit resources onprem create KEY --service S --cluster NAME [--node SERVER]`, and
|
|
793
|
+
*Where → Scaling cluster* in the studio's create form. Without `--node` the reachable server with the most free
|
|
794
|
+
memory under every capacity limit runs it (a full cluster refuses, asking for another server); its env values use
|
|
795
|
+
that server's cluster address. With `options.cluster` in pskit.yml new resources default to the cluster.
|
|
796
|
+
`pskit cluster status` and the studio's cluster page list them per server; a server that leaves keeps them as
|
|
797
|
+
one-server resources.
|
|
798
|
+
|
|
799
|
+
### Changed
|
|
800
|
+
- `--server NAME` now wins over `options.cluster` in pskit.yml (deploys to that one machine); before, the cluster
|
|
801
|
+
always won.
|
|
802
|
+
|
|
803
|
+
## [1.8.0] - 2026-10-24
|
|
804
|
+
|
|
805
|
+
### Added
|
|
806
|
+
- **Scaling clusters for on-prem functions** ([docs/cluster.md](docs/cluster.md)): a master server plus joined servers
|
|
807
|
+
run by **Docker Swarm**, **Kubernetes (k3s)** or **HashiCorp Nomad**, all installed and driven over SSH from saved
|
|
808
|
+
servers. `pskit cluster create | join | leave | status | check | watch | alerts | scale | list | remove`, and a new
|
|
809
|
+
studio page **Scaling cluster**: create a cluster, join servers (also while functions run, adding a new saved server
|
|
810
|
+
in the same dialog), see every server's CPU / memory / disk against the limits, replicas running / desired and
|
|
811
|
+
replicas that cannot be placed, scale, drain and remove servers.
|
|
812
|
+
- `provider.options.cluster` (`cluster: prod` or `{name, replicas, cpu, memory}`) deploys the functions to a cluster:
|
|
813
|
+
the image is built on this machine, copied to every server (no registry), and deployed as one `main` replica on the
|
|
814
|
+
master (schedules, built-in queues / topics / buckets, workflow executions, logs, the data volume) plus `replicas`
|
|
815
|
+
`web` replicas behind the orchestrator's load balancer (HTTP routes and `invoke()`). Joining a server copies the
|
|
816
|
+
deployed images to it and does not redeploy. Without `options.cluster` nothing changes: the host runs on one server.
|
|
817
|
+
- Capacity alerts: when every server is over a limit (default CPU 85 %, memory 85 %, disk 90 %), replicas cannot be
|
|
818
|
+
placed, or no server is ready, pskit calls a function of yours (`event.data.type = "pskit.cluster.capacity"`, e.g. to
|
|
819
|
+
mail DevOps) and / or POSTs a webhook (Slack / Teams `text` included), once per cooldown. Checks run in the studio
|
|
820
|
+
(*Watch while the studio runs*) or with `pskit cluster watch` / `pskit cluster check` (exit 3 when full).
|
|
821
|
+
- Host roles for cluster replicas (`PSKIT_HOST_ROLE=main|web`, `PSKIT_MAIN_URL`): a web replica forwards built-in
|
|
822
|
+
queue / topic / bucket calls, workflow starts and `/__pskit/*` admin calls to the main replica (retrying for a few
|
|
823
|
+
seconds while it restarts), and ships its log entries (tagged `replica`) and invocation counts to it every second.
|
|
824
|
+
`GET /__pskit/health` reports `role` and `replica`. A host without a role behaves as before.
|
|
825
|
+
|
|
826
|
+
## [1.7.0] - 2026-10-23
|
|
827
|
+
|
|
828
|
+
### Changed
|
|
829
|
+
- **E-mail triggers are now one on-prem service.** *Resources → **+ SMTP server*** (or *On-prem services → Mail*)
|
|
830
|
+
starts a Node.js SMTP server (nodemailer's `smtp-server` + `mailparser`, `node:22-alpine`) on any server for the
|
|
831
|
+
domains you list, and ticks the functions to run. Each mail is posted to the host (`POST /__pskit/smtp/<key>`),
|
|
832
|
+
which runs every function with `- smtp: {resource: <key>}`. When one fails, or none is attached, the sender gets
|
|
833
|
+
`451` and retries. Mail for other domains is refused (never a relay). On an SSH server it uses the host network, so
|
|
834
|
+
a host bound to 127.0.0.1 works.
|
|
835
|
+
- `event.data` of an `smtp` event: `from`, `from_name`, `to`, `cc`, `bcc`, `reply_to`, `subject`, `date`, `text`,
|
|
836
|
+
`html`, `headers`, `attachments` (base64 `content`), `envelope`, plus the Amazon SES receipt event (`Records[0].ses`)
|
|
837
|
+
and the raw message (`content`, base64), so code written for SES reads it unchanged.
|
|
838
|
+
- **DNS guide** on the SMTP service (also *How to use* and `pskit resources onprem create --service smtp`): the A and
|
|
839
|
+
MX records with your values, provider notes (Cloudflare grey cloud, keep the root domain's MX), port 25 and tests.
|
|
840
|
+
- `pskit resources onprem create`: `--domains`, `--functions-url`, `--max-size-mb`.
|
|
841
|
+
|
|
842
|
+
### Removed
|
|
843
|
+
- The host's built-in SMTP server and everything around it: `type: smtp` resource options (`domains`, `port`, `auth`,
|
|
844
|
+
`users`, TLS, allow-lists, `verify_senders`, `block_spoofed`), the `recipients` / `subdomains` trigger filters,
|
|
845
|
+
SPF / DKIM / DMARC checks, the Mailbox and `/__pskit/mail`, the *Mail domain* setup wizard (`/api/mail-setup`,
|
|
846
|
+
`/api/mail-handler-stub`, `/api/resource-mail`, `/api/env-file`). Recreate an SMTP server as the on-prem service.
|
|
847
|
+
|
|
848
|
+
## [1.6.0] - 2026-10-23
|
|
849
|
+
|
|
850
|
+
### Added
|
|
851
|
+
- **Receive mail for your domain in a few steps.** Studio *Resources → **+ Mail domain (SMTP)*** looks up the
|
|
852
|
+
domain's current mail (Microsoft 365, Google Workspace ...) and suggests a subdomain such as `inbound.kavion.ai`, with a
|
|
853
|
+
warning before moving the domain's own MX. You pick the machine (its IP), the mail server name, the port and the
|
|
854
|
+
security, tick the functions to run (or create `on-mail` with a ready handler file in Python or Node.js), and pskit
|
|
855
|
+
adds the `smtp` resource and triggers. It then lists the **DNS records** to add at the domain provider: A for the
|
|
856
|
+
mail server, MX, wildcard MX for subdomains, and SPF `-all` / DMARC `p=reject` for a receive-only domain. It
|
|
857
|
+
explains why receiving needs no DKIM record. **Check DNS** shows each record live / missing / different / keep
|
|
858
|
+
(DNS over HTTPS, plain DNS fallback), and an optional port 25 check. **DNS setup** on an smtp resource reopens it.
|
|
859
|
+
Backend: `core/mail_setup.py`, `POST /api/mail-setup`, `/api/mail-handler-stub`.
|
|
860
|
+
- **SPF, DKIM and DMARC checks of received mail** (`runtime/mail_auth.py`, stdlib only: its own DNS client, RSA
|
|
861
|
+
verification). Results are in `event.data["authentication"]`, the logs and the Mailbox. `block_spoofed: true`
|
|
862
|
+
stops mail whose DMARC fails with `p=quarantine / reject`, or that claims to come from the server's own domain
|
|
863
|
+
without passing SPF or DKIM (status *blocked*). The `verify_senders` option turns the checks off. DKIM
|
|
864
|
+
verification is tested against signatures made by dkimpy (simple and relaxed, sha256 and sha1), and SPF against
|
|
865
|
+
live records.
|
|
866
|
+
|
|
867
|
+
## [1.5.0] - 2026-10-23
|
|
868
|
+
|
|
869
|
+
### Added
|
|
870
|
+
- **E-mail (SMTP) triggers on premises.** A resource of `type: smtp` makes the host run an SMTP server for your domains (`options.domains`, subdomains on by default, port 2525, `max_size_mb`). Functions get `- smtp: {resource: inbound-mail, subdomains: [support], recipients: ["*@support.example.com"]}`. The handler receives `event.data` with `from`, `recipient` / `recipients` split into local part, **subdomain** and domain, `to` / `cc`, subject, text, html, headers and attachments (base64). Mail is stored before `250` is answered and delivered after a restart. Every message is logged with its sender, recipients, subdomain, subject, files and a body preview, plus structured fields. The server is never an open relay. Options: SMTP **AUTH on / off** with users whose passwords live in the env file (`password_env`), STARTTLS (`tls_cert` / `tls_key`, `require_tls`), `allowed_senders` and `allowed_ips`. Mail admin API `/__pskit/mail`; `pskit trigger` and `pskit invoke -t smtp` send test mail. Studio: an *E-mail (SMTP)* trigger form, an SMTP server form (domains, password on/off, users, generate and save passwords, TLS, allow-lists) and a **Mailbox** (paged list with subdomain and domain, details, attachments, `.eml`, run functions again, delete, send a test mail). Other providers reject `smtp` triggers when you validate. Guide with DNS (MX, A, wildcard MX for subdomains), port 25, cloud firewalls, TLS, testing and the architecture: `docs/smtp/README.md`.
|
|
871
|
+
- **pskit's own service browsers** where the native UI is missing or limited (*Browse* on a service row). **S3** (MinIO, RustFS, LocalStack, LocalEmu): buckets, folders, paginated listings, filter, multi-file upload, download, info and metadata, old versions, rename / copy, presigned share links, versioning and bucket policies (private / public read / JSON). **Cloud Storage** (fake-gcs-server). **Secrets** for OpenBao (folders, versions, add / edit / delete); its release images have no web UI, which the *"OpenBao UI is not available in this binary"* page meant. Also **Secrets Manager** for LocalStack and LocalEmu. A closed service port is reached over the server's SSH login.
|
|
872
|
+
- **More one-click services**: LocalEmu (AWS emulator), Infisical (secrets manager with its own PostgreSQL and Redis as sidecars; generated `ENCRYPTION_KEY` / `AUTH_SECRET` kept in the env file and reused when it is created again), Grafana, Prometheus, Uptime Kuma, Jaeger, Keycloak, Meilisearch, Typesense, Qdrant, ClickHouse, Neo4j, Eclipse Mosquitto, n8n, Portainer, Gitea and Nginx Proxy Manager. The catalog is grouped (queues, Redis-compatible, object storage, databases, secrets, AWS emulators, monitoring, identity and search, automation and tools). Services are described by data (`sidecars`, `generate`, `connect` templates) in the new `core/onprem_apps.py`.
|
|
873
|
+
- **`infisical` secrets driver** for `get_secret()` / `put_secret()` in Python and `getSecret()` / `putSecret()` in Node.js (machine identity with Universal Auth, or a token; project, environment, path).
|
|
874
|
+
- **Pick the Python version** when installing Python on a server: `system` (the distribution's) or 3.9 to 3.14 as a standalone CPython (through uv, any distribution) linked as `python3.X`. Node.js adds 24.
|
|
875
|
+
|
|
876
|
+
### Fixed
|
|
877
|
+
- Command logs mask every `*KEY*` value (`ENCRYPTION_KEY`, API keys), not only passwords, secrets and tokens.
|
|
878
|
+
|
|
879
|
+
## [1.4.0] - 2026-10-23
|
|
880
|
+
|
|
881
|
+
### Fixed
|
|
882
|
+
- **Studio: Overview edits no longer lose to a stale `providers.<cloud>` copy.** Switching providers parked the old provider's options under `providers.<cloud>:`; switching back copied them to `provider:` but kept the parked block. That block is merged over `provider:` when deploying, so for example *On-premises options → Bind address 0.0.0.0* kept deploying `127.0.0.1` and a picked server kept `deploy.method: local`. Switching back now moves the parked settings into `provider:`. Editing any `provider.*` setting also removes the same setting from the active provider's `providers.<cloud>` block.
|
|
883
|
+
|
|
884
|
+
### Added
|
|
885
|
+
- **Overview warns about provider settings overridden under `providers.<active cloud>`** and offers **Use the values shown here**. This moves them under `provider:`: the values shown in Overview win, and settings only the override has are kept. Function / workflow overrides and other clouds' blocks are left alone.
|
|
886
|
+
- **`pskit validate` / `deploy` warn** when `providers.<cloud>` overrides a different value set under `provider:` for that same cloud (`[providers.onprem.options.host] providers.onprem sets options.host to '127.0.0.1', which overrides '0.0.0.0' ...`).
|
|
887
|
+
|
|
888
|
+
## [1.3.10] - 2026-10-23
|
|
889
|
+
|
|
890
|
+
### Fixed
|
|
891
|
+
- **On premises: a chosen server really deploys there.** With `deploy: {method: local}` in `pskit.yml` (what a new project writes), `pskit deploy --server NAME` and studio *Deploy → Machine* kept `method: local`, so the host started on this machine and was labelled `VM_01 (this machine)`. A saved server now always deploys over SSH (`docker` stays `docker`). `method: local` on its own no longer overrides the server a stage was last deployed to; `--server local` still picks this machine.
|
|
892
|
+
|
|
893
|
+
### Added
|
|
894
|
+
- **Studio Overview → On-premises deployment: Saved server.** Pick one of the servers saved under *Resources → On-prem services → Servers* (writes `provider.options.deploy.server` and switches the method to SSH), or **+ Add server** to save a new one from there. Shows where the stage is deployed now.
|
|
895
|
+
|
|
896
|
+
## [1.3.9] - 2026-10-23
|
|
897
|
+
|
|
898
|
+
### Fixed
|
|
899
|
+
- **On premises: commands go to the host the stage was deployed to.** A deploy remembers its machine (`.pskit/onprem-<stage>/onprem_deployed.json`, plus `deployed_on` in `deployment.json`). `pskit trigger`, `pskit logs`, `resources send`, executions and the studio no longer fall back to `http://127.0.0.1:8080` after `package` / `plan` / `info` re-rendered the spec without `--server`, or after the studio's Machine picker reset. The next deploy without `--server` goes to the same saved server; `--server local` picks this machine. `pskit deploy` prints where it deployed instead of `On-premises local`.
|
|
900
|
+
- **On premises: hosts whose port is closed are reached over SSH.** Logs, triggers, bucket uploads, HTTP tests and the other control calls to a remote host whose port is not reachable from here (the default `127.0.0.1` bind, or a firewall) now run over the deploy's SSH login. Previously they failed with `WinError 10061 ... actively refused`. If nothing answers there either, the error says so and names the redeploy command.
|
|
901
|
+
- **Studio: server pickers start on the deployed server.** Deploy (Machine), Test (new **Server** picker for *Send to …*, also used by its logs) and Logs open on the server the stage was deployed to, mark it `· deployed here`, and offer *This machine (local)*. Deploy asks before moving a stage to another machine. Studio trigger, resource-send and workflow-run jobs now pass `--server`.
|
|
902
|
+
|
|
903
|
+
## [1.3.8] - 2026-10-22
|
|
904
|
+
|
|
905
|
+
### Added
|
|
906
|
+
- **On-prem services from the Resources list**: *Resources → + On-prem service* creates Redis, Kafka, PostgreSQL, MinIO, OpenBao, ... and adds it to the resource list with its triggers; *Add resource* offers *Create a <type> on premises* (catalog filtered to services that can back that type). Services created earlier but missing from `pskit.yml` are listed above the table with one-click **Add**, and rows backed by a service show `on-prem <service> · <server>`.
|
|
907
|
+
- **Logs per server**: the studio *Logs* view has a **Server** picker for on-prem projects, and `pskit logs --server NAME` reads the host on that saved server instead of the last deploy's endpoint. The same `--server` also points `pskit trigger`, `pskit resources send`, executions and the other host commands at that machine (one project deployed to several servers).
|
|
908
|
+
|
|
909
|
+
## [1.3.7] - 2026-10-22
|
|
910
|
+
|
|
911
|
+
### Added
|
|
912
|
+
- **Saved SSH servers**: `pskit resources onprem servers add|list|test|remove` and studio *On-prem services → Servers*. Name each machine once (key file, SSH agent / default key, or password through sshpass); the test reports OS, CPU, memory, disk, Docker access, sudo and installed runtimes. Services are created on one with `create --server NAME` or the create form's **Server** list. Stored in `.pskit/onprem-servers.json`; passwords only in `.pskit/ssh/`.
|
|
913
|
+
- **Deploy to a chosen machine**: `pskit deploy --server NAME` (also package / plan / remove / info), `provider.options.deploy.server` in `pskit.yml` (per stage), and studio **Deploy → Machine**. The saved server's host, user, port and login replace those in `options.deploy`.
|
|
914
|
+
- **Install software on a server**: Node.js (22 / 20 / 18 from NodeSource), Java (OpenJDK 21 / 17), Go (any 1.x.y), nginx (enabled and started), Caddy, Certbot, PM2, Git and basic tools, next to Python and Docker; apt, dnf, yum and apk. `create KEY --service nodejs --version 20 --server edge1`; the studio offers a version picker.
|
|
915
|
+
- **Console for every service**: `pskit resources onprem console KEY [COMMAND]` and studio *Console*: redis-cli, psql, mysql / mariadb, mongosh, rpk, kafka scripts, rabbitmqctl, lavinmqctl, nats (nats-box), mc, aws (s3 / sqs), awslocal, bao, the memcached text protocol and HTTP APIs, or `sh` in the container. Lines run on this machine or over SSH with the service's credentials (hidden in the output); images without a client get a helper container on the service's private network. Servers get `pskit resources onprem shell SERVER [COMMAND]` and the studio *Shell*.
|
|
916
|
+
- **Browser terminal**: `pskit resources onprem terminal (KEY | --server NAME)` and studio *Terminal*: ttyd in Docker on `127.0.0.1` behind a random secret path, embedded in the studio; SSH sessions with the saved login, or a service's interactive client / `sh`. `--list`, `--stop NAME|all`.
|
|
917
|
+
- **Secret managers**: one-click **OpenBao** (Vault API, KV v2 at `secret/`, file storage, unsealed automatically, web UI, the password is the token) and **LocalStack** as a secret manager (AWS Secrets Manager + SSM). `get_secret(name, field=None, store=None, default=None)`, `get_secrets(name)` and `put_secret(name, value)` in the Python runtime and `getSecret` / `getSecrets` / `putSecret` in Node.js, with `vault`, `aws` (SigV4, Lambda credentials) and `env` drivers chosen by `PSKIT_<STORE>_*` variables, so the same handler reads secrets on every provider. New guide *On premises → secrets*.
|
|
918
|
+
|
|
919
|
+
### Changed
|
|
920
|
+
- Command logs also mask `*TOKEN*=` values.
|
|
921
|
+
- `describe_target` names the saved server (`edge1 (ubuntu@10.0.0.5:22)`).
|
|
922
|
+
|
|
923
|
+
## [1.3.6] - 2026-10-22## [1.3.6] - 2026-10-22
|
|
924
|
+
|
|
925
|
+
### Added
|
|
926
|
+
- **Web UI check**: `pskit resources onprem gui KEY --check` and studio *Details > Check web UI* test every web UI of a service: the container, the published port, the HTTP answer on the server itself (over SSH) and from this machine. Each UI gets a verdict and the fix: not running, port not published, bound to `127.0.0.1`, app not answering, firewall dropping (timeout) or rejecting (refused). On Azure / AWS / GCP the cloud is read from the instance metadata, with the exact `az vm open-port` command (resource group and VM name filled in), the subnet + NIC NSG note, the security group / firewall-rule steps, ufw / firewalld status, and the tunnel that works without opening anything. Nothing is changed.
|
|
927
|
+
- **Web UI login choice**: companion UIs start *with password* (generated, or your own with `--gui-password-env` / the studio field) or *without password* (`--gui-login none`; Redis Commander, Kafka UI, Mongo Express). Adminer always asks for the database login. A UI without login on `0.0.0.0` prints a warning. `pskit resources onprem gui KEY --login none|password --password-env VAR` switches an existing UI.
|
|
928
|
+
- **SSH login without a key file**: service targets and on-prem deploys log in with a key file, with the SSH agent / default key (no `pem`; also `auth: agent`), or with a password through sshpass (`password_file`, or `auth: password` with `SSHPASS`; studio *Log in with: Password*, saved in `.pskit/ssh/`, owner-only). The password never appears on a command line, in state, `pskit_host.json` or Terraform state.
|
|
929
|
+
- `pskit resources onprem ssh-key user@host[:port]`: logs in with the password once (ssh asks in the terminal, so it works on Windows without sshpass), installs `~/.ssh/pskit_ed25519` and checks that the key logs in.
|
|
930
|
+
- Guides: *Web UIs > With or without a password*, *The UI does not open* (the usual reasons an inbound rule "does not work"), *Try the web UIs in local Docker first*, and *SSH login: key, agent or password*; every How to use guide's Web UI section names the UI's port to open and the check command.
|
|
931
|
+
|
|
932
|
+
### Changed
|
|
933
|
+
- Remote Docker deploys no longer require a `.pem`: without one, OpenSSH uses the agent / default key (`pskit deploy` still offers to enter a path in a terminal). A `pem` that points to a missing file is still an error.
|
|
934
|
+
|
|
935
|
+
### Fixed
|
|
936
|
+
- A second companion web UI of the same kind on one server reused the default port and failed (`port is already allocated`); it now takes the next free port.
|
|
937
|
+
|
|
938
|
+
## [1.3.5] - 2026-10-22
|
|
939
|
+
|
|
940
|
+
### Added
|
|
941
|
+
- **More one-click on-prem services**, each driven end to end through its pskit driver: Dragonfly and KeyDB (Redis-compatible: queue, stream, cache), Apache Kafka (KRaft), LavinMQ (AMQP, RabbitMQ driver class), Azurite (Azure Blob + Queue with your own account and key), LocalStack (SQS + S3), fake-gcs-server (Cloud Storage) and RustFS (S3-compatible with a console).
|
|
942
|
+
- **Web UIs**: built-in UIs (RabbitMQ, LavinMQ, MinIO, RustFS, ElasticMQ, NATS, Mailpit) are listed with URL and login, and pskit can start a companion UI on a private Docker network with the service: Adminer (PostgreSQL / MySQL / MariaDB, server filled in), Redis Commander (Redis family, login), Kafka UI (login), Mongo Express (login). `pskit resources onprem gui KEY [--port] [--remove]`, `create --gui`, studio *Also start the web UI* and *Details > Add / Remove web UI*; every How to use guide has a **Web UI** section with a tunnel command (`tunnel --remote-port`).
|
|
943
|
+
- **Existing cloud code on premises**: the host serves the Lambda Invoke API (`POST /2015-03-31/functions/<name|ARN>/invocations`, RequestResponse / Event / DryRun, `FunctionError` on handler errors) and the SQS API for its queues (send / batch / receive with long polling / delete / visibility / attributes / list / create / purge). boto3 and the AWS SDKs work by changing `endpoint_url`; the `admin_token` doubles as the access key id. On-prem queues expose their SQS-compatible URL as `resource(key).url`.
|
|
944
|
+
- `invoke()` accepts deployed names and Lambda ARNs (with or without an alias) as well as pskit names, on every provider.
|
|
945
|
+
- Drivers: `create_queue` (azure_queue) and `create_bucket` (s3 family, azure_blob, gcs) create the queue or bucket on first use and after an emulator restart.
|
|
946
|
+
- Guides: *General > Existing cloud code* (`docs/resource-guides/compatibility.md`), shown in the studio; on-prem queue guides add an *Existing AWS SDK code* section.
|
|
947
|
+
|
|
948
|
+
### Fixed
|
|
949
|
+
- Extra ports (consoles, Azurite's queue port) were fixed numbers, so a second instance of a service on one server failed to start; they now move with the main port.
|
|
950
|
+
- Services answering over HTTP are ready only once they answer (Docker's port proxy accepts TCP before the app listens).
|
|
951
|
+
- Built-in queue messages count deliveries (`ApproximateReceiveCount` semantics) for leases and the SQS API.
|
|
952
|
+
|
|
953
|
+
### Changed
|
|
954
|
+
- Studio: calling the host from code is part of each resource's **How to use** guide (section 7, *Call it from code*) instead of a separate *Call from code* panel. On premises it has complete Python and Node.js programs for that resource with the pskit client (add data, page through it with `peek`, consume with `receive` + `ack` / `nack`, upload / download / list / delete files, publish with attributes, error handling), the host URL, token note and a live reachability check, then HTTP (7.2), the service's own library (7.3) and a timeouts section (7.4). The consume step is commented out when a pskit trigger already consumes the queue or its driver has no leases. `pskit client info` stays for the terminal.
|
|
955
|
+
|
|
956
|
+
## [1.3.4] - 2026-10-22
|
|
957
|
+
|
|
958
|
+
### Added
|
|
959
|
+
- **pskit client** for any program: `py_serverless_kit.client.PskitClient` (Python, standard library only) and `PskitClient` in the `pskit` Node.js package (with TypeScript types). Queues (`send`, `send_batch`, `depth`, `peek`, `receive` + `ack` / `nack`), topics (`publish`, `peek`), buckets (`put`, `get`, `delete`, `list`, `keys`), `invoke`, workflows, `check`, `resources`; resource keys or native names; `PskitClient.from_project(".")`. Everything goes through the host's HTTP API, so only the host port must be reachable.
|
|
960
|
+
- `pskit client info` (endpoint, token, reachability check, Python / Node.js / curl code per resource), `pskit client install-node` (copies the `pskit` package into `node_modules`), `pskit client tunnel` and `pskit resources onprem tunnel KEY` (SSH port forwarding for firewalled ports, printing the variables to use).
|
|
961
|
+
- Host: `GET /__pskit/storage/<bucket>` lists objects and `GET /__pskit/storage/<bucket>/<key>` returns one.
|
|
962
|
+
- Studio: *Resources → Call from code* (client guide with a live reachability check); *On-prem services → Details* and *How to use* warn when this machine cannot reach a service's port and say how to fix it.
|
|
963
|
+
- `docs/client.md`: client APIs, the full host HTTP API, and what to do when connections time out.
|
|
964
|
+
|
|
965
|
+
### Fixed
|
|
966
|
+
- Scripts generated for on-prem services hung for a minute when the service's port was firewalled (e.g. ElasticMQ on an Azure VM). Every direct-client example now uses short connect timeouts and a single attempt (boto3, redis, kafka-python, nats, pika, psycopg, pymysql, pymongo, pymemcache, smtplib, and their Node.js counterparts), so it fails in about five seconds; the guides explain the firewall and offer the tunnel and the pskit client instead.
|
|
967
|
+
|
|
968
|
+
## [1.3.3] - 2026-10-22
|
|
969
|
+
|
|
970
|
+
### Added
|
|
971
|
+
- **Credentials for on-prem services**: choose the user and password when creating a service (studio *Security* box with *Generate*; `--user`, `--password`, `--password-env`), and whether it listens on `127.0.0.1` or the network. Redis / Valkey with a custom user get an ACL user with the `default` user disabled. Passwords are percent-encoded in URLs and validated; services that run without authentication (Kafka, ElasticMQ, Memcached, Mailpit) refuse a password and say how to keep them private.
|
|
972
|
+
- **Use a service from any program**: *How to use* on each on-prem service and `pskit resources onprem usage KEY [--reveal]`: address, credentials, Python and Node.js code that connects directly (Redis lists and streams, Kafka, NATS JetStream, RabbitMQ, ElasticMQ, MinIO, PostgreSQL, MySQL, MongoDB, Redis cache, Memcached, SMTP) with the library to install, terminal commands and security notes. Resource guides on premises gain section 7, *Use it from any other program*, with the host HTTP API (any driver) and the direct client.
|
|
973
|
+
- **Browse data**: studio *Resources → Data* and `pskit resources data KEY` page through waiting queue messages (peeked, not consumed), pending topic messages and bucket objects (prefix filter, preview, delete); built-in queue messages can be deleted one by one. New host endpoints `GET /__pskit/resources/<key>/data`, `GET|DELETE /__pskit/resources/<key>/object`, `DELETE /__pskit/resources/<key>/message`, `GET /__pskit/queues/<name>/peek`. The redis, redis_stream and pskit_host drivers (and custom classes with `peek`) are browsable; services that count a delivery when showing a message show their depth.
|
|
974
|
+
|
|
975
|
+
## [1.3.2] - 2026-10-22
|
|
976
|
+
|
|
977
|
+
### Added
|
|
978
|
+
- **How to use, for every resource**: studio *Resources → How to use* and `pskit resources usage KEY` show an end-to-end guide for that resource on the current provider and stage: the library to install for Python and Node.js and how pskit packages it, the `pskit.yml` and trigger, handler code (publish / consume / connect) with copy buttons, local tests (`pskit invoke`, `pskit dev`), deployed tests (`resources send`, `resources check`, `logs`, cloud CLI), provider notes and troubleshooting. Covers every provider and resource type: S3-compatible buckets on Alibaba, Tencent, Huawei, Oracle, IBM, DigitalOcean and Cloudflare get `boto3` / `@aws-sdk/client-s3` code with the right endpoint; queues and topics there use the SDK example from the resource guides, with its library in the install step.
|
|
979
|
+
- `docs/resource-usage.md`: libraries per provider and type, how dependencies reach the function, secrets and a testing checklist.
|
|
980
|
+
|
|
981
|
+
## [1.3.1] - 2026-10-22
|
|
982
|
+
|
|
983
|
+
### Added
|
|
984
|
+
- **Code for every resource**: the studio's *Test a resource* panel shows Python and Node.js handler code (publish + consume for queues, buckets and topics on each cloud; PostgreSQL, MySQL, MongoDB, Redis, Memcached and SMTP connection examples) with the client library to add.
|
|
985
|
+
- **`pskit resources check KEY`** and studio *Test connection*: queue depth, bucket object count, or a connection check (Redis `PING`), run from the on-prem host once deployed (`POST /__pskit/resources/<key>/check`), else from this machine.
|
|
986
|
+
- **`pskit resources clear KEY`** empties a built-in on-prem queue, bucket or topic (`DELETE /__pskit/resources/<key>/data`). Studio *Delete* asks whether to keep or delete a resource's data (one-click services: stop or delete the container).
|
|
987
|
+
- Node.js on premises: `submitQueue`, `submitTopic`, `putObject` and `deleteObject` in `pskit`, like the Python helpers (through `PSKIT_HOST_URL`).
|
|
988
|
+
|
|
989
|
+
### Fixed
|
|
990
|
+
- On premises: an ElasticMQ queue created on an SSH server failed with `QueueDoesNotExist`: the queue was created from this machine (often firewalled) and ElasticMQ forgets queues on restart. It is now created from the server over SSH when needed, and the `sqs` driver recreates a missing queue (`create_queue`, on by default for non-AWS endpoints).
|
|
991
|
+
|
|
992
|
+
## [1.3.0] - 2026-10-22
|
|
993
|
+
|
|
994
|
+
### Added
|
|
995
|
+
- **Resource guides** (`docs/resource-guides/`): step-by-step pages per provider and resource type (storage, queue, topic, database, cache, custom) for AWS, GCP, Azure, Alibaba, Tencent, Huawei, Oracle, IBM, DigitalOcean, Cloudflare and on premises: how to create the service in the console, where to find each value, the `pskit.yml` to attach it as an external resource, a handler snippet, how to test it and common errors.
|
|
996
|
+
- **One-click on-prem services** (`pskit resources onprem create|list|status|logs|backup|remove|catalog`, studio *Resources → On-prem services*): start Redis, Valkey, Kafka (Redpanda), NATS JetStream, RabbitMQ, ElasticMQ (SQS API), MinIO, PostgreSQL, MySQL, MariaDB, MongoDB, Memcached or Mailpit as a Docker container on this machine or any SSH server (the functions' server or another one; Docker is installed there when missing), or install Python / Docker on a server. The resource, its triggers on the functions you pick and `provider.options.env_file` are added to `pskit.yml`; generated passwords go to `.env.onprem`. Kafka, NATS and RabbitMQ get a driver class in `pskit_drivers/` and their client library in `requirements.txt`. Backups stream into `.pskit/backups/`.
|
|
997
|
+
- **`redis_stream` queue driver**: a Redis 6.2+ / Valkey stream with a consumer group (native leases and delivery counts, crash takeover with `XAUTOCLAIM`, several hosts per group). Offered as the *stream* role of Redis and Valkey.
|
|
998
|
+
- **`pskit_host` queue driver**: functions on one on-prem host consume the built-in queue of another, through new lease endpoints `POST /__pskit/queues/<name>/lease|ack|nack` (at-least-once).
|
|
999
|
+
- On premises: `provider.options.env_file` ships a `KEY=VALUE` file with the host (`host.env`) for local, SSH and Docker deploys and loads it at start, so `<name>_env` secrets need no systemd or container configuration and never reach Terraform state. `GET /__pskit/resources` lists resources with their backend, consumers and queue depth.
|
|
1000
|
+
- Studio: **Guides** shows the resource guides for every cloud in the app, with *How to set up* links from the resource form.
|
|
1001
|
+
|
|
1002
|
+
### Fixed
|
|
1003
|
+
- On premises: a driver-backed queue or bucket that no trigger consumes (only published to with `submit_queue` / `put_object` / `pskit resources send`, or used as a `dead_letter`) silently went to a local folder; drivers are now bound from `resources:` too. `dead_letter` may name a resource key. Managed queues, buckets and topics no event uses are created when the host starts.
|
|
1004
|
+
- On premises (Windows): deploy failed with `WinError 206` when vendored packages made the staging path longer than 260 characters.
|
|
1005
|
+
- `examples/19-custom-drivers/app/kafka_queue.py` polled with a zero timeout, so the consumer never joined its group and received nothing.
|
|
1006
|
+
- `runtime_js/package.json` version now follows `__version__` (it was left at 1.2.0 in 1.2.1).
|
|
1007
|
+
|
|
1008
|
+
## [1.2.0] - 2026-10-21
|
|
1009
|
+
|
|
1010
|
+
### Added
|
|
1011
|
+
- **Test resources directly**: `pskit resources send KEY` sends a message to a queue, uploads an object to a bucket or publishes to a topic, for managed resources (once deployed) and external / custom-named ones (right away). `pskit resources send --list` shows how to test every resource: sample payload, pskit and cloud CLI commands and console steps; for database, cache and custom resources it shows the `PSKIT_RESOURCE_*` variables and a Python / Node.js snippet. Studio: **Test a resource** panel and a **Test** button on every resource row.
|
|
1012
|
+
|
|
1013
|
+
### Fixed
|
|
1014
|
+
- Azure: `pskit resources send` and `pskit trigger` read the storage account and Service Bus connection strings from the deployment's Terraform state, so `AZURE_STORAGE_CONNECTION_STRING` / `AZURE_SERVICEBUS_CONNECTION_STRING` are only needed as overrides. The error now shows the `az` command that prints them.
|
|
1015
|
+
|
|
1016
|
+
## [1.1.0] - 2026-10-21
|
|
1017
|
+
|
|
1018
|
+
### Added
|
|
1019
|
+
- **Test functions with real events**: `pskit trigger` sends a test event to a deployed function through its trigger: an HTTP request, an SQS / Pub/Sub / Storage-queue / on-prem queue message, an S3 / GCS / Blob / on-prem upload, an SNS / Pub/Sub / Service Bus / on-prem topic message, or a direct invocation. `pskit trigger --list` shows, for every function and trigger, a sample payload, the local `pskit invoke` command, the `pskit trigger` command, the cloud's own CLI command and the console steps. Studio **Test** page: pick a trigger, edit or save the event, then Run locally or Send to the deployed stage with live logs, plus a How-to-test panel (studio, terminal, console).
|
|
1020
|
+
- `pskit resources list | delete`: list the buckets, queues and topics pskit created (deployed, or kept by `--keep-resources`) and delete them permanently. Kept ones are remembered in `.pskit/<provider>-<stage>/kept/`, so they can be deleted after the stage is gone. Studio: **Resources → In the cloud**, with select, delete selected and delete all kept.
|
|
1021
|
+
|
|
1022
|
+
## [1.0.0] - 2026-10-21
|
|
1023
|
+
|
|
1024
|
+
### Added
|
|
1025
|
+
- **Node.js and TypeScript functions** (`provider.runtime: nodejs18 | nodejs20 | nodejs22 | nodejs24`) on every provider. A service is either Python or Node.js. Handlers use the same `module.function` form, and the `pskit` package (vendored as `pskit_runtime/`) has the same Event / Context / Response / BatchResult API in camelCase, plus `invoke()`, resources and the embedded workflow engine. TypeScript is compiled with `tsc` while packaging (`package.node`). The on-prem host and `pskit dev` / `pskit invoke` run Node.js handlers through a JSON-lines worker. See `docs/nodejs.md` and `deploy_docs/NODE_RUNTIME.md`.
|
|
1026
|
+
- `pskit remove --keep-resources`: destroy functions and triggers but keep managed buckets, queues and topics with their data (they leave the Terraform state). Studio's Deploy page has the matching switch.
|
|
1027
|
+
- Studio:
|
|
1028
|
+
- **Project environment** creates `.venv` with a chosen interpreter and installs `requirements.txt`, or runs `npm install` for Node.js services.
|
|
1029
|
+
- Full VS Code: pick Python and Node.js versions; studio builds a code-server image with them once.
|
|
1030
|
+
- Triggers: **Create & select** adds a new queue, bucket or topic to Resources and selects it.
|
|
1031
|
+
- JS/TS editing: highlighting, handler stubs in TypeScript or ESM/CommonJS JavaScript, and Node.js runtimes in the runtime pickers.
|
|
1032
|
+
- On-prem deploy fields for Node.js (`node`, `node_url`, `node_sha256`, `host_python`).
|
|
1033
|
+
|
|
1034
|
+
## [0.9.0] - 2026-10-21
|
|
1035
|
+
|
|
1036
|
+
### Added
|
|
1037
|
+
- `enabled: false` on functions and workflows: kept in `pskit.yml`, skipped on deploy. Combined with `providers.<cloud>` overrides it switches items (or single triggers) off on one cloud only.
|
|
1038
|
+
- **Azure native workflows** on Azure Logic Apps (Consumption) with `engine: native` (`auto` stays embedded). The pskit output includes the trigger callback URL, and `pskit workflow start` uses it. Azure also outputs `log_analytics_workspace_id` when Application Insights is on.
|
|
1039
|
+
- **Cloud logs** (`core/cloud_logs.py`): `pskit logs` and the dashboard read logs from AWS CloudWatch, GCP Cloud Logging and Azure Log Analytics, as well as on-prem. Log streams can be listed and deleted (AWS, on-prem) with `pskit logs --streams / --delete / --delete-all` and in the dashboard. On-prem hosts gain `GET /__pskit/logs/streams` and `DELETE /__pskit/logs`.
|
|
1040
|
+
- **`pskit doctor`** (`core/setup_check.py`): checks Terraform, the cloud CLI, credentials, required provider options and on-prem SSH/Docker, with download links and per-OS install steps.
|
|
1041
|
+
- `pskit --help` lists every command and workflow subcommand with examples; help is no longer truncated.
|
|
1042
|
+
- Studio:
|
|
1043
|
+
- **Setup & credentials** page: the checks above, an `aws configure`-style profile form, provider environment variables for the session, browser logins (`az login`, `gcloud auth ...`) and an SSH connection test.
|
|
1044
|
+
- **Logs** page and per-function live logs: tail, list streams, delete selected or all.
|
|
1045
|
+
- File picker for the on-prem SSH private key.
|
|
1046
|
+
- Dropdowns (with a custom value) for region, stage, memory, timeout, log retention, plan SKUs, SSH user, timezone and more.
|
|
1047
|
+
- Schedules **at a specific time**: daily, weekdays, chosen days, monthly or yearly at HH:MM in a timezone.
|
|
1048
|
+
- Trigger options each provider rejects or ignores are derived from its validation and shown in the form. Unsupported auth modes are disabled, and only supported trigger types are offered.
|
|
1049
|
+
- The queue, bucket and topic source picker offers a new resource, a project resource, a pick from the cloud account (optionally added as an external resource), or a typed name.
|
|
1050
|
+
- Enable or disable a function or workflow everywhere or only on the current provider. Before deploy, and when switching provider, unsupported items are listed with a one-click "disable on this provider".
|
|
1051
|
+
- Clear the recent jobs list (all finished jobs, or one).
|
|
1052
|
+
|
|
1053
|
+
## [0.8.0] - 2026-10-21
|
|
1054
|
+
|
|
1055
|
+
### Added
|
|
1056
|
+
- **`pskit studio`**: a local web UI to build a project without writing YAML.
|
|
1057
|
+
- New-project wizard; provider cards for all 11 targets with their capabilities; provider, region, runtime and provider-option forms; on-prem deploy method, services and tuning.
|
|
1058
|
+
- AWS-console-style **Create function** wizard. Trigger types follow what the selected provider supports, with HTTP path-parameter preview and CORS/auth, a cron/rate builder, and a queue/storage/topic source picker (new, from Resources, **Browse account** or typed).
|
|
1059
|
+
- Visual workflow builder: a diagram plus an inspector for every state type, choice rule groups, retry/catch, and nested parallel/map.
|
|
1060
|
+
- Resources with an on-prem driver picker for every built-in driver and custom classes; secret fields read from env vars.
|
|
1061
|
+
- Code page with a CodeMirror editor, or **Full VS Code**: code-server pulled into Docker on demand, run on the project and embedded.
|
|
1062
|
+
- Deploy page (validate/package/plan/deploy/info/remove with live logs, invoke, local workflow runs); raw-YAML mode with a diff against disk.
|
|
1063
|
+
- Edits stay in a draft that is validated live and saved with backups and conflict detection. `${...}` values are kept as written.
|
|
1064
|
+
- Session token, loopback bind, Host/Origin checks. See `docs/studio.md`.
|
|
1065
|
+
- Studio account discovery: lists existing SQS queues, S3 buckets, SNS topics and state machines (boto3); Pub/Sub topics and subscriptions and GCS buckets (google-cloud-*); Azure queues and containers (connection string); and on-prem directories.
|
|
1066
|
+
- `providers/onprem_catalog.py`: a data catalog of on-prem driver fields, kept in sync with validation by a test.
|
|
1067
|
+
|
|
1068
|
+
### Fixed
|
|
1069
|
+
- The dashboard server reads a POST body before rejecting the request (403/415), so Windows no longer resets the connection before the client reads the error.
|
|
1070
|
+
|
|
1071
|
+
## [0.7.0] - 2026-10-21
|
|
1072
|
+
|
|
1073
|
+
### Added
|
|
1074
|
+
- On-premises drivers that watch queues and buckets in other providers: `sqs` (AWS, JSON protocol + SigV4), `azure_queue` and `azure_blob` (Shared Key, SAS or connection string; Azurite), `pubsub` (pull subscription) and `gcs` (access token, `token_command` or the metadata server; emulators), `mns` (Alibaba Cloud) and `cloudflare_queue` (HTTP pull consumer). Leases use each service's own visibility timeout, so delivery stays at-least-once. See the provider matrix in `docs/resources.md`.
|
|
1075
|
+
- S3 storage presets `aws`, `oss`, `cos`, `obs`, `oci`, `ibm_cos`, `spaces`, `r2` and `minio` (or `driver: s3` + `provider:`). `s3` without `endpoint` now targets AWS (virtual-host style), and credentials fall back to the `AWS_*` environment variables.
|
|
1076
|
+
- `custom` queue and storage drivers: `class: package.module:ClassName` from your app, constructed with the remaining options. Import errors, constructor errors and missing methods are reported with the class name. `docs/resources.md` has a RabbitMQ example (AMQP with manual acks).
|
|
1077
|
+
- Any on-prem driver parameter can be written as `<name>_env: VARIABLE`, read from the host's environment at start, so secrets stay out of `pskit_host.json` and Terraform state.
|
|
1078
|
+
- `examples/19-custom-drivers`: runnable `custom` drivers (`SqliteQueue` with visibility timeout, receive counts and a dead-letter table; `FolderStorage` for local/NFS/SMB folders) plus RabbitMQ (pika) and Kafka (kafka-python) templates, all at-least-once.
|
|
1079
|
+
- `examples/20-onprem-external-clouds`: one on-prem host consuming SQS, Azure Storage Queue, Pub/Sub, MNS and Cloudflare Queues and watching S3, Azure Blob, GCS, R2 and MinIO, with every secret read through `*_env`.
|
|
1080
|
+
|
|
1081
|
+
### Fixed
|
|
1082
|
+
- The on-premises host makes the app importable before building its queue/storage drivers, so a `custom` driver class from the app loads at start.
|
|
1083
|
+
- The on-premises host sets `PSKIT_ONPREM_ROOT` before building its drivers, so relative paths in driver options resolve against the host directory.
|
|
1084
|
+
|
|
1085
|
+
## [0.6.0] - 2026-10-21
|
|
1086
|
+
|
|
1087
|
+
### Added
|
|
1088
|
+
- **`resources:`** for storage, queues, topics, databases, caches and custom services. A resource is managed (pskit creates it) or `external: true` (pskit only attaches it). Bound functions get `PSKIT_RESOURCES` and `PSKIT_RESOURCE_<KEY>_TYPE/NAME/EXTERNAL/<connection key>` variables, plus `ARN`/`URL` on AWS and `ID` for Pub/Sub on GCP. `functions:` limits which functions get a binding. `queue`, `storage` and `topic` events accept `resource: <key>`. Standalone managed resources are created on AWS, GCP, Azure and on premises; other providers report a validation error. AWS roles get a `pskit-resources` policy for the bound resources. See `docs/resources.md`.
|
|
1089
|
+
- On-premises `provider.options` `execution_retention`, `workflow_workers`, `log_buffer`, `log_level` and `capture_output` to tune the host's execution store, workflow concurrency and log capture.
|
|
1090
|
+
- `resource()`, `resources()` and `Resource` in `py_serverless_kit`, to read bindings the same way on every cloud.
|
|
1091
|
+
- On-premises drivers for resources: `redis` queues (stdlib RESP client; `<key>`, `<key>:processing` and `<key>:claims`, with crash recovery) and `s3` storage (SigV4, MinIO and any S3-compatible store, `prefix`, `path_style`, `session_token`), plus a per-resource `directory`. Unreachable backends become host notes and the host keeps running.
|
|
1092
|
+
- Workflow execution ids everywhere. The on-premises host tracks runs in `<data_dir>/executions/`: status, current state, history (`enter`/`exit`/`caught`/`retry`/`fail`), input, output and error. `GET /__pskit/executions[/<id>]` and `POST /__pskit/executions/<id>/cancel` inspect and control runs. Cancel stops before the next state and wakes `wait` states. `workflows.<name>.timeout` is enforced by the embedded engine (`TIMED_OUT`), and runs interrupted by a restart become `ABORTED`. Cloud orchestrators return `execution_id` with their synchronous result. See `docs/workflow-executions.md`.
|
|
1093
|
+
- `pskit workflow start | executions | status | cancel` for deployed workflows on the on-premises host, AWS Step Functions (`pip install "py-serverless-kit[aws]"`) and Google Cloud Workflows (new `[gcp]` extra: `google-cloud-workflows`).
|
|
1094
|
+
- On-premises logs: the host captures logging, `print`/stdout/stderr, one entry per invocation and host notes, tagged with function and request id, in memory and in `<data_dir>/logs/host.jsonl` (rotated). `GET /__pskit/logs` (`since`, `before`, `limit`, `level`, `function`, `source`, `q`), `GET /__pskit/stats` (invocations, errors and durations per function, queue depths), and `pskit logs [-f]`.
|
|
1095
|
+
- A new React + Vite dashboard (single self-contained page) with sortable, paginated tables, deployment tabs (Functions, Workflows, Executions, Logs, Resources, Outputs) and light/dark themes. `pskit dashboard --serve` (new `--host`) adds a JSON API for live host health and stats, a log tail, and workflow executions (list, start, follow, cancel). The API checks the Host header and same-origin POSTs and keeps admin tokens server-side.
|
|
1096
|
+
- `docs/scenarios.md`: step-by-step guides by use case.
|
|
1097
|
+
|
|
1098
|
+
### Changed
|
|
1099
|
+
- **Breaking (on premises):** `POST /workflows/<name>` and `POST /__pskit/workflows/<name>` start the workflow in the background and answer `202 {"execution_id", "status": "RUNNING", "status_url", ...}`. Add `?wait=true` (or `Prefer: wait`, or `x-pskit-wait: true`) to get the old synchronous result. That result now also includes `execution_id`, `started_at` and `stopped_at`.
|
|
1100
|
+
- `deployment.json` (and `pskit info --json`) include the deployment `key` (`<provider>-<stage>`) and `resources` (connection key names only).
|
|
1101
|
+
|
|
1102
|
+
### Fixed
|
|
1103
|
+
- The on-premises host drains the request body before answering `401` for a missing admin token. On Windows the client previously saw a connection reset instead of the 401.
|
|
1104
|
+
- Re-validating a dumped config no longer leaves each event's config as a plain dict.
|
|
1105
|
+
|
|
1106
|
+
Redeploy to pick up the new runtime. Handler code is unchanged.
|
|
1107
|
+
|
|
1108
|
+
## [0.5.2] - 2026-10-19
|
|
1109
|
+
|
|
1110
|
+
### Fixed
|
|
1111
|
+
- On-premises SSH deploy as a normal user such as `azureuser`. With `deploy.sudo: true`, apply creates `deploy.path` with `sudo -n mkdir` and `chown`s it to the SSH user before `scp`. A user who cannot write `/opt` no longer fails with `Permission denied`.
|
|
1112
|
+
|
|
1113
|
+
Redeploy the on-premises host after upgrading. Handler code is unchanged.
|
|
1114
|
+
|
|
1115
|
+
## [0.5.1] - 2026-10-19
|
|
1116
|
+
|
|
1117
|
+
### Fixed
|
|
1118
|
+
- On-premises `python: bundle` on Windows. Unpacking a Linux CPython into the project raised `WinError 206` (`The filename or extension is too long`) on setuptools test files under `pkg_resources/tests`. A remote deploy now copies that archive straight into `release.tar.gz` and leaves those test files out. A partial `onprem_app/python` tree from the failed unpack is removed on the next deploy.
|
|
1119
|
+
|
|
1120
|
+
Redeploy the on-premises host after upgrading. Handler code is unchanged.
|
|
1121
|
+
|
|
1122
|
+
## [0.5.0] - 2026-10-19
|
|
1123
|
+
|
|
1124
|
+
### Changed
|
|
1125
|
+
- On-premises remote deploy copies one `release.tar.gz` with `scp` and starts it from a script on the server. `options.deploy.method: scp` is the same path as `ssh`. A `.pem` (`pem` or `identity_file`) is passed with `IdentitiesOnly`. `pskit deploy` asks for that path on a terminal for SSH as well as Docker; press Enter on the SSH prompt to keep the SSH agent or the default key. Docker on a server still requires a key.
|
|
1126
|
+
- The server script restarts a systemd unit (`systemctl restart`, so a redeploy replaces the running process), installs and starts Docker when `method: docker` and `docker` is missing, and uses `sudo -n` so a missing sudoers rule fails immediately. It exports a normal `PATH` (non-login SSH often cannot see `systemctl` or `python3`). `pskit-run.sh` starts a bundled CPython when one was copied, then `python3.x`, then `python3`.
|
|
1127
|
+
- Apply waits until `http://127.0.0.1:<port>/__pskit/health` answers. A dead process or container fails the deploy and prints `journalctl` or `docker logs`. A process that binds `0.0.0.0` is checked on `127.0.0.1`, including when `advertise` is a public URL.
|
|
1128
|
+
|
|
1129
|
+
Redeploy on-premises hosts to pick up the new provisioner. Handler code is unchanged.
|
|
1130
|
+
|
|
1131
|
+
## [0.4.0] - 2026-10-19
|
|
1132
|
+
|
|
1133
|
+
### Added
|
|
1134
|
+
- On-premises Docker deploy to a server. Set `options.deploy.method: docker` and `options.deploy.host`. `pskit deploy` asks for a `.pem` private key when `options.deploy.pem` is unset (`identity_file` is the same field). The image is built on the machine that runs `pskit`, copied over SSH, and started with `docker run`. If `docker` is missing on the server, apply installs it (`docker.io` via apt, `docker` via dnf or yum, or `docker` via apk) and then loads the image. `install_docker: false` skips the install and fails if Docker is absent. `sudo` defaults to true for this path so the SSH user can install and start the daemon.
|
|
1135
|
+
|
|
1136
|
+
Redeploy on-premises Docker hosts to pick up the new provisioner. Handler code is unchanged.
|
|
1137
|
+
|
|
1138
|
+
## [0.3.0] - 2026-10-17
|
|
1139
|
+
|
|
1140
|
+
### Added
|
|
1141
|
+
- On-premises deploy targets. `provider.options.deploy.method` is `local` (default, previous behaviour), `ssh` (copy the host over OpenSSH and start a process or systemd unit), or `docker` (build an image that already contains Python). When the server has no Python, set `python: bundle` to ship a portable CPython, or use `method: docker`. `python_home` / `python_url` cover air-gapped mirrors. Wheels are vendored for the target OS/arch (manylinux when the server is Linux).
|
|
1142
|
+
- Example [17-on-premises-remote](examples/17-on-premises-remote): SSH + bundled interpreter + systemd.
|
|
1143
|
+
|
|
1144
|
+
### Fixed
|
|
1145
|
+
- On-prem host: Windows process helpers (`ctypes.windll`, `subprocess.DETACHED_PROCESS`) are gated on `sys.platform == "win32"` so mypy on Linux/macOS CI no longer reports missing attributes.
|
|
1146
|
+
|
|
1147
|
+
Redeploy on-premises hosts to pick up the new `onprem_deploy.py` provisioner. Handler code is unchanged.
|
|
1148
|
+
|
|
1149
|
+
## [0.2.0] - 2026-10-17
|
|
1150
|
+
|
|
1151
|
+
### Added
|
|
1152
|
+
- On-premises provider (`provider.name: onprem`). `pskit deploy` starts one long-lived Python process on the machine that runs the command. HTTP is served directly. Schedules, file queues (with dead-letter and partial batch failure), directory storage and file topics are created at start when they do not already exist. Point `provider.options.services.<kind>` at `{use: directory, path: ...}` to use a directory you already have. `existing: true` waits for that directory instead of creating it. Workflows run on the embedded engine inside the host, and `invoke()` stays in-process. `pskit remove` stops the process and leaves the data directory in place.
|
|
1153
|
+
- Example [16-on-premises](examples/16-on-premises). Every other example has an `providers.onprem` block (its own port, public auth where a cloud authorizer does not apply, local state where the file used a cloud backend).
|
|
1154
|
+
|
|
1155
|
+
No change to handlers that already run on a cloud. Redeploy to pick up the new runtime if you use `BatchResult` or `invoke()` on premises.
|
|
1156
|
+
|
|
1157
|
+
## [0.1.3] - 2026-10-15
|
|
1158
|
+
|
|
1159
|
+
### Fixed
|
|
1160
|
+
- AWS: `pskit deploy` failed with `creating Lambda Function ...: decomposing request: bufio.Scanner: token too long` once the bundle (e.g. with vendored dependencies) got large, because the zip was sent inline in every `CreateFunction` request. The artifact is now uploaded once to S3 (`aws_s3_object`) and each Lambda function references it via `s3_bucket`/`s3_key`. This also lifts the 50 MB inline upload limit.
|
|
1161
|
+
|
|
1162
|
+
### Added
|
|
1163
|
+
- AWS options `artifact_bucket` (use an existing bucket for code uploads instead of the private `<service>-<stage>-code-*` bucket pskit creates) and `artifact_upload: s3 | direct` (`direct` restores the old inline upload).
|
|
1164
|
+
|
|
1165
|
+
No runtime changes. Existing AWS deployments get a new code bucket on the next `pskit deploy`; Lambda functions are updated in place.
|
|
1166
|
+
|
|
1167
|
+
## [0.1.2] - 2026-10-15
|
|
1168
|
+
|
|
1169
|
+
### Fixed
|
|
1170
|
+
- Python 3.9 support: `pskit package`/`deploy` (and the Cloudflare provider) crashed with `TypeError: write_text() got an unexpected keyword argument 'newline'`, because `Path.write_text(newline=...)` only exists on Python 3.10+. Generated files are now written as UTF-8 bytes with `\n` line endings on every Python version.
|
|
1171
|
+
- GCP adapter: the storage object `size` check now narrows `None` explicitly, so mypy passes on Python 3.9 CI. Runtime behavior is unchanged.
|
|
1172
|
+
|
|
1173
|
+
No runtime behavior changes: functions deployed with 0.1.1 don't need to be redeployed.
|
|
1174
|
+
|
|
1175
|
+
## [0.1.1] - 2026-10-15
|
|
1176
|
+
|
|
1177
|
+
### Changed
|
|
1178
|
+
- Author and maintainer set to Asif Khan @ Kavion.ai (`py_serverless_kit.__author__`, package metadata, LICENSE).
|
|
1179
|
+
- Project URLs (homepage, docs, issues, changelog) now point to https://github.com/kavion-ai/py-serverless-kit.
|
|
1180
|
+
- README links are absolute so they work on the PyPI project page; added CI/PyPI/license badges.
|
|
1181
|
+
- `scripts/validate_all_providers.py` explains that Terraform is optional instead of printing a traceback when it isn't installed.
|
|
1182
|
+
|
|
1183
|
+
### Added
|
|
1184
|
+
- `deploy_docs/How_to_deploy.md`: short PyPI release guide with PowerShell commands and troubleshooting (e.g. TestPyPI `403`).
|
|
1185
|
+
- `deploy_docs/HOW_TO_INSTALL_TERRAFORM.md`: installing Terraform on Windows.
|
|
1186
|
+
|
|
1187
|
+
No runtime changes: functions deployed with 0.1.0 don't need to be redeployed.
|
|
1188
|
+
|
|
1189
|
+
## [0.1.0] - 2026-10-15
|
|
1190
|
+
|
|
1191
|
+
### Added
|
|
1192
|
+
- Portable handler API: `Event`, `HttpRequest`, `Record`, `Headers`, `Context`, `Response`, HTTP error classes, `BatchResult`, `invoke()`.
|
|
1193
|
+
- `pskit.yml` configuration with `extends:`, `providers:` and `stages:` overrides, and `${env:}`, `${opt:}`, `${self:}`, `${file()}` and `${tf:}` variables.
|
|
1194
|
+
- Providers: AWS (stable), Google Cloud (stable), Azure (stable), Alibaba Cloud (beta), Huawei Cloud (beta), Tencent Cloud (beta), DigitalOcean (beta), IBM Cloud (beta), Oracle Cloud (experimental), Cloudflare Workers (experimental).
|
|
1195
|
+
- Triggers: HTTP (path params, CORS, auth), schedule (rate/cron), queue, storage, topic.
|
|
1196
|
+
- Workflows: native AWS Step Functions and Google Cloud Workflows compilers, plus an embedded engine for the other providers and local runs.
|
|
1197
|
+
- CLI: `init`, `validate`, `package`, `plan`, `deploy`, `remove`, `info`, `dashboard`, `dev`, `invoke`, `workflow run|show`, `providers`, `tf`.
|
|
1198
|
+
- Deployment dashboard (self-contained HTML).
|
|
1199
|
+
- Local dev server with hot reload, and `LocalRunner` for tests.
|
|
1200
|
+
- `scripts/validate_all_providers.py`, which runs `terraform validate` for every provider.
|