Michael Bridgen

Supply digest of images that are selected by policy

1

You sometimes want to use the digest of an image, rather than the tag; e.g., if you are interested in exactly reproducible builds. For that reason, it'd be useful to...

git revision policy

1

So far there's a semver policy for selecting images, which selects the highest version within a given range. Another variety of policy that we use everywhere in the Weave Cloud...

It's sometimes necessary to pin an automation to a particular tag of an image, say if - there's a known bad image that would be selected by the policy, and...

Tell user if a duplicate "extracted" tag is seen

2

With regexp filtering, it's possible to extract a value from each tag for the policy to consider. This is to cover a use case like giving all your tags `dev-`,...

Order by build timestamp (label)

2

I.e., how Flux v1 does it. - needs to download image metadata, so will need rate limiting, caching, garbage collection; - explicitly specify to use labels (rather than guessing)

Filter out images at ImageRepository level

7

In a given `ImagePolicy` object you may want to select a subset of the images, e.g., those marked as destined for a particular environment `dev-*`. You might _also_ want to...

When stack objects aren't deleted after tests, it can mean - resources created by the stack aren't tidied up; - the finalizer logic isn't well tested - the stack might...

Since #324 and #336, you can refer to sources that are represented by other custom resources (Flux sources, and Pulumi YAML-containing Program objects). It would be nice to make these...

This changes the which-source-is-it switch around a little, so that instead of each case checking something is non-nil and all the others are nil, the invalid cases are ruled out...

This example shows how to set up the operator and Flux's source controller so they can work together. It includes a subordinate example which shows how to create a `GitRepository`...