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