Releases · hauler-dev/hauler

20 Feb 13:10

github-actions

v1.0.0

79b240d

v1.0.0

Changelog

214704b adding graphics @bgulla
6ca7fb6 updated readme and removed roadmap @zackbradys
d70a867 updated/cleaned up install.sh @zackbradys
5592ec0 remove deprecated commands @amartin120
4759879 Bump helm.sh/helm/v3 from 3.14.0 to 3.14.1 @dependabot
dbcfe13 bug-fix: handle complex file names @amartin120
cd8d4f6 add login command @amartin120
ccd529a update to add size totals and cosign bits to the info command @amartin120

Full Changelog: v0.4.4...v1.0.0

Contributors

bgulla, zackbradys, and 2 other contributors

Assets 10

16 Feb 13:30

github-actions

v1.0.0-rc.1

e825437

v1.0.0-rc.1 Pre-release

Pre-release

Changelog

4759879 Bump helm.sh/helm/v3 from 3.14.0 to 3.14.1
dbcfe13 bug-fix: handle complex file names
cd8d4f6 add login command
ccd529a update to add size totals and cosign bits to the info command

Assets 10

13 Feb 00:46

github-actions

v0.4.4

3cf4afe

v0.4.4

Changelog

59ff02b add annotations for registry @amartin120
8b33980 add annotations for key and platform @amartin120

Full Changelog: v0.4.3...v0.4.4

Hauler now allows for the use of key/platform/registry annotations for the image spec of a Hauler manifest. This gives users the ability to provide global overrides without the use of specifying flags via the CLI.

apiVersion: content.hauler.cattle.io/v1alpha1
kind: Images
metadata:
  name: <name>
  annotations:
    hauler.dev/key: <cosign public key>
    hauler.dev/platform: <platform>
    hauler.dev/registry: <registry>

Flags passed from the CLI have a global effect on any image UNLESS it has a (key/platform) specified on the individual image. Individual image key/platform takes precedence.

If you have hauler.dev/key and/or hauler.dev/platform at the annotation level, it would work just like the CLI flag and globally apply for everything except individual images specifying otherwise. Just like above.

If you just so happen to provide both an annotation AND the CLI flag for the same thing, the CLI flag wins.

As for the hauler.dev/registry annotation, it will apply globally unless the provided image reference already has a registry specified in its name.

Contributors

amartin120

Assets 10

31 Jan 21:08

github-actions

v0.4.3

ae80b48

v0.4.3

Changelog

1ae496f dep bumps for security vuln fixes @amartin120
fc7a19c check tag to determine pre-release @amartin120
85d6bc0 Update install.sh for file cleaning @clemenko
a05d21c add platform flag for image add and sync @amartin120
0e6c369 bump cosign version to v2.2.2+carbide.2 @amartin120
a977cec improve cosign setup @amartin120
fbafa60 updated archive default name @zackbradys
b24b25d add license file @amartin120
d9e298b adjust to make registry and fileserver subcommands @amartin120
e14453f add fileserver option for store serve @amartin120

Notable updates:

hauler store add image and hauler store sync now have a --platform flag for better handling of multi-arch images. Omitting the flag will default to pulling/saving the entirety of a multi-arch image just as it's done in previous versions.
- Hauler manifests provided to the sync command now support a platform attribute for individual images as well. For example:
```
apiVersion: content.hauler.cattle.io/v1alpha1
kind: Images
metadata:
name: hauler-content-images-example
spec:
images:
  - name: nginx
    key: key.pub
    platform: linux/amd64
```
hauler store serve has been broken down into hauler store serve registry/fileserver to handle the addition of the fileserver option.
cosign has better integration with Hauler. (behind the scenes stuff, but still...)