Michael Warkentin
Michael Warkentin
We should also reconsider (per our discussions) if `--no-strict-offset-reset` even needs to be a thing anymore now that we primarily use `--auto-offset-reset=earliest` for all of our consumers.
Just came across a proposal for UUIDv7 which supports time-ordered values: https://datatracker.ietf.org/doc/html/draft-peabody-dispatch-new-uuid-format-04#name-uuid-version-7
+1! Although I wonder if termination protection should be a separate resource from the stack itself? This is how it's modelled in the AWS API, and it would allow us...
See https://docs.aws.amazon.com/AWSCloudFormation/latest/APIReference/API_UpdateTerminationProtection.html