Why can't Apple do a patch?

Brett Tofel — Sun, 28 Mar 2021 15:30:08 +0000

The cover image for this post shows updates being recommended for four (4) of the applications on my Mac. They represent 3+ Gb of download from Apple's App Store. So I guess I just wanted to wonder out loud...

At this size, these certainly don't seem to be binary patch files, and if not, why not?

BinaryMisfit on this StackExchange thread from 2 years ago states the following:

AppStore updates at the moment is always a complete full version of the new application being downloaded, the copy you have replaced, and the balance trashed.

This seems really wasteful for the millions of MacOS App Store users' bandwidth and for Apple's bandwidth.

Comments, or insight, appreciated.

How to AND NOT something in a CRD

Brett Tofel — Tue, 19 Nov 2019 14:21:40 +0000

This advice is valid for sure if you're working with a Kubernetes CRD with version like this:

apiVersion: apiextensions.k8s.io/v1beta1
kind: CustomResourceDefinition

It might be valid for other versions too.

If you want to create a structural CRD, and you want to require something not be there when some other value is set one way or another, here's an example.

                            prometheus:
                              type: object
                              oneOf:
                              - required:
                                - enabled
                                - uri
                                properties:
                                  enabled:
                                    enum:
                                    - true
                              - properties:
                                  enabled:
                                    enum:
                                    - false
                                allOf:
                                - not:
                                    required:
                                      - uri
                              properties:
                                enabled:
                                  description: Whether or not to enable the Presto-Prometheus connector.
                                  type: boolean
                                uri:
                                  description: URI for Prometheus.
                                  type: string
                                  format: uri
                                chunkSizeDuration:
                                  description: Default size of each Prometheus query chunk.

So that means:

We require oneOf the subschemas to be fulfilled. Either enabled is true in which case we require uri be defined. Or, enabled is false in which case, uri is not required. The extra allOf in there, in this case, is simply a way to allow for the not in that 2nd subschema. And just highlight what is meant by subschemas. oneOf starts a list of them. So the first is:

                              - required:
                                - enabled
                                - uri
                                properties:
                                  enabled:
                                    enum:
                                    - true

and the second is:

                              - properties:
                                  enabled:
                                    enum:
                                    - false
                                allOf:
                                - not:
                                    required:
                                      - uri

And to be structural you must list all the properties again, and you can include any items you're not setting requirements on. Which is the rest of the yaml above.

Happy computing.

DEV Community: Brett Tofel

Why can't Apple do a patch?

How to AND NOT something in a CRD