pam-python 0.1.31__tar.gz → 0.1.32__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.
- {pam_python-0.1.31 → pam_python-0.1.32}/PKG-INFO +1 -1
- {pam_python-0.1.31 → pam_python-0.1.32}/pam/templates/init/AGENT.md +6 -0
- {pam_python-0.1.31 → pam_python-0.1.32}/pam_python.egg-info/PKG-INFO +1 -1
- {pam_python-0.1.31 → pam_python-0.1.32}/setup.py +1 -1
- {pam_python-0.1.31 → pam_python-0.1.32}/LICENSE.txt +0 -0
- {pam_python-0.1.31 → pam_python-0.1.32}/README.md +0 -0
- {pam_python-0.1.31 → pam_python-0.1.32}/pam/__init__.py +0 -0
- {pam_python-0.1.31 → pam_python-0.1.32}/pam/api.py +0 -0
- {pam_python-0.1.31 → pam_python-0.1.32}/pam/cli.py +0 -0
- {pam_python-0.1.31 → pam_python-0.1.32}/pam/interface_task_manager.py +0 -0
- {pam_python-0.1.31 → pam_python-0.1.32}/pam/models/__init__.py +0 -0
- {pam_python-0.1.31 → pam_python-0.1.32}/pam/models/request_command.py +0 -0
- {pam_python-0.1.31 → pam_python-0.1.32}/pam/server.py +0 -0
- {pam_python-0.1.31 → pam_python-0.1.32}/pam/service.py +0 -0
- {pam_python-0.1.31 → pam_python-0.1.32}/pam/sqlite.py +0 -0
- {pam_python-0.1.31 → pam_python-0.1.32}/pam/task_manager.py +0 -0
- {pam_python-0.1.31 → pam_python-0.1.32}/pam/temp_file_utils.py +0 -0
- {pam_python-0.1.31 → pam_python-0.1.32}/pam/templates/buildcmd/pamb +0 -0
- {pam_python-0.1.31 → pam_python-0.1.32}/pam/templates/buildcmd/pamb-base.sh +0 -0
- {pam_python-0.1.31 → pam_python-0.1.32}/pam/templates/docker/Dockerfile +0 -0
- {pam_python-0.1.31 → pam_python-0.1.32}/pam/templates/init/dockerignore.tmpl +0 -0
- {pam_python-0.1.31 → pam_python-0.1.32}/pam/templates/init/gitignore.tmpl +0 -0
- {pam_python-0.1.31 → pam_python-0.1.32}/pam/templates/init/main.tmpl +0 -0
- {pam_python-0.1.31 → pam_python-0.1.32}/pam/templates/init/pylintrc.tmpl +0 -0
- {pam_python-0.1.31 → pam_python-0.1.32}/pam/templates/init/run_unit_test.bat +0 -0
- {pam_python-0.1.31 → pam_python-0.1.32}/pam/templates/init/run_unit_test.ps1 +0 -0
- {pam_python-0.1.31 → pam_python-0.1.32}/pam/templates/init/run_unit_test.sh +0 -0
- {pam_python-0.1.31 → pam_python-0.1.32}/pam/templates/service/functions.tmpl +0 -0
- {pam_python-0.1.31 → pam_python-0.1.32}/pam/templates/service/service.test.tmpl +0 -0
- {pam_python-0.1.31 → pam_python-0.1.32}/pam/templates/service/service.yaml +0 -0
- {pam_python-0.1.31 → pam_python-0.1.32}/pam/templates/service/service_class.tmpl +0 -0
- {pam_python-0.1.31 → pam_python-0.1.32}/pam/tester_task.py +0 -0
- {pam_python-0.1.31 → pam_python-0.1.32}/pam/utils.py +0 -0
- {pam_python-0.1.31 → pam_python-0.1.32}/pam_python.egg-info/SOURCES.txt +0 -0
- {pam_python-0.1.31 → pam_python-0.1.32}/pam_python.egg-info/dependency_links.txt +0 -0
- {pam_python-0.1.31 → pam_python-0.1.32}/pam_python.egg-info/entry_points.txt +0 -0
- {pam_python-0.1.31 → pam_python-0.1.32}/pam_python.egg-info/requires.txt +0 -0
- {pam_python-0.1.31 → pam_python-0.1.32}/pam_python.egg-info/top_level.txt +0 -0
- {pam_python-0.1.31 → pam_python-0.1.32}/setup.cfg +0 -0
|
@@ -19,6 +19,12 @@ This document explains the data plugin service lifecycle so developers can creat
|
|
|
19
19
|
The value `endpoint: /Rfm_segmentSvc` means CDP will call:
|
|
20
20
|
`http://ip-of-this-k8s-pod/services/Rfm_segmentSvc`
|
|
21
21
|
|
|
22
|
+
### Code Organization Guidelines
|
|
23
|
+
|
|
24
|
+
- Separate each lifecycle step into clear, dedicated functions. Add comments at critical points so humans can review and audit later.
|
|
25
|
+
- Avoid nested functions unless absolutely necessary.
|
|
26
|
+
- Put service logic in `[service_name]/functions.py`, then import and use it from the service class to keep the overall code easy to read.
|
|
27
|
+
|
|
22
28
|
## Service Lifecycle
|
|
23
29
|
|
|
24
30
|
CDP spawns a service instance when a job starts and terminates it after the job completes. This design supports parallel execution. For example, two runs will spawn two separate instances. The only risk is shared local files (e.g., sqlite) which can cause conflicts.
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|