menedev / dockmoor Goto Github PK

The update command should update images to the latest image according to SemVer-based tags or the current latest image.

Blocked by #8

The pin command replaces image references with their equivalent, but more reproducible counterpart.
Ways to archive that:

• Add digest to image reference
• Add (more specific) tag.
  • none -> latest
  • none -> 1.2.1
  • latest -> 1.2.1
  • 1.2 -> 1.2.1

Note that the substitution should only be performed if the new reference is equivalent, i.e. referring to the same image.
Depending on the scope this can mean one of two things:

• Docker Daemon (blocked by #1 )
• Docker Registry (blocked #2)

There should be an option to toggle between both scopes. Blocked by #8

Based on information from either the docker daemon (blocked by #1) or a docker repository (blocked be #2), image references with a tag complying to SemVer rules can be identified and filtered when there are no newer versions available.

Blocked by #8

Dockmoor has several filters, to limit actions to a set of image references. This includes:

• domain
• name
• tag

For all those filters a regex implementation would be useful.

The regex implementation could be triggered by surrounding the string with / on the commandline, e.g.

dockmoor list --tag "/-testing/"

However other implementations are welcome.

dockmoor should be able to pin an image reference to the version that is currently used. For this to work, the docker daemon must be queried for the digest of the current image version.

Implement the dockfmt.Format interface for .travis.yml.

Design goal: When the file is changed, every change must be as local as possible. That means that white-spaces (including line-endings) and comments are retained. Only the image reference may change.

While this is not strictly blocked by #5 / #13, the design goal only makes sense afterwards.

dockmoor should be able to pin an image reference to the version that is currently available on a repository. For this to work, the repository must be queried for the digest of the current image version.

Implement the dockfmt.Format interface for docker-compose.yml.

Design goal: When the file is changed, every change must be as local as possible. That means that white-spaces (including line-endings) and comments are retained. Only the image reference may change.

While this is not strictly blocked by #5 / #13, the design goal only makes sense afterwards.

http://tldp.org/LDP/abs/html/exitcodes.html

The interface should allow to query all tags and their digest.
Blocked by #1 and #2

Implement the dockfmt.Format interface for .circleci/config.yml.

Design goal: When the file is changed, every change must be as local as possible. That means that white-spaces (including line-endings) and comments are retained. Only the image reference may change.

While this is not strictly blocked by #5 / #13, the design goal only makes sense afterwards.

Each component of a reference should be reflected by at least one predicate.

See https://github.com/docker/distribution/blob/master/reference/reference.go

The components are:

• Domain (including port)
• Path
• Tag
• Digest

There is also the synthesized

• Name (which is Domain + Path)
• FamiliarName (which is just the last path-component, e.g. nginx for docker.io/library/nginx)

which should be taken into account as this seems to be the most widely used form of docker image references.

Since yaml is widely used, there should be a common set of helpers to cope with the format. Unfortunately there is currently no round-trip parser for yml in go.

The helpers should allow to retrieve and replace values by path. Other implementations are welcome as long as they allow to change single values without affecting other parts of a yaml file.

Both, AsciiDoc and Markdown, are not part of this projects scope. Also other projects could benefit from a generated documentation, just like dockmoor does.

Implement the dockfmt.Format interface for .gitlab-ci.yml.

Design goal: When the file is changed, every change must be as local as possible. That means that white-spaces (including line-endings) and comments are retained. Only the image reference may change.

While this is not strictly blocked by #5 / #13, the design goal only makes sense afterwards.

We currently lack instructions how to compile the project locally.