feat(cd): set DEFANG_ETAG env in CD task

[lionello]

Description

GCP was already using DEFANG_ETAG so doing the same for AWS and DO.

Linked Issues

Checklist

• I have performed a self-review of my code
• I have added appropriate tests
• I have updated the Defang CLI docs and/or README to reflect my changes, if necessary

Summary by CodeRabbit

• Infrastructure Improvements
  • Enhanced continuous deployment operation tracking and identification across AWS and DigitalOcean BYOC providers, enabling improved monitoring and log retrieval throughout the deployment lifecycle.

[jordanstephens]

Nice!

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

---

📝 Walkthrough

Walkthrough

The pull request introduces per-CD-operation etag handling in BYOC AWS and DO client implementations. An etag field is added to cdCommand structs and threaded through CD command construction, deployment flows, and log retrieval operations, with the etag propagated via environment variable.

Changes

Cohort / File(s)	Summary
BYOC AWS CD Etag Handling src/pkg/cli/client/byoc/aws/byoc.go	Added etag field to cdCommand struct. Generate etag during deploy flow and include in ProjectUpdate payload. Thread etag through CD command creation and pass via DEFANG_ETAG environment variable. Updated log retrieval to match etag against stored cdEtag or CD task ID. Store etag in provider state on CD execution.
BYOC DO CD Etag Handling src/pkg/cli/client/byoc/do/byoc.go	Added etag field to cdCommand struct. Initialize etag in CdCommand creation and propagate through deploy and CdCommand paths. Support DEFANG_ETAG injection in Pulumi environment during CD command execution. Update b.cdEtag tracking accordingly.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

• chore: add deployment_id to ProjectUpdate proto #1942: The main PR's etag field additions in ProjectUpdate payload directly enable the per-CD etag threading introduced in these BYOC changes.
• Always use etag for gcp cdCommands, remove useless code #1772: Related PR making identical cdCommand etag field additions and switching CD flow to per-operation etag handling.

Suggested reviewers

• jordanstephens
• edwardrf

Poem

🐰 Per-operation etags now flow,
Through AWS and DO, all aglow,
Each CD command gets its own ID,
No more ambiguity, hooray for thee! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'feat(cd): set DEFANG_ETAG env in CD task' directly and specifically describes the main change: adding the DEFANG_ETAG environment variable to CD tasks.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch lio/set-etag-env

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 golangci-lint (2.5.0)

level=warning msg="[linters_context] running gomodguard failed: unable to read module file go.mod: current working directory must have a go.mod file: if you are not using go modules it is suggested to disable this linter"
level=error msg="[linters_context] typechecking error: pattern ./...: directory prefix . does not contain main module or its selected dependencies"

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}