Created
February 17, 2019 12:44
-
-
Save tzununbekov/df2530be4db511d6bf05e711a6b80877 to your computer and use it in GitHub Desktop.
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
| package main | |
| import ( | |
| "fmt" | |
| "log" | |
| "time" | |
| "github.com/ghodss/yaml" | |
| "github.com/knative/build-pipeline/pkg/apis/pipeline/v1alpha1" | |
| metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" | |
| ) | |
| func main() { | |
| tr := v1alpha1.TaskRun{ | |
| TypeMeta: metav1.TypeMeta{ | |
| Kind: "TaskRun", | |
| APIVersion: "pipeline.knative.dev/v1beta1", | |
| }, | |
| ObjectMeta: metav1.ObjectMeta{ | |
| Name: "taskname", | |
| Namespace: "default", | |
| CreationTimestamp: metav1.Time{Time: time.Now()}, | |
| }, | |
| Spec: v1alpha1.TaskRunSpec{ | |
| TaskRef: &v1alpha1.TaskRef{ | |
| Name: "taskrefname", | |
| }, | |
| Trigger: v1alpha1.TaskTrigger{ | |
| Type: v1alpha1.TaskTriggerTypePipelineRun, | |
| Name: "testtriggername", | |
| }, | |
| }, | |
| } | |
| out, err := yaml.Marshal(tr) | |
| if err != nil { | |
| log.Fatal(err) | |
| return | |
| } | |
| fmt.Printf("%s", out) | |
| } |
When I attempted to do something similar with the same block, I ran into:
cab@ptolamaios:/nfs-scratch/cab/clients/triggermesh/github-actions/foo$ go build # _/nfs-scratch/cab/clients/triggermesh/github-actions/foo ./main.go:15:3: cannot use "k8s.io/apimachinery/pkg/apis/meta/v1".TypeMeta literal (type "k8s.io/apimachinery/pkg/apis/meta/v1".TypeMeta) as type "github.com/knative/build-pipeline/vendor/k8s.io/apimachinery/pkg/apis/meta/v1".TypeMeta in field value ./main.go:19:3: cannot use "k8s.io/apimachinery/pkg/apis/meta/v1".ObjectMeta literal (type "k8s.io/apimachinery/pkg/apis/meta/v1".ObjectMeta) as type "github.com/knative/build-pipeline/vendor/k8s.io/apimachinery/pkg/apis/meta/v1".ObjectMeta in field valueGranted I just ran
go get && go buildhowever from what I've seen floating around this seems to be more of how thebuild-pipelinerepo is handling their versioning.
Seems like it is just a vendoring problem.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I attempted to do something similar with the same block, I ran into:
Granted I just ran
go get && go buildhowever from what I've seen floating around this seems to be more of how thebuild-pipelinerepo is handling their versioning.