[Feature]: Harden FileSystemSerDes publication and reference validation

未关闭
#679 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
python

调研方向

从 FileSystemSerDes 和配置的内部值 SerDes 开始,然后对比 aws/aws-durable-execution-sdk-java#648 中 Java SDK filesystem SerDes 的工作。审查 #527 中跟踪的云覆盖范围,涵盖不可变发布以及所有权/完整性场景。完成的标准是具备带版本且绑定所有者的 envelope、安全的不可变且经过完整性检查的读取、legacy 兼容性、保留的模式、异常重新序列化以及生命周期文档。

由索引模型根据 Issue 内容生成。

描述

enhancement parity pkg:sdk

What would you like?

Harden FileSystemSerDes so checkpoint file references remain immutable, integrity-checked, and bound to the durable payload that produced them.

The current implementation writes to a deterministic <operation_id>.json path using "w" and stores an unversioned {"file": ...} envelope. A later serialization for the same operation can overwrite content referenced by an older checkpoint, and deserialization trusts the file path carried in the envelope.

The desired behavior is:

  • publish each file payload immutably so an existing checkpoint never observes replaced content;
  • use a versioned, self-identifying filesystem envelope;
  • bind the envelope to its durable execution and entity identity;
  • verify file integrity and path safety before reading;
  • retain ALWAYS, OVERFLOW, preview, URI, and hash modes.

Possible Implementation

  • Serialize the configured value SerDes once, compute a SHA-256 digest, and create a unique payload file with exclusive-create semantics.
  • Include an envelope marker/version, owner durable execution ARN, owner entity/operation ID, payload type, file path, and content digest.
  • On deserialization, validate the recognized envelope, expected execution directory and filename, base-path containment, symbolic links, owner rules, and content digest.
  • Define explicit rules for safe cross-execution references such as invocation input/results. When an exception is forwarded through a child context, deserialize and reserialize it under the new owner rather than copying an owner-bound file envelope.
  • Preserve compatibility by continuing to read the existing legacy envelope format for an appropriate migration period.
  • Document storage lifecycle guidance because immutable payload publication can create orphaned files after checkpoint replacement.
  • Extend the cloud coverage tracked by #527 with immutable publication and ownership/integrity scenarios.

Is this a breaking change?

No. Existing constructors and configuration should remain compatible, and legacy envelopes can continue to be readable.

Does this require an RFC?

Yes.

Additional Context

The Java SDK filesystem SerDes work in aws/aws-durable-execution-sdk-java#648 uses immutable publication, versioned ownership metadata, content hashes, containment checks, and symbolic-link rejection. This issue requests equivalent guarantees adapted to Python's synchronous SerDes[Any] and configurable inner value SerDes.

主要语言
Python
星标
59
派生
32
平均合并
1 天 5 小时
30 天内合并 PR
76

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

aws/aws-durable-execution-sdk-python 的其他 Issue

查看 aws/aws-durable-execution-sdk-python 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。