Warn about upcoming removal of git outputs #1283
Labels
area/release
Indicates an issue on release (process, tasks).
Comments
bobcatfish
added a commit
to bobcatfish/pipeline
that referenced
this issue
Sep 14, 2019
In tektoncd#1109 we will be removing support for git as an output. In the current implementation, git as an output is just a volume that holds the data from the git repo, and copies it between Tasks (when git as an output is linked to git as an input). As discussed in tektoncd#1076, the model we want for PipelineResources is for them to take the outside world and represent it on disk when used as an input, and when used as an output, to update the outside world. In order to do this, what we actually want for a git output is for it to create a commit the repo it is referencing. However up until this point folks have been using git resources in the way that we want Volume Resources to behave tektoncd#1062, so we want to transition folks to Volume Resources and away from using git outputs. Fixes tektoncd#1283
3 tasks
|
@bobcatfish @dlorenc what is the status for this one ? /kind api |
|
Looks like the warning was added in #1310 ! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In #1109 we will remove support for git outputs. We may add support via #1280 in the same release but even if we do, the functionality of a git output will be radically different from what it is today. We should include a warning in 1 release, via both release notes and via a warning logged by the controller whenever git is used as an output.
The text was updated successfully, but these errors were encountered: