Transition Secure MAX_IMAGE_SIZE_BYTE to MAX_IMAGE_SIZE_MB

Problem to solve

We currently rely on MAX_IMAGE_SIZE_BYTE as a signaling mechanism for becoming aware of large image size increases in our devopssecure docker images. This is overly prescriptive and too much of a magic number. In the case of our images we often do not care if the image size increases by less than a MB so I'd vote we reduce the specificity to MBs, or if there is debate, at least KBs.

Intended users

• Delaney (Development Team Lead)
• Sasha (Software Developer)

User experience goal

Easier version bumps and community contributions

Proposal

Drop MAX_IMAGE_SIZE_BYTE in favor of MAX_IMAGE_SIZE_MB

Further details

Permissions and Security

Documentation

Availability & Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Is this a cross-stage feature?

All groups of devopssecure, groupcomposition analysis groupstatic analysis groupdynamic analysis

Links / references