You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 10, 2023. It is now read-only.
Bug description
Theres alot of compile deps, but the way we call hack/tools/Makefile doesnt clean them out which means that if you have older ytt like 3.0, youll get unobvious errors like
ytt: Error: Non-ytt comment at line upstream/metadata.yaml:1: '# maps release series of major.minor to cluster-api contract version':
Unrecognized comment type (expected '#@' or '#!'). (hint: if this is plain YAML — not a template — consider `--file-mark '<filename>:type=yaml-plain'`)
This can cost hours of developer debugging on a local env. So we need to quickly test YTT (and optionally other versions) in the hack tools make flow, after running it so that we can inform users that they have a wrong version in their toolchain in the hack dir.
Affected product area (please put an X in all that apply)
( ) APIs
( ) Addons
( ) CLI
( ) Docs
( ) IAM
( ) Installation
( ) Plugin
( ) Security
( x ) Test and Release
( ) User Experience
( x ) Developer Experience
Expected behavior
the make tools workflow will ensure that you either have the right tools, or explicitly fail.
Steps to reproduce the bug
install ytt 0.3.0 in hack/tools/bin and then run make test
Version (include the SHA if the version is not obvious)
main
Environment where the bug was observed (cloud, OS, etc)
Relevant Debug Output (Logs, manifests, etc)
The text was updated successfully, but these errors were encountered:
Bug description
Theres alot of compile deps, but the way we call hack/tools/Makefile doesnt clean them out which means that if you have older ytt like 3.0, youll get unobvious errors like
This can cost hours of developer debugging on a local env. So we need to quickly test YTT (and optionally other versions) in the hack tools make flow, after running it so that we can inform users that they have a wrong version in their toolchain in the hack dir.
Affected product area (please put an X in all that apply)
Expected behavior
the make tools workflow will ensure that you either have the right tools, or explicitly fail.
Steps to reproduce the bug
install ytt 0.3.0 in hack/tools/bin and then run
make test
Version (include the SHA if the version is not obvious)
main
Environment where the bug was observed (cloud, OS, etc)
Relevant Debug Output (Logs, manifests, etc)
The text was updated successfully, but these errors were encountered: