cf-opcua-server
Current-phase Cogniflow OPC UA owner module.
The package still publishes under the existing cf-opcua-server name for compatibility, but it now covers both:
- virtual OPC UA server utilities for demos
- reusable one-shot OPC UA read APIs for owner-module consumers
- a native owner-contract provider consumed by
cf_pipeline_engineandcf_basic_io
Architecture note:
cf_datahiveis the reference owner for storage egresscf_opcua_serveris the current owner for OPC UA integration until a future dedicated rename/migration task possibly broadens the package tocf-opencua
Published distribution name:
pip install cf-opcua-server
Usage
cf-opcua-server start --interval 1.0
Read a snapshot from an OPC UA endpoint:
cf-opcua-server read --endpoint opc.tcp://127.0.0.1:4840/VirtualPhServer
Python API:
from cf_opcua_server import DEFAULT_NODE_MAP, read_nodes_once_json_sync, read_nodes_once_sync
payload = read_nodes_once_sync(
"opc.tcp://127.0.0.1:4840/VirtualPhServer",
DEFAULT_NODE_MAP,
timeout=2.0,
)
print(payload)
payload_json = read_nodes_once_json_sync(
"opc.tcp://127.0.0.1:4840/VirtualPhServer",
DEFAULT_NODE_MAP,
timeout=2.0,
)
print(payload_json)
The default read mapping uses the virtual demo nodes:
pHtemperaturetimestamp
Runner-owned consumers that need a single-line payload can use:
cf-opcua-server read --compact --endpoint opc.tcp://127.0.0.1:4840/VirtualPhServer
The package also publishes a native provider surface for CfOpcuaOwnerContractV1.
The engine links that provider and injects it into CfExecutionContext.opcua_owner
for plugin-executed cfio:OpcuaReaderStep.
Publishing
cf_opcua_server is published with the dedicated Windows workflow:
- Workflow:
.github/workflows/cf_opcua_server_windows_publish.yml - Package directory:
sandcastle/cf_opcua_server - PyPI tag:
cf-opcua-server-v<version> - TestPyPI tag:
cf-opcua-server-v<version>-test
Local preflight:
powershell -ExecutionPolicy Bypass -File scripts/mimic_windows_python_publish_workflow.ps1 `
-WorkflowFile .github/workflows/cf_opcua_server_windows_publish.yml `
-PackageDir sandcastle/cf_opcua_server `
-PythonExe py `
-PythonVersion 3.14
Queue a dry-run dispatch:
powershell -ExecutionPolicy Bypass -File scripts/queue_windows_python_publish_workflow.ps1 `
-WorkflowFile .github/workflows/cf_opcua_server_windows_publish.yml `
-PackageDir sandcastle/cf_opcua_server `
-PublishTarget testpypi `
-Ref main `
-RequireLocalPass `
-DryRun
Metadata
Release files for cf-opcua-server 0.2.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| cf_opcua_server-0.2.4.tar.gz | 10.4 kB | Without provenance | Details for cf_opcua_server-0.2.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cf_opcua_server-0.2.4-cp314-cp314-win_amd64.whl | CPython 3.14 | CPython 3.14 | Windows x86-64 | Details for cf_opcua_server-0.2.4-cp314-cp314-win_amd64.whl |
Total release size: 43.3 kB
Release files / cf_opcua_server-0.2.4.tar.gz
| Download URL | cf_opcua_server-0.2.4.tar.gz |
|---|---|
| Size | 10.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
496eabd4e7fbe1bcd9e4c02e0e59c8342c21617bae2d9f3cf1c231974664997f
|
|
BLAKE2b-256 checksum How to use checksums |
2e3de89c67b531e21f36b8bd59caae9892caf02e21767682ed211c19f10a2632
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.2.0 CPython/3.14.4
|
Release files / cf_opcua_server-0.2.4-cp314-cp314-win_amd64.whl
| Download URL | cf_opcua_server-0.2.4-cp314-cp314-win_amd64.whl |
|---|---|
| Size | 32.9 kB |
| Tags | CPython 3.14 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
ef4df1a377fadd1997523cdfd5f0f3435f0dc156e2a2a44a38cac28eb5c0d946
|
|
BLAKE2b-256 checksum How to use checksums |
a455a1f9d6a2798200ec60c4dca2c99df570c6d8b4f754419e6a4e3f382b75b8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.2.0 CPython/3.14.4
|
Security for cf-opcua-server 0.2.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.