-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: release 2.0 #30
Conversation
Co-authored-by: Fritz Durchardt <fritz.duchardt.ext@gec.io> Co-authored-by: German Lashevich <german.lashevich@gmail.com> Closes #32
On vendir sync a new vendir.sync.yaml is safed to the "tmp" folder containing the current state of vendir.yaml condensed into hash values. If this file remains unchanged, vendir sync can be omitted. The feature can be enabled on environment and application level with the new application.cache.enabled flag.
On vendir sync a new vendir.sync.yaml is safed to the "tmp" folder containing the current state of vendir.yaml condensed into hash values. If this file remains unchanged, vendir sync can be omitted. The feature can be enabled on environment and application level with the new application.cache.enabled flag.
feat: Add Vendig Sync caching
feat: Add vendir authentication via the enviroment
Co-authored-by: Fritz Durchardt <fritz.duchardt.ext@gec.io> Closes #37
Co-authored-by: Fritz Durchardt <fritz.duchardt.ext@gec.io> Co-authored-by: German Lashevich <german.lashevich@gmail.com>
#62) …s and Applications --------- Co-authored-by: Fritz Durchardt <fritz.duchardt.ext@gec.io>
fix: make render errors more prominent
Co-authored-by: Fritz Durchardt <fritz.duchardt.ext@gec.io>
Co-authored-by: Kris Budde <kris.budde@gec.io>
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
Co-authored-by: German Lashevich <german.lashevich@gmail.com>
No description provided.