This is an automated email from the ASF dual-hosted git repository.

lahirujayathilake pushed a change to branch swag-api
in repository https://gitbox.apache.org/repos/asf/airavata-custos.git


    omit 1ec838001 Integrated swag-driven OpenAPI spec generation
    omit f14290123 Renumber audit migrations for consistency
    omit 64709e780 Consolidate AMIE migrations and switch trace/span IDs to hex 
strings
    omit c4b7246cc Move AMIE HTTP endpoints into the connector via mux 
passthrough
    omit 677bfa0db Update AMIE baseline integration tests to align with the new 
audit modeling
    omit 276496522 Add AMIE endpoints
    omit 2d81f32ad Drop UNION in audit_trace_store
    omit 9809e5f6d Route AMIE audit writes through core audit_events
    omit 7b1a3cd31 Replace amie_audit_log with amie_audit_extras table
    omit 93345d872 Add entity_type column to audit_events
    omit 02a6fde1a Rename TraceEvent fields and COmanage subscriber audit event 
for clarity
    omit f170fa5d3 Renumber tracing migrations
    omit 83fdf59e5 Updated the baseline amie integration tests to reflect the 
additional tracing events
    omit 234fb1984 Remove cross-connector tracing test from AMIE pipeline 
package
    omit e6d12a477 expose audit endpoints
    omit b5e168f66 Add audit-driven trace store that reads audit_events and 
amie_audit_log
    omit ab20cbcfe source-column
    omit 37efe47c8 Include tracing for SLURM subscribers
    omit 916e102f9 Include tracing for COmanage subscriber
    omit f4060a70d Include tracing for AMIE packet handlers
    omit c2b01ae7a Add trace_id, span_id and parent_span_id columns
    omit ff2563ed0 Propagate request context across event bus so subscribers 
inherit trace IDs
    omit 73cfbf7aa add OpenTelemetry tracing package for context propagation
     add 4759f2ea9 Request tracing support across core and connectors (#489)
     add 4220822c1 Integrated swag-driven OpenAPI spec generation

This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version.  This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:

 * -- * -- B -- O -- O -- O   (1ec838001)
            \
             N -- N -- N   refs/heads/swag-api (4220822c1)

You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.

Any revisions marked "omit" are not gone; other references still
refer to them.  Any revisions marked "discard" are gone forever.

No new revisions were added by this update.

Summary of changes:

Reply via email to