fix(lambda): report resolved executed version

[aniketshukla1]

Summary

Closes #1989.

• Carry the resolved Lambda target version through the invocation result.
• Emit that version in X-Amz-Executed-Version instead of always reporting $LATEST.
• Add a version-qualified DryRun regression test for the public HTTP endpoint.

Type of change

• Bug fix (fix:)
• New feature (feat:)
• Breaking change (feat! or fix!)
• Docs / chore

AWS Compatibility

Version-qualified and alias-qualified invokes previously reported $LATEST even when another published version ran. The header now reports the resolved version, including aliases that route to a version.

Checklist

• ./mvnw test passes locally
• New or updated integration test added
• Commit messages follow Conventional Commits

Focused verification: ./mvnw -q -Dtest=LambdaVersionIntegrationTest test and ./mvnw -q -Dtest=LambdaIntegrationTest test (JDK 25).

[github-actions]

🎉 Thanks for your first pull request to Floci!

Your CI checks need a maintainer to approve them before they run. That is GitHub's standard gate on first-time contributors, not a problem with your PR — so if the checks look like they are doing nothing, that is why. Once a maintainer approves, CI and the compatibility suite start automatically. Nothing is needed from you in the meantime.

While you wait, a couple of things that make review faster:

• Link the issue this fixes with Closes #N in the description
• Commits follow Conventional Commits (feat(s3): ..., fix(dynamodb): ...)
• Behaviour changes come with a test — see CONTRIBUTING.md

Come join us in Slack — it is the fastest way to reach maintainers if you get stuck, or want feedback on an approach before investing more time in it.

[greptile-apps]

Greptile Summary

Fix X-Amz-Executed-Version to report the resolved Lambda version instead of always $LATEST.

• InvokeResult carries executedVersion; LambdaService.invoke sets it from the resolved LambdaFunction.getVersion().
• LambdaController emits that value on the invoke response header.
• Integration test covers DryRun invoke of function:1 expecting header 1.

Confidence Score: 5/5

Safe to merge; the resolved version is set on every LambdaController invoke path and defaults correctly for $LATEST and published versions.

Controller always goes through LambdaService.invoke, which sets executedVersion from LambdaFunction.version (default "$LATEST", numeric after publish/alias resolve). Direct executor callers do not emit this header. No null or wrong-header failure remains on the public invoke path.

Important Files Changed

Filename	Overview
src/main/java/io/github/hectorvent/floci/services/lambda/LambdaService.java	After executor invoke, stamps resolved fn version onto InvokeResult for the HTTP header path.
src/main/java/io/github/hectorvent/floci/services/lambda/LambdaController.java	Replaces hardcoded $LATEST with result.getExecutedVersion() on X-Amz-Executed-Version.
src/main/java/io/github/hectorvent/floci/services/lambda/model/InvokeResult.java	Adds executedVersion field with getter/setter; controller path always sets it via LambdaService.
src/test/java/io/github/hectorvent/floci/services/lambda/LambdaVersionIntegrationTest.java	Adds ordered DryRun test that version-qualified invoke returns X-Amz-Executed-Version 1.

Sequence Diagram

sequenceDiagram
  participant Client
  participant LambdaController
  participant LambdaService
  participant Executor as LambdaExecutorService
  Client->>LambdaController: POST .../functions/name:1/invocations
  LambdaController->>LambdaService: invoke(region, name:1, ...)
  LambdaService->>LambdaService: "resolveInvokeTarget → fn.version=1"
  LambdaService->>Executor: invoke(fn, payload, type)
  Executor-->>LambdaService: InvokeResult
  LambdaService->>LambdaService: setExecutedVersion(fn.getVersion())
  LambdaService-->>LambdaController: result
  LambdaController-->>Client: X-Amz-Executed-Version: 1

Loading

_{Reviews (1): Last reviewed commit: "fix(lambda): report resolved executed ve..." | Re-trigger Greptile}

[pgermosen]

Looks good
(added a new comments both are minors)

Clean, correctly-layered fix. X-Amz-Executed-Version was hardcoded to "$LATEST" at LambdaController.java:253 regardless of what actually ran; the resolved target now flows through InvokeResult instead. Three lines of real logic, in the one layer that knows the answer.

One process note: the checklist leaves ./mvnw test passes locally unticked, with focused runs of LambdaVersionIntegrationTest and LambdaIntegrationTest instead. I ran the full suite against this head, so that box is covered — see above.

[pgermosen]

No $LATEST baseline — which is the case that could actually regress.

The header used to be hardcoded "$LATEST", so an unqualified invoke was accidentally correct before and needs to stay correct now. Nothing asserts it, and it's the cheapest possible regression guard — it also covers the qualifier == null branch of resolveInvokeTarget, which the new test doesn't touch:

    @Test
    @Order(4)
    void invokeUnqualifiedReturnsLatest() {
        given()
            .header("X-Amz-Invocation-Type", "DryRun")
        .when()
            .post(BASE_PATH + "/functions/" + FUNCTION_NAME + "/invocations")
        .then()
            .statusCode(204)
            .header("X-Amz-Executed-Version", equalTo("$LATEST"));
    }

[pgermosen]

Verified this is safe, noting it so the reasoning is on record.

Setting the field here rather than in the executor is the right call — LambdaService is the layer that resolved the qualifier, and LambdaExecutorService never sees it. Two things I checked because they'd have been silent failures:

• fn.getVersion() can't be null: LambdaFunction.version defaults to "$LATEST" (LambdaFunction.java:42) and is only reassigned on publish (:934). That matters more than it looks — JAX-RS header(name, null) removes the header rather than sending it empty, so a null here would have silently dropped X-Amz-Executed-Version from every response, a regression from the old always-$LATEST behavior.
• executorService.invoke returns a non-null InvokeResult on every path (DryRun 204, Event 202, and each executeSync branch), so this can't NPE.

Minor style point, take it or leave it: this is a set-after-construct on an object that otherwise arrives fully built by its constructor. Threading it through as a constructor arg would keep InvokeResult immutable-ish, but that touches five call sites for little gain — I'd leave it.

[aniketshukla1]

@pgermosen Thanks for the review, much appreciated.

[aniketshukla1]

@hectorvent , is there anything else needs to be done in this ? Let me know.
Thanks

[hectorvent]

Thanks @aniketshukla1

[hectorvent]

🎉 This PR is included in version 1.6.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀