Fixes#79
Changes:
1. Renames task `kn-create` to `kn`
2. `kn` task takes a parameter of type array as `ARGS`
3. `kn` task defines a resource of type image as `image`
4. User should reference the `image` as an element of array parameter `ARGS` for e.g. `--image=$(inputs.resources.image.url)`
5. Additional `ClusterRole` for `kn-deployer` account for `revisions` and `routes` resources
6. Adds examples in README.md for creating and updating a Knative Service
7. Adds `kn-image` parameter to task for referencing the kn CLI image to be used, defaults to latest released version of kn image available `gcr.io/knative-releases/github.com/knative/client/cmd/kn`
We are currently using the latest release to run tests on
catalog. This means this fails with 0.7.0 and above.
`containerTemplate` is now `stepTemplate`.
Signed-off-by: Vincent Demeester <vdemeest@redhat.com>
This will remove the script used in image for/
openshift client task.
As we are able to provide arguments as string
with tekton pipeline 0.6.0
we dont need script any more, also updated the
Dockerfile, tasks and README accordingly
Conftest is a tool used to validate configuration files using Open
Policy Agent. This commit adds a `Task` spec for using Conftest from
Tekton, along with documentation of the parameters and usage.
The default value of GO11MODULE is auto in golang.
We should allow to change the value, in order to force module support on or off regardless of directory location
Signed-off-by: jtcheng <jtcheng0616@gmail.com>
Adding OpenWhisk Tekton Resources which can be used to serve OpenWhisk actions on Knative.
These changes include an entire workflow of how to run OpenWhisk Actions on Knative,
specifically OpenWhisk NodeJS runtime. It also includes examples such as:
1. Simple Hello World action
2. Hello World action with JSON Payload as Parameters
3. OpenWhisk Action File from a GitHub Repo
4. OpenWhisk Action from a zip file
Kubeval is a tool used to validate Kubernetes configuration against
the upstream object schemas. This commit adds a `Task` spec for using
Kubeval from Tekton, along with documentation of the parameters and usage.
This task is used to sync an Argo CD application with its underlying Git repository and to wait for it to become healthy. It takes in no resources, only parameters, and passes them to the argocd command. The application's name and the Argo CD server address are required. Some form of login is also required, either through a username/password combo or an authentication token. The specific revision to sync to and the flags to append to commands can also be passed as parameters.
Currently there is no way to pass plain strings or files between tasks, or it could have been better to split the login and sync tasks. This way, there could have been two login tasks - one for username/password and one for authentication token. With the current approach, the bash command runs an if statement to see if the token's default value was overriden, and if so, it uses that token. Otherwise, it uses the username/password passed in. This issue (typing of PipelineResources) is being discussed in https://github.com/tektoncd/pipeline/issues/238.
This adds initial golang tasks : build (`golang-build`),
tests (`golang-tests`) and linting (`golangci-lint`, using
golangci-lint).
Signed-off-by: Vincent Demeester <vdemeest@redhat.com>
- Small fix on the parameter name (and comments), `BUILDER_IMAGE` and
`S2I_IMAGE` were inverted.
- Remove the `examples` folder and add an example inline.
- Add a non-exhaustive list of s2i builder images that can be used
with this task.
Signed-off-by: Vincent Demeester <vdemeest@redhat.com>
We need to pin to specific version rather than go with the dynamic
latest commit. The version v0.9.0 seems to be a stable one.
Add the parameter context support for kaniko.
This will add a script to Dockerfile which will
receive command as string and then parse them
to execute with oc
This way we can make the task resuable
Changes to use the ubi image as base image
Update both the examples to use reusables task
Update README
This e2e test just verifies each task is valid by setting up a test cluster and
creating each task. This uses boskos to provision and clean a project.
This also fixes up the makisu task to remove the extraneuous yaml file.
Those comments are added by default when doing a `dep init`. We don't
need them and can just refer to the documentation instead.
Signed-off-by: Vincent Demeester <vdemeest@redhat.com>
As Pipeline graduated from `knative`, we're trying, with `plumbing` to
make remove our dependency on knative `test-infra` scripts. Those
scripts have been migrated to `tektoncd/plumbing`, so let's start use those.
The end goal being to reduce even more the use of those script and
only use pipeline to run experimental pipelines 👼.
Signed-off-by: Vincent Demeester <vdemeest@redhat.com>
