-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
gitresolver pipes extra resolved data through Annotation
Change 1: - before: The resolvedResource returned by gitresolver only contains revision and the actual yaml content. - now: The resolvedResource returned by gitresolver contains the actual yaml content and all information about git source - url, revision, pathToYaml Change 2: - before: The revision information in git resolvedResource is the original value provided by user, which can be actual commit hash, or branch name or tag. - now: For the branch name and tag, we fetch its actual commit hash and save it in the revision field of the resolvedResource. Change 3: - before: The resolvedResource's annotations are not used/passed to the runobject at all. - now: The annotations are passed to the runobject along with the annotations in resolved task. Motivation: Tekton Chains needs to capture the source of the config file (pipeline.yaml or task.yaml) in the SLSA provenance's `predicate.invocation.configSource` field. - Passing all 3 fields all the way from resolver to runobject will make it possible for Chains to capture the information without modifying user-defined spec. (change 1 + 3) - Aligning revision field to be actual hash helps Chains capture the actual diest which is required for the `predicate.invocation.configSource` field. (change 2)
- Loading branch information
Showing
15 changed files
with
197 additions
and
109 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.