git: 26763a8e3d8e - main - devel/py-azure-core-tracing-opentelemetry: Add py-azure-core-tracing-opentelemetry 1.0.0b12

The branch main has been updated by sunpoet:

URL: https://cgit.FreeBSD.org/ports/commit/?id=26763a8e3d8efc248878886196c6ab2f7fe7b44a

commit 26763a8e3d8efc248878886196c6ab2f7fe7b44a
Author:     Po-Chuan Hsieh <sunpoet@FreeBSD.org>
AuthorDate: 2025-06-30 20:48:36 +0000
Commit:     Po-Chuan Hsieh <sunpoet@FreeBSD.org>
CommitDate: 2025-06-30 20:51:58 +0000

    devel/py-azure-core-tracing-opentelemetry: Add py-azure-core-tracing-opentelemetry 1.0.0b12
    
    You can enable distributed tracing in Azure client libraries by configuring the
    OpenTelemetry SDK. OpenTelemetry is a popular open-source observability
    framework for generating, capturing, and collecting telemetry data for
    cloud-native software.
    
    There are two key concepts related to tracing: span and trace. A span represents
    a single operation in a trace. A span can represent an HTTP request, a remote
    procedure call (RPC), a database query, or even the path that your code takes. A
    trace is a tree of spans showing the path of work through a system. You can
    distinguish a trace on its own by a unique 16-byte sequence called a TraceID.
---
 devel/Makefile                                     |  1 +
 devel/py-azure-core-tracing-opentelemetry/Makefile | 26 ++++++++++++++++++++++
 devel/py-azure-core-tracing-opentelemetry/distinfo |  3 +++
 .../py-azure-core-tracing-opentelemetry/pkg-descr  | 10 +++++++++
 4 files changed, 40 insertions(+)

diff --git a/devel/Makefile b/devel/Makefile
index cd31072c23d9..5c9a4c431ddd 100644
--- a/devel/Makefile
+++ b/devel/Makefile
@@ -4451,6 +4451,7 @@
     SUBDIR += py-azure-appconfiguration
     SUBDIR += py-azure-batch
     SUBDIR += py-azure-core
+    SUBDIR += py-azure-core-tracing-opentelemetry
     SUBDIR += py-azure-cosmos
     SUBDIR += py-azure-data-tables
     SUBDIR += py-azure-datalake-store
diff --git a/devel/py-azure-core-tracing-opentelemetry/Makefile b/devel/py-azure-core-tracing-opentelemetry/Makefile
new file mode 100644
index 000000000000..55fb88fd584b
--- /dev/null
+++ b/devel/py-azure-core-tracing-opentelemetry/Makefile
@@ -0,0 +1,26 @@
+PORTNAME=	azure-core-tracing-opentelemetry
+PORTVERSION=	1.0.0b12
+CATEGORIES=	devel python
+MASTER_SITES=	PYPI
+PKGNAMEPREFIX=	${PYTHON_PKGNAMEPREFIX}
+DISTNAME=	azure_core_tracing_opentelemetry-${PORTVERSION}
+
+MAINTAINER=	sunpoet@FreeBSD.org
+COMMENT=	Microsoft Azure Azure Core OpenTelemetry plugin Library for Python
+WWW=		https://github.com/Azure/azure-sdk-for-python/tree/main/sdk/core/azure-core-tracing-opentelemetry \
+		https://github.com/Azure/azure-sdk-for-python
+
+LICENSE=	MIT
+LICENSE_FILE=	${WRKSRC}/LICENSE
+
+BUILD_DEPENDS=	${PYTHON_PKGNAMEPREFIX}setuptools>=0:devel/py-setuptools@${PY_FLAVOR} \
+		${PYTHON_PKGNAMEPREFIX}wheel>=0:devel/py-wheel@${PY_FLAVOR}
+RUN_DEPENDS=	${PYTHON_PKGNAMEPREFIX}azure-core>=1.24.0:devel/py-azure-core@${PY_FLAVOR} \
+		${PYTHON_PKGNAMEPREFIX}opentelemetry-api>=1.12.0:devel/py-opentelemetry-api@${PY_FLAVOR}
+
+USES=		python
+USE_PYTHON=	autoplist concurrent pep517
+
+NO_ARCH=	yes
+
+.include <bsd.port.mk>
diff --git a/devel/py-azure-core-tracing-opentelemetry/distinfo b/devel/py-azure-core-tracing-opentelemetry/distinfo
new file mode 100644
index 000000000000..25e9836168df
--- /dev/null
+++ b/devel/py-azure-core-tracing-opentelemetry/distinfo
@@ -0,0 +1,3 @@
+TIMESTAMP = 1751208116
+SHA256 (azure_core_tracing_opentelemetry-1.0.0b12.tar.gz) = bb454142440bae11fd9d68c7c1d67ae38a1756ce808c5e4d736730a7b4b04144
+SIZE (azure_core_tracing_opentelemetry-1.0.0b12.tar.gz) = 26010
diff --git a/devel/py-azure-core-tracing-opentelemetry/pkg-descr b/devel/py-azure-core-tracing-opentelemetry/pkg-descr
new file mode 100644
index 000000000000..ff68fe0d5c74
--- /dev/null
+++ b/devel/py-azure-core-tracing-opentelemetry/pkg-descr
@@ -0,0 +1,10 @@
+You can enable distributed tracing in Azure client libraries by configuring the
+OpenTelemetry SDK. OpenTelemetry is a popular open-source observability
+framework for generating, capturing, and collecting telemetry data for
+cloud-native software.
+
+There are two key concepts related to tracing: span and trace. A span represents
+a single operation in a trace. A span can represent an HTTP request, a remote
+procedure call (RPC), a database query, or even the path that your code takes. A
+trace is a tree of spans showing the path of work through a system. You can
+distinguish a trace on its own by a unique 16-byte sequence called a TraceID.