cmsdials 2.2.0__tar.gz → 2.3.0__tar.gz

{cmsdials-2.2.0 → cmsdials-2.3.0}/.gitlab-ci.yml

@@ -81,8 +81,8 @@ test_matrix:
         coverage_format: cobertura
         path: coverage.xml
   variables:
-    SECRET_KEY: "$SECRET_KEY"
-    # Application owning SECRET_KEY, enables the api-access token tests
+    CLIENT_SECRET: "$CLIENT_SECRET"
+    # Application owning CLIENT_SECRET, enables the api-access token tests
     CLIENT_ID: "cms-dials-dev-api-client-test"
   rules:
     - if: '$CI_PIPELINE_SOURCE == "merge_request_event"'

{cmsdials-2.2.0 → cmsdials-2.3.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: cmsdials
-Version: 2.2.0
+Version: 2.3.0
 Summary: The Python api client interface to DIALS service
 Author-email: Gabriel Moreira <gabriel.moreira@cern.ch>
 Project-URL: Repository, https://gitlab.cern.ch/cms-dqmdc/libraries/dials-py
@@ -368,15 +368,15 @@ uv pip install -e .
 The repository has some tests written to make sure DIALS responses are compatible with pydantic metaclasses, you can use pytest to run all tests but you need to specify a secret key to authenticate non-interactively against DIALS api:
 
 ```bash
-SECRET_KEY=... uv run pytest tests
+CLIENT_SECRET=... uv run pytest tests
 ```
 
-The secret key is an api client enabled secret key and can be obtained from the applications portal, any api client secret key whitelisted in DIALS can be used. Set `CLIENT_ID` to the client id of the same application to test the api-access token flow (`SECRET_KEY=... CLIENT_ID=... uv run pytest tests`); otherwise those tests are skipped and the deprecated `X-CLIENT-SECRET` header is used. Tests target the dev Keycloak applications by default, overwrite them with `AUTH_CLIENT_ID` and `AUTH_AUDIENCE`. The interactive authentication flow should be tested manually, an example for this can be found in [test_auth_client.py](/tests/integration/test_auth_client.py).
+The secret key is an api client enabled secret key and can be obtained from the applications portal, any api client secret key whitelisted in DIALS can be used. Set `CLIENT_ID` to the client id of the same application to test the api-access token flow (`CLIENT_SECRET=... CLIENT_ID=... uv run pytest tests`); otherwise those tests are skipped and the deprecated `X-CLIENT-SECRET` header is used. Tests target the dev Keycloak applications by default, overwrite them with `AUTH_CLIENT_ID` and `AUTH_AUDIENCE`. The interactive authentication flow should be tested manually, an example for this can be found in [test_auth_client.py](/tests/integration/test_auth_client.py).
 
 If testing against a local version of DIALS you need to specify the BASE_URL:
 
 ```bash
-SECRET_KEY=... BASE_URL=http://localhost:8000 uv run pytest tests
+CLIENT_SECRET=... BASE_URL=http://localhost:8000 uv run pytest tests
 ```
 
 #### Tox
@@ -384,7 +384,7 @@ SECRET_KEY=... BASE_URL=http://localhost:8000 uv run pytest tests
 Tox is pre-configured in `tox.ini`, so you can run the following to test against multiple python versions locally:
 
 ```bash
-SECRET_KEY=... uv run tox
+CLIENT_SECRET=... uv run tox
 ```
 
 **[asdf](https://asdf-vm.com/) users**

{cmsdials-2.2.0 → cmsdials-2.3.0}/README.md

@@ -345,15 +345,15 @@ uv pip install -e .
 The repository has some tests written to make sure DIALS responses are compatible with pydantic metaclasses, you can use pytest to run all tests but you need to specify a secret key to authenticate non-interactively against DIALS api:
 
 ```bash
-SECRET_KEY=... uv run pytest tests
+CLIENT_SECRET=... uv run pytest tests
 ```
 
-The secret key is an api client enabled secret key and can be obtained from the applications portal, any api client secret key whitelisted in DIALS can be used. Set `CLIENT_ID` to the client id of the same application to test the api-access token flow (`SECRET_KEY=... CLIENT_ID=... uv run pytest tests`); otherwise those tests are skipped and the deprecated `X-CLIENT-SECRET` header is used. Tests target the dev Keycloak applications by default, overwrite them with `AUTH_CLIENT_ID` and `AUTH_AUDIENCE`. The interactive authentication flow should be tested manually, an example for this can be found in [test_auth_client.py](/tests/integration/test_auth_client.py).
+The secret key is an api client enabled secret key and can be obtained from the applications portal, any api client secret key whitelisted in DIALS can be used. Set `CLIENT_ID` to the client id of the same application to test the api-access token flow (`CLIENT_SECRET=... CLIENT_ID=... uv run pytest tests`); otherwise those tests are skipped and the deprecated `X-CLIENT-SECRET` header is used. Tests target the dev Keycloak applications by default, overwrite them with `AUTH_CLIENT_ID` and `AUTH_AUDIENCE`. The interactive authentication flow should be tested manually, an example for this can be found in [test_auth_client.py](/tests/integration/test_auth_client.py).
 
 If testing against a local version of DIALS you need to specify the BASE_URL:
 
 ```bash
-SECRET_KEY=... BASE_URL=http://localhost:8000 uv run pytest tests
+CLIENT_SECRET=... BASE_URL=http://localhost:8000 uv run pytest tests
 ```
 
 #### Tox
@@ -361,7 +361,7 @@ SECRET_KEY=... BASE_URL=http://localhost:8000 uv run pytest tests
 Tox is pre-configured in `tox.ini`, so you can run the following to test against multiple python versions locally:
 
 ```bash
-SECRET_KEY=... uv run tox
+CLIENT_SECRET=... uv run tox
 ```
 
 **[asdf](https://asdf-vm.com/) users**

{cmsdials-2.2.0 → cmsdials-2.3.0}/cmsdials/_version.py

@@ -18,7 +18,7 @@ version_tuple: tuple[int | str, ...]
 commit_id: str | None
 __commit_id__: str | None
 
-__version__ = version = '2.2.0'
-__version_tuple__ = version_tuple = (2, 2, 0)
+__version__ = version = '2.3.0'
+__version_tuple__ = version_tuple = (2, 3, 0)
 
-__commit_id__ = commit_id = 'g395406611'
+__commit_id__ = commit_id = 'g044d28ceb'

{cmsdials-2.2.0 → cmsdials-2.3.0}/cmsdials/clients/workspace/client.py

@@ -8,7 +8,7 @@ from ...utils.logger import logger
 
 class WorkspaceClient(BaseAPIClient):
     default_timeout = 30
-    lookup_url = "auth/"
+    lookup_url = "workspaces/"
 
     def __init__(
         self,
@@ -46,7 +46,7 @@ class WorkspaceClient(BaseAPIClient):
         return response.json()
 
     def list(self, retries=DEFAULT_RETRIES):
-        return self.__get("workspaces", retries=retries)
+        return self.__get("", retries=retries)
 
     def my_workspace(self, retries=DEFAULT_RETRIES):
-        return self.__get("user-default-workspace", retries=retries)
+        return self.__get("my-default/", retries=retries)

{cmsdials-2.2.0 → cmsdials-2.3.0}/cmsdials.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: cmsdials
-Version: 2.2.0
+Version: 2.3.0
 Summary: The Python api client interface to DIALS service
 Author-email: Gabriel Moreira <gabriel.moreira@cern.ch>
 Project-URL: Repository, https://gitlab.cern.ch/cms-dqmdc/libraries/dials-py
@@ -368,15 +368,15 @@ uv pip install -e .
 The repository has some tests written to make sure DIALS responses are compatible with pydantic metaclasses, you can use pytest to run all tests but you need to specify a secret key to authenticate non-interactively against DIALS api:
 
 ```bash
-SECRET_KEY=... uv run pytest tests
+CLIENT_SECRET=... uv run pytest tests
 ```
 
-The secret key is an api client enabled secret key and can be obtained from the applications portal, any api client secret key whitelisted in DIALS can be used. Set `CLIENT_ID` to the client id of the same application to test the api-access token flow (`SECRET_KEY=... CLIENT_ID=... uv run pytest tests`); otherwise those tests are skipped and the deprecated `X-CLIENT-SECRET` header is used. Tests target the dev Keycloak applications by default, overwrite them with `AUTH_CLIENT_ID` and `AUTH_AUDIENCE`. The interactive authentication flow should be tested manually, an example for this can be found in [test_auth_client.py](/tests/integration/test_auth_client.py).
+The secret key is an api client enabled secret key and can be obtained from the applications portal, any api client secret key whitelisted in DIALS can be used. Set `CLIENT_ID` to the client id of the same application to test the api-access token flow (`CLIENT_SECRET=... CLIENT_ID=... uv run pytest tests`); otherwise those tests are skipped and the deprecated `X-CLIENT-SECRET` header is used. Tests target the dev Keycloak applications by default, overwrite them with `AUTH_CLIENT_ID` and `AUTH_AUDIENCE`. The interactive authentication flow should be tested manually, an example for this can be found in [test_auth_client.py](/tests/integration/test_auth_client.py).
 
 If testing against a local version of DIALS you need to specify the BASE_URL:
 
 ```bash
-SECRET_KEY=... BASE_URL=http://localhost:8000 uv run pytest tests
+CLIENT_SECRET=... BASE_URL=http://localhost:8000 uv run pytest tests
 ```
 
 #### Tox
@@ -384,7 +384,7 @@ SECRET_KEY=... BASE_URL=http://localhost:8000 uv run pytest tests
 Tox is pre-configured in `tox.ini`, so you can run the following to test against multiple python versions locally:
 
 ```bash
-SECRET_KEY=... uv run tox
+CLIENT_SECRET=... uv run tox
 ```
 
 **[asdf](https://asdf-vm.com/) users**

cmsdials-2.3.0/cmsdials.egg-info/scm_version.json

@@ -0,0 +1,8 @@
+{
+  "tag": "2.3.0",
+  "distance": 0,
+  "node": "g044d28ceb686efd620bbbb7c6a4d87fbda5d076c",
+  "dirty": false,
+  "branch": "HEAD",
+  "node_date": "2026-10-21"
+}

{cmsdials-2.2.0 → cmsdials-2.3.0}/tests/integration/env.py

@@ -1,12 +1,12 @@
 import os
 
 
-SECRET_KEY = os.getenv("SECRET_KEY")
-if not SECRET_KEY:
-    raise OSError("SECRET_KEY environment variable is not set.")
+CLIENT_SECRET = os.getenv("CLIENT_SECRET")
+if not CLIENT_SECRET:
+    raise OSError("CLIENT_SECRET environment variable is not set.")
 
 BASE_URL = os.getenv("BASE_URL", "https://dev-cmsdials-api.web.cern.ch/")
-# Client id of the application owning SECRET_KEY. When set, tests authenticate
+# Client id of the application owning CLIENT_SECRET. When set, tests authenticate
 # with api-access tokens instead of the deprecated X-CLIENT-SECRET header.
 CLIENT_ID = os.getenv("CLIENT_ID") or None
 AUTH_CLIENT_ID = os.getenv("AUTH_CLIENT_ID", "cms-dials-dev-public-app")

{cmsdials-2.2.0 → cmsdials-2.3.0}/tests/integration/test_auth_client.py

@@ -9,7 +9,7 @@ from cmsdials.auth.bearer import Credentials as BearerCredentials
 from cmsdials.auth.models import Token
 from cmsdials.auth.secret_key import Credentials as SecretKeyCredentials
 
-from .env import BASE_URL, CLIENT_ID, SECRET_KEY, TEST_WORKSPACE
+from .env import BASE_URL, CLIENT_ID, CLIENT_SECRET, TEST_WORKSPACE
 from .utils import build_auth_client
 
 
@@ -23,14 +23,14 @@ def __setup_dials_from_creds_and_test(
 
 
 def test_secret_key_success() -> None:
-    creds = SecretKeyCredentials(token=SECRET_KEY)
+    creds = SecretKeyCredentials(token=CLIENT_SECRET)
     __setup_dials_from_creds_and_test(creds)
 
 
 @pytest.mark.skipif(CLIENT_ID is None, reason="CLIENT_ID is not set")
 def test_api_access_success() -> None:
     creds = SecretKeyCredentials(
-        token=SECRET_KEY, client_id=CLIENT_ID, client=build_auth_client()
+        token=CLIENT_SECRET, client_id=CLIENT_ID, client=build_auth_client()
     )
     headers: dict[str, str] = {}
     creds.before_request(headers)

{cmsdials-2.2.0 → cmsdials-2.3.0}/tests/integration/utils.py

@@ -7,7 +7,7 @@ from .env import (
     AUTH_CLIENT_ID,
     BASE_URL,
     CLIENT_ID,
-    SECRET_KEY,
+    CLIENT_SECRET,
     TEST_WORKSPACE,
 )
 
@@ -18,6 +18,6 @@ def build_auth_client() -> AuthClient:
 
 def setup_dials_object() -> Dials:
     creds = Credentials(
-        token=SECRET_KEY, client_id=CLIENT_ID, client=build_auth_client()
+        token=CLIENT_SECRET, client_id=CLIENT_ID, client=build_auth_client()
     )
     return Dials(creds, base_url=BASE_URL, workspace=TEST_WORKSPACE)

{cmsdials-2.2.0 → cmsdials-2.3.0}/tox.ini

@@ -5,5 +5,5 @@ env_list = py39, py310, py311, py312
 [testenv]
 description = Run test under {base_python}
 commands = pytest tests
-passenv = SECRET_KEY, CLIENT_ID, BASE_URL
+passenv = CLIENT_SECRET, CLIENT_ID, BASE_URL
 allowlist_externals = pytest

cmsdials-2.2.0/cmsdials.egg-info/scm_version.json

@@ -1,8 +0,0 @@
-{
-  "tag": "2.2.0",
-  "distance": 0,
-  "node": "g395406611acfaa2d58ea545fbd751958a8aa6e95",
-  "dirty": false,
-  "branch": "HEAD",
-  "node_date": "2026-09-29"
-}