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 was archived by the owner on Oct 29, 2021. It is now read-only.
Is it a goal to allow tl's verify method to be built into other Go applications? I am thinking similarly how Kustomize provides API packages that it then uses itself to provide the CLI's functionality.
My use case is, that I provide release artifacts as zip files for both framework releases and upstream services I package. The kbst CLI scaffolds user repositories from release artifacts and also vendors packaged manifests from catalog artifacts in a user's repository.
Optimally I could use the GitHub action to add release artifacts to the log and have kbst verify artifacts automatically.
Am I on the right track here? I'd be happy to follow this issue up with a PR if this is a direction that you think is useful.
The text was updated successfully, but these errors were encountered:
Is it a goal to allow
tl
's verify method to be built into other Go applications? I am thinking similarly how Kustomize provides API packages that it then uses itself to provide the CLI's functionality.My use case is, that I provide release artifacts as zip files for both framework releases and upstream services I package. The
kbst
CLI scaffolds user repositories from release artifacts and also vendors packaged manifests from catalog artifacts in a user's repository.Optimally I could use the GitHub action to add release artifacts to the log and have
kbst
verify artifacts automatically.Am I on the right track here? I'd be happy to follow this issue up with a PR if this is a direction that you think is useful.
The text was updated successfully, but these errors were encountered: