zipher-sdk 0.4.4__tar.gz → 0.4.5__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 (25) hide show
  1. {zipher-sdk-0.4.4/zipher_sdk.egg-info → zipher-sdk-0.4.5}/PKG-INFO +14 -1
  2. {zipher-sdk-0.4.4 → zipher-sdk-0.4.5}/README.md +13 -0
  3. {zipher-sdk-0.4.4 → zipher-sdk-0.4.5}/setup.py +1 -1
  4. {zipher-sdk-0.4.4 → zipher-sdk-0.4.5/zipher_sdk.egg-info}/PKG-INFO +14 -1
  5. {zipher-sdk-0.4.4 → zipher-sdk-0.4.5}/LICENSE +0 -0
  6. {zipher-sdk-0.4.4 → zipher-sdk-0.4.5}/setup.cfg +0 -0
  7. {zipher-sdk-0.4.4 → zipher-sdk-0.4.5}/tests/__init__.py +0 -0
  8. {zipher-sdk-0.4.4 → zipher-sdk-0.4.5}/tests/test_acl/__init__.py +0 -0
  9. {zipher-sdk-0.4.4 → zipher-sdk-0.4.5}/tests/test_acl/sample_job.py +0 -0
  10. {zipher-sdk-0.4.4 → zipher-sdk-0.4.5}/tests/test_acl/test_acl.py +0 -0
  11. {zipher-sdk-0.4.4 → zipher-sdk-0.4.5}/tests/test_client.py +0 -0
  12. {zipher-sdk-0.4.4 → zipher-sdk-0.4.5}/zipher/__init__.py +0 -0
  13. {zipher-sdk-0.4.4 → zipher-sdk-0.4.5}/zipher/acl/__init__.py +0 -0
  14. {zipher-sdk-0.4.4 → zipher-sdk-0.4.5}/zipher/acl/models.py +0 -0
  15. {zipher-sdk-0.4.4 → zipher-sdk-0.4.5}/zipher/acl/zipher_installer.py +0 -0
  16. {zipher-sdk-0.4.4 → zipher-sdk-0.4.5}/zipher/cli.py +0 -0
  17. {zipher-sdk-0.4.4 → zipher-sdk-0.4.5}/zipher/client.py +0 -0
  18. {zipher-sdk-0.4.4 → zipher-sdk-0.4.5}/zipher/exceptions.py +0 -0
  19. {zipher-sdk-0.4.4 → zipher-sdk-0.4.5}/zipher/models.py +0 -0
  20. {zipher-sdk-0.4.4 → zipher-sdk-0.4.5}/zipher/utils.py +0 -0
  21. {zipher-sdk-0.4.4 → zipher-sdk-0.4.5}/zipher_sdk.egg-info/SOURCES.txt +0 -0
  22. {zipher-sdk-0.4.4 → zipher-sdk-0.4.5}/zipher_sdk.egg-info/dependency_links.txt +0 -0
  23. {zipher-sdk-0.4.4 → zipher-sdk-0.4.5}/zipher_sdk.egg-info/entry_points.txt +0 -0
  24. {zipher-sdk-0.4.4 → zipher-sdk-0.4.5}/zipher_sdk.egg-info/requires.txt +0 -0
  25. {zipher-sdk-0.4.4 → zipher-sdk-0.4.5}/zipher_sdk.egg-info/top_level.txt +0 -0
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.1
2
2
  Name: zipher-sdk
3
- Version: 0.4.4
3
+ Version: 0.4.5
4
4
  Summary: Python SDK for programmatic access to the Zipher API
5
5
  Home-page: UNKNOWN
6
6
  Author: Zipher Inc.
@@ -136,6 +136,19 @@ optimized_cluster = client.update_existing_conf(job_id="my-job-id", existing_con
136
136
 
137
137
  ```
138
138
 
139
+ #### Optional: passing per-run parameters
140
+
141
+ You can specify run-level parameters that Zipher will take into consideration. This is useful for parametrized jobs, where Zipher can explicitly learn the different usage patterns of different parametes.
142
+
143
+
144
+ ```python
145
+ optimized_cluster = client.update_existing_conf(
146
+ job_id="my-job-id",
147
+ existing_conf=config_payload,
148
+ run_params={"customer_ids": ["c1", "c2"], "lookback_days": "30"},
149
+ )
150
+ ```
151
+
139
152
  ### Update Existing Multiple Tasks Configuration
140
153
 
141
154
  You can update multiple databricks tasks by initializing a zipher Client and sending a JSON representing a list of dbx SubmitTask objects to
@@ -121,6 +121,19 @@ optimized_cluster = client.update_existing_conf(job_id="my-job-id", existing_con
121
121
 
122
122
  ```
123
123
 
124
+ #### Optional: passing per-run parameters
125
+
126
+ You can specify run-level parameters that Zipher will take into consideration. This is useful for parametrized jobs, where Zipher can explicitly learn the different usage patterns of different parametes.
127
+
128
+
129
+ ```python
130
+ optimized_cluster = client.update_existing_conf(
131
+ job_id="my-job-id",
132
+ existing_conf=config_payload,
133
+ run_params={"customer_ids": ["c1", "c2"], "lookback_days": "30"},
134
+ )
135
+ ```
136
+
124
137
  ### Update Existing Multiple Tasks Configuration
125
138
 
126
139
  You can update multiple databricks tasks by initializing a zipher Client and sending a JSON representing a list of dbx SubmitTask objects to
@@ -8,7 +8,7 @@ with open('README.md', encoding='utf-8') as f:
8
8
 
9
9
  setup(
10
10
  name='zipher-sdk',
11
- version='0.4.4',
11
+ version='0.4.5',
12
12
  description='Python SDK for programmatic access to the Zipher API',
13
13
  long_description=long_description,
14
14
  long_description_content_type='text/markdown',
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.1
2
2
  Name: zipher-sdk
3
- Version: 0.4.4
3
+ Version: 0.4.5
4
4
  Summary: Python SDK for programmatic access to the Zipher API
5
5
  Home-page: UNKNOWN
6
6
  Author: Zipher Inc.
@@ -136,6 +136,19 @@ optimized_cluster = client.update_existing_conf(job_id="my-job-id", existing_con
136
136
 
137
137
  ```
138
138
 
139
+ #### Optional: passing per-run parameters
140
+
141
+ You can specify run-level parameters that Zipher will take into consideration. This is useful for parametrized jobs, where Zipher can explicitly learn the different usage patterns of different parametes.
142
+
143
+
144
+ ```python
145
+ optimized_cluster = client.update_existing_conf(
146
+ job_id="my-job-id",
147
+ existing_conf=config_payload,
148
+ run_params={"customer_ids": ["c1", "c2"], "lookback_days": "30"},
149
+ )
150
+ ```
151
+
139
152
  ### Update Existing Multiple Tasks Configuration
140
153
 
141
154
  You can update multiple databricks tasks by initializing a zipher Client and sending a JSON representing a list of dbx SubmitTask objects to
File without changes
File without changes
File without changes
File without changes
File without changes
File without changes
File without changes