hmm wonder how you could get to explicit opt-in with a separate type or something that requires the container image be set. That way you can assert up front that whatever your image scheme is is working properly - such as ensuring the environment variable containing the image is set.
might make sense to model this as a context or something since I may want to know what git branch / commit checkout the code is at in the same way i might want to know what image i am running in. Maybe a bunch of optionals is an ok way to capture that.
|288 ↗||(On Diff #25173)|
there are workarounds we can employ using whitelist_for_persistence to control the serialization format, in this case drop keys for the new fields if value is None so it doesn't change the output string and therefor hash
thats if we even need to bother depending on our 0.10.0 plans