Read OFT params from env file

Adopted the way that up-spec reads in the OpenFastTrace configuration
params from an env file in the local workspace. This makes it easier
to adapt the file patterns and tags according to the evolvement of
up-spec. The former way of using GitHub repo variables for that
purpose was rather static and did not allow to use different sets of
patterns on different branches in the repo.

Author: sophokles73

.env.oft-latest

@@ -0,0 +1,23 @@
+# Copyright (c) 2025 Contributors to the Eclipse Foundation
+#
+# See the NOTICE file(s) distributed with this work for additional
+# information regarding copyright ownership.
+#
+# This program and the accompanying materials are made available under the
+# terms of the Apache License Version 2.0 which is available at
+# https://www.apache.org/licenses/LICENSE-2.0
+#
+# SPDX-License-Identifier: Apache-2.0
+
+# shellcheck disable=SC2148,SC2034
+
+# The file patterns that specify the relevant parts of the latest uProtocol Specification
+# that this component is supposed to implement
+UP_SPEC_FILE_PATTERNS="up-spec/basics/uattributes.adoc up-spec/up-l1/README.adoc up-spec/up-l1/mqtt_5.adoc"
+
+# The file patterns that specify this component's resources which contain specification items
+# that cover the requirements
+COMPONENT_FILE_PATTERNS="*.adoc *.md *.rs .github examples src tests"
+
+OFT_FILE_PATTERNS="$UP_SPEC_FILE_PATTERNS $COMPONENT_FILE_PATTERNS"
+OFT_TAGS="_,TransportLayerImpl,TransportLayerImplPush"

…rkflows/check-up-spec-compatibility.yaml …kflows/latest-up-spec-compatibility.yaml.github/workflows/check-up-spec-compatibility.yaml renamed to .github/workflows/latest-up-spec-compatibility.yaml .github/workflows/check-up-spec-compatibility.yaml renamed to .github/workflows/latest-up-spec-compatibility.yaml

@@ -12,11 +12,10 @@
 # *******************************************************************************/
 
 # Verifies that this crate can be built using the uProtocol Core API from up-spec's main branch.
-# Also performs requirements tracing using OpenFastTrace. For that purpose, the workflow requires
-# the UP_SPEC_OPEN_FAST_TRACE_FILE_PATTERNS variable to contain the file patterns to use for
-# invoking the "run-oft" Action.
+# Also performs requirements tracing using OpenFastTrace. The job fails if any of the two
+# activities fail.
 
-name: uP Spec Compatibility
+name: Latest uP Spec Compatibility
 
 on:
   schedule:
@@ -33,7 +32,7 @@ env:
   CARGO_TERM_COLOR: always
 
 jobs:
-  tests:
+  requirements-tracing:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
@@ -49,16 +48,23 @@ jobs:
           git status
           cd "${{ github.workspace }}"
 
-      # run OpenFastTrace first because OFT will always succeed and produce
+      - name: "Determine OpenFastTrace file patterns from .env file"
+        uses: xom9ikk/dotenv@v2.3.0
+        with:
+          mode: "oft-latest"
+          load-mode: strict
+
+      # run OpenFastTrace first because the action will always succeed and produce
       # a tracing report
       - name: Run OpenFastTrace
+        id: run-oft
         uses: eclipse-uprotocol/ci-cd/.github/actions/run-oft@main
         with:
-          file-patterns: "${{ vars.UP_SPEC_OPEN_FAST_TRACE_FILE_PATTERNS }} ${{ vars.UP_RUST_OPEN_FAST_TRACE_FILE_PATTERNS }}"
-          tags: "_,TransportLayerImpl,TransportLayerImplPush"
+          file-patterns: "${{ env.OFT_FILE_PATTERNS }}"
+          tags: "${{ env.OFT_TAGS_}}"
 
       # now try to build and run the tests which may fail if incomaptible changes
-      # have been introduced in up-spec
+      # have been introduced into the uProtocol Core API
       - uses: dtolnay/rust-toolchain@master
         with: 
           toolchain: ${{ env.RUST_TOOLCHAIN }}
@@ -70,3 +76,13 @@ jobs:
           cargo nextest run --all-features
           # but it cannot execute doc tests
           cargo test --doc --all-features
+
+      # This step will only be run if the tests in the previous step have succeeded.
+      # In that case, we use the exit code produced by the OFT run as the job's
+      # overall outcome. This means that the job fails if the tests run successfully
+      # but some of the requirements from up-spec are not covered.
+      - name: Determine exit status
+        env:
+          OFT_EXIT_CODE: ${{ steps.run-oft.outputs.oft-exit-code }}
+        run: |
+          exit $OFT_EXIT_CODE

.github/workflows/nightly.yaml

@@ -47,8 +47,9 @@ jobs:
   coverage:
     uses: eclipse-uprotocol/ci-cd/.github/workflows/rust-coverage.yaml@main
 
-  # disabled until up-spec repository has been tagged with the MQTT5 transport specification containing OFT spec items
-  # requirements-tracing:
+  # disabled until up-spec repository has been tagged with the MQTT5 transport specification containing
+  # OFT spec items
+  # current-spec-compliance:
   #   uses: eclipse-uprotocol/ci-cd/.github/workflows/requirements-tracing.yaml@main
   #   with:
-  #     oft-file-patterns: "${{ vars.UP_SPEC_OPEN_FAST_TRACE_FILE_PATTERNS }} ${{ vars.UP_RUST_OPEN_FAST_TRACE_FILE_PATTERNS }}"
+  #     env-file-suffix: "oft-current"