cmsdials 2.4.1__tar.gz → 3.0.0__tar.gz

{cmsdials-2.4.1 → cmsdials-3.0.0}/.gitlab-ci.yml

@@ -82,7 +82,7 @@ test_matrix:
         path: coverage.xml
   variables:
     CLIENT_SECRET: "$CLIENT_SECRET"
-    # Application owning CLIENT_SECRET, enables the api-access token tests
+    # Application owning CLIENT_SECRET, required by the integration tests
     CLIENT_ID: "cms-dials-dev-api-client-test"
   rules:
     - if: '$CI_PIPELINE_SOURCE == "merge_request_event"'

cmsdials-3.0.0/PKG-INFO

@@ -0,0 +1,159 @@
+Metadata-Version: 2.4
+Name: cmsdials
+Version: 3.0.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
+Classifier: Development Status :: 5 - Production/Stable
+Classifier: Programming Language :: Python :: 3.9
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Requires-Python: >=3.9
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: requests<3.0.0,>=2.31.0
+Requires-Dist: urllib3<2.0.0,>=1.26.16
+Requires-Dist: pydantic<3.0.0,>=2.8.2
+Provides-Extra: pandas
+Requires-Dist: pandas>=1.5.3; extra == "pandas"
+Provides-Extra: tqdm
+Requires-Dist: tqdm>=4.66.1; extra == "tqdm"
+Dynamic: license-file
+
+![Build Status](https://gitlab.cern.ch/cms-ppd/technical-support/libraries/dials-py/badges/develop/pipeline.svg)
+![Coverage](https://gitlab.cern.ch/cms-ppd/technical-support/libraries/dials-py/badges/develop/coverage.svg)
+![Latest Release](https://gitlab.cern.ch/cms-ppd/technical-support/libraries/dials-py/-/badges/release.svg)
+[![PyPI version](https://badge.fury.io/py/cmsdials.png)](https://badge.fury.io/py/cmsdials)
+
+# dials-py
+
+The Python client of the [DIALS](https://cms-ppd.docs.cern.ch/ts/software/DIALS/index.html) API.
+
+The full documentation, with every endpoint, filters, pandas and progress bar support, retrying and resuming long queries, ML certification JSONs and the development instance, is in the [dials-py user guide](https://cms-ppd.docs.cern.ch/ts/software/DIALS/user_guide/dials_py.html).
+
+## Installation
+
+```bash
+pip install cmsdials
+```
+
+The `pandas` and `tqdm` extras enable conversion to DataFrames and progress bars:
+
+```bash
+pip install "cmsdials[pandas,tqdm]"
+```
+
+## Usage
+
+Tokens are issued by CERN's Keycloak directly, dials-py never sends your password or a client secret to DIALS.
+
+To log in as yourself, with the device flow (interactive, the credentials are cached in `.cache/` and renewed automatically):
+
+```python
+from cmsdials.auth.device import Credentials
+
+creds = Credentials.from_creds_file()
+```
+
+To log in as an application, with its client id and secret (unattended scripts, the application must be granted [API access](https://cms-ppd.docs.cern.ch/ts/software/DIALS/user_guide/api_access.html)):
+
+```python
+import os
+
+from cmsdials.auth.client_credentials import Credentials
+
+creds = Credentials(client_id="my-application", client_secret=os.environ["CLIENT_SECRET"])
+```
+
+Then query DIALS, optionally in another workspace than the one picked from your e-groups:
+
+```python
+from cmsdials import Dials
+from cmsdials.filters import LumisectionHistogram1DFilters
+
+dials = Dials(creds, workspace="tracker")
+
+data = dials.h1d.list_all(
+    LumisectionHistogram1DFilters(me="PixelPhase1/Tracks/PXBarrel/charge_PXLayer_2"),
+    max_pages=5,
+)
+```
+
+## Development
+
+Install the dependencies and the package using `uv`:
+
+```shell
+uv sync --all-groups --extra pandas --extra tqdm
+uv run pre-commit install
+uv pip install -e .
+```
+
+### Running tests
+
+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 the client id and secret of an application to authenticate non-interactively against DIALS api:
+
+```bash
+CLIENT_SECRET=... CLIENT_ID=... uv run pytest tests
+```
+
+Any application granted API access in DIALS can be used: `CLIENT_ID` is its client id and `CLIENT_SECRET` its client secret, both obtained from the applications portal. 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
+CLIENT_SECRET=... CLIENT_ID=... BASE_URL=http://localhost:8000 uv run pytest tests
+```
+
+#### Tox
+
+Tox is pre-configured in `tox.ini`, so you can run the following to test against multiple python versions locally:
+
+```bash
+CLIENT_SECRET=... CLIENT_ID=... uv run tox
+```
+
+**[asdf](https://asdf-vm.com/) users**
+
+tox requires multiple versions of Python to be installed. Using `asdf`, you have multiple versions installed, but they aren’t normally exposed to the current shell. You can use the following command to expose multiple versions of Python in the current directory:
+
+```bash
+asdf set python 3.12.9 3.11.10 3.10.13 3.9.19
+```
+
+This will use `3.12.9` by default (if you just run `python`), but it will also put `python3.11`, `python3.10` and `python3.9` symlinks in your path so you can run those too (which is exactly what tox is looking for).
+
+### Releasing the package on PyPI
+
+The package is available in PyPI at [cmsdials](https://pypi.org/project/cmsdials/), under the [cmsdqm](https://pypi.org/org/cms-dqm/) organization. You'll need at leat Mantainer rights to be able to push new versions.
+
+#### CI
+
+Do not worry. The GitLab CI is configured to automatically publish the package on PyPI and the release notes in GitLab whever a tag is pushed to the repo.
+
+> [!NOTE]
+> For this to work the CI/CD variables named `UV_PUBLISH_TOKEN`, `GITLAB_TOKEN` should be registered in gitlab. The `UV_PUBLISH_TOKEN` is a api token access of CMSDQM organization and the `GITLAB_TOKEN` is a Project Access Token with api read/write rights, which is needed to read merge requests using the `glab-cli`.
+> https://gitlab.cern.ch/cms-dqmdc/libraries/dials-py/-/settings/access_tokens
+
+#### Manual
+
+If you want to follow the manual approach, you need to first build and then publish.
+
+##### Build
+
+You can use uv to build the package using:
+
+```bash
+uv build
+```
+
+The build system will automatically update the package version based on the git tag of the current commit.
+
+##### Publish
+
+Provided you have already generate a PyPI api token in your account or in CMDQM org, you can publish using:
+
+```bash
+UV_PUBLISH_TOKEN=... uv publish
+```

cmsdials-3.0.0/README.md

@@ -0,0 +1,136 @@
+![Build Status](https://gitlab.cern.ch/cms-ppd/technical-support/libraries/dials-py/badges/develop/pipeline.svg)
+![Coverage](https://gitlab.cern.ch/cms-ppd/technical-support/libraries/dials-py/badges/develop/coverage.svg)
+![Latest Release](https://gitlab.cern.ch/cms-ppd/technical-support/libraries/dials-py/-/badges/release.svg)
+[![PyPI version](https://badge.fury.io/py/cmsdials.png)](https://badge.fury.io/py/cmsdials)
+
+# dials-py
+
+The Python client of the [DIALS](https://cms-ppd.docs.cern.ch/ts/software/DIALS/index.html) API.
+
+The full documentation, with every endpoint, filters, pandas and progress bar support, retrying and resuming long queries, ML certification JSONs and the development instance, is in the [dials-py user guide](https://cms-ppd.docs.cern.ch/ts/software/DIALS/user_guide/dials_py.html).
+
+## Installation
+
+```bash
+pip install cmsdials
+```
+
+The `pandas` and `tqdm` extras enable conversion to DataFrames and progress bars:
+
+```bash
+pip install "cmsdials[pandas,tqdm]"
+```
+
+## Usage
+
+Tokens are issued by CERN's Keycloak directly, dials-py never sends your password or a client secret to DIALS.
+
+To log in as yourself, with the device flow (interactive, the credentials are cached in `.cache/` and renewed automatically):
+
+```python
+from cmsdials.auth.device import Credentials
+
+creds = Credentials.from_creds_file()
+```
+
+To log in as an application, with its client id and secret (unattended scripts, the application must be granted [API access](https://cms-ppd.docs.cern.ch/ts/software/DIALS/user_guide/api_access.html)):
+
+```python
+import os
+
+from cmsdials.auth.client_credentials import Credentials
+
+creds = Credentials(client_id="my-application", client_secret=os.environ["CLIENT_SECRET"])
+```
+
+Then query DIALS, optionally in another workspace than the one picked from your e-groups:
+
+```python
+from cmsdials import Dials
+from cmsdials.filters import LumisectionHistogram1DFilters
+
+dials = Dials(creds, workspace="tracker")
+
+data = dials.h1d.list_all(
+    LumisectionHistogram1DFilters(me="PixelPhase1/Tracks/PXBarrel/charge_PXLayer_2"),
+    max_pages=5,
+)
+```
+
+## Development
+
+Install the dependencies and the package using `uv`:
+
+```shell
+uv sync --all-groups --extra pandas --extra tqdm
+uv run pre-commit install
+uv pip install -e .
+```
+
+### Running tests
+
+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 the client id and secret of an application to authenticate non-interactively against DIALS api:
+
+```bash
+CLIENT_SECRET=... CLIENT_ID=... uv run pytest tests
+```
+
+Any application granted API access in DIALS can be used: `CLIENT_ID` is its client id and `CLIENT_SECRET` its client secret, both obtained from the applications portal. 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
+CLIENT_SECRET=... CLIENT_ID=... BASE_URL=http://localhost:8000 uv run pytest tests
+```
+
+#### Tox
+
+Tox is pre-configured in `tox.ini`, so you can run the following to test against multiple python versions locally:
+
+```bash
+CLIENT_SECRET=... CLIENT_ID=... uv run tox
+```
+
+**[asdf](https://asdf-vm.com/) users**
+
+tox requires multiple versions of Python to be installed. Using `asdf`, you have multiple versions installed, but they aren’t normally exposed to the current shell. You can use the following command to expose multiple versions of Python in the current directory:
+
+```bash
+asdf set python 3.12.9 3.11.10 3.10.13 3.9.19
+```
+
+This will use `3.12.9` by default (if you just run `python`), but it will also put `python3.11`, `python3.10` and `python3.9` symlinks in your path so you can run those too (which is exactly what tox is looking for).
+
+### Releasing the package on PyPI
+
+The package is available in PyPI at [cmsdials](https://pypi.org/project/cmsdials/), under the [cmsdqm](https://pypi.org/org/cms-dqm/) organization. You'll need at leat Mantainer rights to be able to push new versions.
+
+#### CI
+
+Do not worry. The GitLab CI is configured to automatically publish the package on PyPI and the release notes in GitLab whever a tag is pushed to the repo.
+
+> [!NOTE]
+> For this to work the CI/CD variables named `UV_PUBLISH_TOKEN`, `GITLAB_TOKEN` should be registered in gitlab. The `UV_PUBLISH_TOKEN` is a api token access of CMSDQM organization and the `GITLAB_TOKEN` is a Project Access Token with api read/write rights, which is needed to read merge requests using the `glab-cli`.
+> https://gitlab.cern.ch/cms-dqmdc/libraries/dials-py/-/settings/access_tokens
+
+#### Manual
+
+If you want to follow the manual approach, you need to first build and then publish.
+
+##### Build
+
+You can use uv to build the package using:
+
+```bash
+uv build
+```
+
+The build system will automatically update the package version based on the git tag of the current commit.
+
+##### Publish
+
+Provided you have already generate a PyPI api token in your account or in CMDQM org, you can publish using:
+
+```bash
+UV_PUBLISH_TOKEN=... uv publish
+```

{cmsdials-2.4.1 → cmsdials-3.0.0}/cmsdials/_version.py

@@ -18,7 +18,7 @@ version_tuple: tuple[int | str, ...]
 commit_id: str | None
 __commit_id__: str | None
 
-__version__ = version = '2.4.1'
-__version_tuple__ = version_tuple = (2, 4, 1)
+__version__ = version = '3.0.0'
+__version_tuple__ = version_tuple = (3, 0, 0)
 
-__commit_id__ = commit_id = 'g7433d876a'
+__commit_id__ = commit_id = 'g3b39a8c48'

{cmsdials-2.4.1 → cmsdials-3.0.0}/cmsdials/auth/client.py

@@ -1,5 +1,4 @@
 import time
-import warnings
 from datetime import datetime, timedelta
 from typing import Optional
 
@@ -48,24 +47,17 @@ class AuthClient(BaseAPIClient):
         audience: Optional[str] = None,
         **kwargs,
     ) -> None:
-        # Leftovers from releases that logged in through DIALS: tokens are now
+        # Leftovers from releases that logged in through DIALS: tokens are
         # issued by Keycloak, and the instance is selected by client_id and
         # audience, so these would silently target production.
-        ignored = [
-            name
-            for name in ("base_url", "route", "version")
-            if kwargs.get(name) is not None
-        ]
-        if args or ignored:
-            warnings.warn(
-                "AuthClient ignores base_url, route and version, which will "
-                "raise TypeError in dials-py 3.0.0. Tokens are issued by CERN "
-                "Keycloak: to target another DIALS instance, pass its "
-                "client_id and audience instead.",
-                DeprecationWarning,
-                stacklevel=2,
+        if args or kwargs:
+            raise TypeError(
+                "AuthClient does not accept base_url, route, version or other "
+                "API client arguments. Tokens are issued by CERN Keycloak: to "
+                "target another DIALS instance, pass its client_id and "
+                "audience instead."
             )
-        super().__init__(*args, **kwargs)
+        super().__init__()
         keycloak_url = keycloak_url or self.PRODUCTION_KEYCLOAK_URL
         if not keycloak_url.endswith("/"):
             keycloak_url += "/"

{cmsdials-2.4.1 → cmsdials-3.0.0}/cmsdials/cmsdials.py

@@ -9,7 +9,6 @@ from .clients.lumisection.client import LumisectionClient
 from .clients.mes.client import MonitoringElementClient
 from .clients.ml_bad_lumisection.client import MLBadLumisectionClient
 from .clients.ml_models_index.client import MLModelsIndexClient
-from .clients.oms_proxy.client import OMSProxyClient
 from .clients.run.client import RunClient
 from .clients.workspace.client import WorkspaceClient
 
@@ -35,7 +34,6 @@ class Dials:
         self.lumi = LumisectionClient(creds, workspace, *args, **kwargs)
         self.run = RunClient(creds, workspace, *args, **kwargs)
         self.mes = MonitoringElementClient(creds, workspace, *args, **kwargs)
-        self.oms = OMSProxyClient(creds, *args, **kwargs)
         self.ml_bad_lumis = MLBadLumisectionClient(
             creds, workspace, *args, **kwargs
         )

{cmsdials-2.4.1 → cmsdials-3.0.0}/cmsdials/filters.py

@@ -6,7 +6,6 @@ from .clients.lumisection.models import LumisectionFilters
 from .clients.mes.models import MEFilters
 from .clients.ml_bad_lumisection.models import MLBadLumisectionFilters
 from .clients.ml_models_index.models import MLModelsIndexFilters
-from .clients.oms_proxy.models import OMSFilter, OMSPage
 from .clients.run.models import RunFilters
 
 
@@ -19,7 +18,5 @@ __all__ = [
     "MEFilters",
     "MLBadLumisectionFilters",
     "MLModelsIndexFilters",
-    "OMSFilter",
-    "OMSPage",
     "RunFilters",
 ]

cmsdials-3.0.0/cmsdials.egg-info/PKG-INFO

@@ -0,0 +1,159 @@
+Metadata-Version: 2.4
+Name: cmsdials
+Version: 3.0.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
+Classifier: Development Status :: 5 - Production/Stable
+Classifier: Programming Language :: Python :: 3.9
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Requires-Python: >=3.9
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: requests<3.0.0,>=2.31.0
+Requires-Dist: urllib3<2.0.0,>=1.26.16
+Requires-Dist: pydantic<3.0.0,>=2.8.2
+Provides-Extra: pandas
+Requires-Dist: pandas>=1.5.3; extra == "pandas"
+Provides-Extra: tqdm
+Requires-Dist: tqdm>=4.66.1; extra == "tqdm"
+Dynamic: license-file
+
+![Build Status](https://gitlab.cern.ch/cms-ppd/technical-support/libraries/dials-py/badges/develop/pipeline.svg)
+![Coverage](https://gitlab.cern.ch/cms-ppd/technical-support/libraries/dials-py/badges/develop/coverage.svg)
+![Latest Release](https://gitlab.cern.ch/cms-ppd/technical-support/libraries/dials-py/-/badges/release.svg)
+[![PyPI version](https://badge.fury.io/py/cmsdials.png)](https://badge.fury.io/py/cmsdials)
+
+# dials-py
+
+The Python client of the [DIALS](https://cms-ppd.docs.cern.ch/ts/software/DIALS/index.html) API.
+
+The full documentation, with every endpoint, filters, pandas and progress bar support, retrying and resuming long queries, ML certification JSONs and the development instance, is in the [dials-py user guide](https://cms-ppd.docs.cern.ch/ts/software/DIALS/user_guide/dials_py.html).
+
+## Installation
+
+```bash
+pip install cmsdials
+```
+
+The `pandas` and `tqdm` extras enable conversion to DataFrames and progress bars:
+
+```bash
+pip install "cmsdials[pandas,tqdm]"
+```
+
+## Usage
+
+Tokens are issued by CERN's Keycloak directly, dials-py never sends your password or a client secret to DIALS.
+
+To log in as yourself, with the device flow (interactive, the credentials are cached in `.cache/` and renewed automatically):
+
+```python
+from cmsdials.auth.device import Credentials
+
+creds = Credentials.from_creds_file()
+```
+
+To log in as an application, with its client id and secret (unattended scripts, the application must be granted [API access](https://cms-ppd.docs.cern.ch/ts/software/DIALS/user_guide/api_access.html)):
+
+```python
+import os
+
+from cmsdials.auth.client_credentials import Credentials
+
+creds = Credentials(client_id="my-application", client_secret=os.environ["CLIENT_SECRET"])
+```
+
+Then query DIALS, optionally in another workspace than the one picked from your e-groups:
+
+```python
+from cmsdials import Dials
+from cmsdials.filters import LumisectionHistogram1DFilters
+
+dials = Dials(creds, workspace="tracker")
+
+data = dials.h1d.list_all(
+    LumisectionHistogram1DFilters(me="PixelPhase1/Tracks/PXBarrel/charge_PXLayer_2"),
+    max_pages=5,
+)
+```
+
+## Development
+
+Install the dependencies and the package using `uv`:
+
+```shell
+uv sync --all-groups --extra pandas --extra tqdm
+uv run pre-commit install
+uv pip install -e .
+```
+
+### Running tests
+
+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 the client id and secret of an application to authenticate non-interactively against DIALS api:
+
+```bash
+CLIENT_SECRET=... CLIENT_ID=... uv run pytest tests
+```
+
+Any application granted API access in DIALS can be used: `CLIENT_ID` is its client id and `CLIENT_SECRET` its client secret, both obtained from the applications portal. 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
+CLIENT_SECRET=... CLIENT_ID=... BASE_URL=http://localhost:8000 uv run pytest tests
+```
+
+#### Tox
+
+Tox is pre-configured in `tox.ini`, so you can run the following to test against multiple python versions locally:
+
+```bash
+CLIENT_SECRET=... CLIENT_ID=... uv run tox
+```
+
+**[asdf](https://asdf-vm.com/) users**
+
+tox requires multiple versions of Python to be installed. Using `asdf`, you have multiple versions installed, but they aren’t normally exposed to the current shell. You can use the following command to expose multiple versions of Python in the current directory:
+
+```bash
+asdf set python 3.12.9 3.11.10 3.10.13 3.9.19
+```
+
+This will use `3.12.9` by default (if you just run `python`), but it will also put `python3.11`, `python3.10` and `python3.9` symlinks in your path so you can run those too (which is exactly what tox is looking for).
+
+### Releasing the package on PyPI
+
+The package is available in PyPI at [cmsdials](https://pypi.org/project/cmsdials/), under the [cmsdqm](https://pypi.org/org/cms-dqm/) organization. You'll need at leat Mantainer rights to be able to push new versions.
+
+#### CI
+
+Do not worry. The GitLab CI is configured to automatically publish the package on PyPI and the release notes in GitLab whever a tag is pushed to the repo.
+
+> [!NOTE]
+> For this to work the CI/CD variables named `UV_PUBLISH_TOKEN`, `GITLAB_TOKEN` should be registered in gitlab. The `UV_PUBLISH_TOKEN` is a api token access of CMSDQM organization and the `GITLAB_TOKEN` is a Project Access Token with api read/write rights, which is needed to read merge requests using the `glab-cli`.
+> https://gitlab.cern.ch/cms-dqmdc/libraries/dials-py/-/settings/access_tokens
+
+#### Manual
+
+If you want to follow the manual approach, you need to first build and then publish.
+
+##### Build
+
+You can use uv to build the package using:
+
+```bash
+uv build
+```
+
+The build system will automatically update the package version based on the git tag of the current commit.
+
+##### Publish
+
+Provided you have already generate a PyPI api token in your account or in CMDQM org, you can publish using:
+
+```bash
+UV_PUBLISH_TOKEN=... uv publish
+```

{cmsdials-2.4.1 → cmsdials-3.0.0}/cmsdials.egg-info/SOURCES.txt

@@ -26,13 +26,11 @@ cmsdials.egg-info/scm_version.json
 cmsdials.egg-info/top_level.txt
 cmsdials/auth/__init__.py
 cmsdials/auth/_base.py
-cmsdials/auth/bearer.py
 cmsdials/auth/client.py
 cmsdials/auth/client_credentials.py
 cmsdials/auth/device.py
 cmsdials/auth/exceptions.py
 cmsdials/auth/models.py
-cmsdials/auth/secret_key.py
 cmsdials/clients/__init__.py
 cmsdials/clients/dataset_index/__init__.py
 cmsdials/clients/dataset_index/client.py
@@ -58,9 +56,6 @@ cmsdials/clients/ml_bad_lumisection/models.py
 cmsdials/clients/ml_models_index/__init__.py
 cmsdials/clients/ml_models_index/client.py
 cmsdials/clients/ml_models_index/models.py
-cmsdials/clients/oms_proxy/__init__.py
-cmsdials/clients/oms_proxy/client.py
-cmsdials/clients/oms_proxy/models.py
 cmsdials/clients/run/__init__.py
 cmsdials/clients/run/client.py
 cmsdials/clients/run/models.py
@@ -79,7 +74,6 @@ tests/integration/test_h1d_client.py
 tests/integration/test_h2d_client.py
 tests/integration/test_lumisection_client.py
 tests/integration/test_mes_client.py
-tests/integration/test_oms_proxy_client.py
 tests/integration/test_resume.py
 tests/integration/test_run_client.py
 tests/integration/utils.py

{cmsdials-2.4.1 → cmsdials-3.0.0}/cmsdials.egg-info/scm_file_list.json

@@ -12,13 +12,11 @@
     "cmsdials/__init__.py",
     "cmsdials/auth/__init__.py",
     "cmsdials/auth/_base.py",
-    "cmsdials/auth/bearer.py",
     "cmsdials/auth/client.py",
     "cmsdials/auth/client_credentials.py",
     "cmsdials/auth/device.py",
     "cmsdials/auth/exceptions.py",
     "cmsdials/auth/models.py",
-    "cmsdials/auth/secret_key.py",
     "cmsdials/clients/__init__.py",
     "cmsdials/clients/dataset_index/__init__.py",
     "cmsdials/clients/dataset_index/client.py",
@@ -44,9 +42,6 @@
     "cmsdials/clients/ml_models_index/__init__.py",
     "cmsdials/clients/ml_models_index/client.py",
     "cmsdials/clients/ml_models_index/models.py",
-    "cmsdials/clients/oms_proxy/__init__.py",
-    "cmsdials/clients/oms_proxy/client.py",
-    "cmsdials/clients/oms_proxy/models.py",
     "cmsdials/clients/run/__init__.py",
     "cmsdials/clients/run/client.py",
     "cmsdials/clients/run/models.py",
@@ -71,7 +66,6 @@
     "tests/integration/test_h2d_client.py",
     "tests/integration/test_lumisection_client.py",
     "tests/integration/test_mes_client.py",
-    "tests/integration/test_oms_proxy_client.py",
     "tests/integration/test_resume.py",
     "tests/integration/test_run_client.py",
     "tests/integration/utils.py",

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

@@ -0,0 +1,8 @@
+{
+  "tag": "3.0.0",
+  "distance": 0,
+  "node": "g3b39a8c4892ceefba0c836cd524029d5116b005b",
+  "dirty": false,
+  "branch": "HEAD",
+  "node_date": "2026-11-12"
+}

{cmsdials-2.4.1 → cmsdials-3.0.0}/tests/integration/env.py

@@ -1,15 +1,18 @@
 import os
 
 
-_client_secret = os.getenv("CLIENT_SECRET")
-if not _client_secret:
-    raise OSError("CLIENT_SECRET environment variable is not set.")
-CLIENT_SECRET: str = _client_secret
+def _required(name: str) -> str:
+    value = os.getenv(name)
+    if not value:
+        raise OSError(f"{name} environment variable is not set.")
+    return value
+
+
+CLIENT_SECRET = _required("CLIENT_SECRET")
 
 BASE_URL = os.getenv("BASE_URL", "https://dev-cmsdials-api.web.cern.ch/")
-# 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
+# Client id of the application owning CLIENT_SECRET
+CLIENT_ID = _required("CLIENT_ID")
 AUTH_CLIENT_ID = os.getenv("AUTH_CLIENT_ID", "cms-dials-dev-public-app")
 AUTH_AUDIENCE = os.getenv("AUTH_AUDIENCE", "cms-dials-dev-confidential-app")
 TEST_WORKSPACE = os.getenv("TEST_WORKSPACE", "global")
@@ -21,6 +24,3 @@ TEST_FILE_ID = int(
 )  # /store/data/Run2026A/ZeroBias/DQMIO/PromptReco-v1/000/401/605/00000/2D15036C-0CB4-4B76-AA85-D1DB7DC6981F.root
 TEST_RUN_NUMBER = int(os.getenv("TEST_RUN_NUMBER", 401605))
 TEST_LS_NUMBER = int(os.getenv("TEST_LS_NUMBER", 1))
-TEST_TRUTH_OMS_DATASETRATES_LENGTH = int(
-    os.getenv("TEST_TRUTH_OMS_DATASETRATES_LENGTH", 242)
-)