Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reorganize Catalog based on Catalog Organization Proposal #389

Merged
merged 70 commits into from
Jul 10, 2020
Merged

Reorganize Catalog based on Catalog Organization Proposal #389

merged 70 commits into from
Jul 10, 2020

Conversation

PuneetPunamiya
Copy link
Member

@PuneetPunamiya PuneetPunamiya commented Jun 24, 2020

Changes

  • NOTE: This patch covers the first part of the issue where it modifies all the tasks and moves the tasks which don't need to be split to the task directory. The task which has to be split and moved to the task directory will be added in the next pr (Split tasks based on Catalog Organization Proposal #401) to make review easier
  1. Each resource follows the following structure
    ./task/         👈 the kind of the resource 
      /argocd       👈 definition file must have same name
        /OWNERS     👈 owners of this ressource
        /README.md  👈 fallback README if version is missing README
        /0.1
          /README.md     👈 [optional] since there can be a fallback
          /argocd.yaml   👈 the file name must be resource name
          /samples/deploy-to-k8s.yaml
        /0.2/...
      /golang-build
        /0.1
          /README.md
          /golang-build.yaml
          /samples/golang-build.yaml
  1. Resource YAML file includes following changes
  • Labels include the version of the resource.
  • Annotations include minimum pipeline version supported by the resource,
    tags associated with the resource and displayName of the resource
  
labels:
  app.kubernetes.io/version: "0.1"            👈 version of the resource
  
annotations:
  tekton.dev/pipelines.minVersion: "0.12.1"   👈 will work from x version  of pipeline
  tekton.dev/tags: "ansible, cli"                        👈 Comma separated list of tags 
  tekton.dev/displayName: "Ansible Tower Cli"    
  
spec:
description: |-
  ansible-tower-cli task simplifies 
  workflow, jobs, manage users...   👈 # Summary
  
  Ansible Tower (formerly ‘AWX’) is a ...

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

See the contribution guide
for more details.

@tekton-robot tekton-robot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jun 24, 2020
@tekton-robot tekton-robot added size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. labels Jun 24, 2020
task/makisu/0.1/makisu.yaml Outdated Show resolved Hide resolved
makisu/makisu.yaml Outdated Show resolved Hide resolved
@tekton-robot tekton-robot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Jun 25, 2020
@sthaha
Copy link
Member

sthaha commented Jun 26, 2020

Please note Hub has been deployed to https://ui-tekton-hub.apps.openshift-web.p0s5.p1.openshiftapps.com/ based on this PR. I will force a resync of Hub tasks as more tasks are added to this PR.

@tekton-robot tekton-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Jun 30, 2020
@vdemeester
Copy link
Member

/retest

@tekton-robot tekton-robot added size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. and removed size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Jun 30, 2020
github/set_status.yaml Outdated Show resolved Hide resolved
github/close_issue.yaml Outdated Show resolved Hide resolved
gcs/gcs-upload.yaml Outdated Show resolved Hide resolved
@tekton-robot tekton-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 6, 2020
@PuneetPunamiya
Copy link
Member Author

/retest

gcs/gcs-create-bucket.yaml Outdated Show resolved Hide resolved
gcs/gcs-create-bucket.yaml Outdated Show resolved Hide resolved
gcs/gcs-delete-bucket.yaml Outdated Show resolved Hide resolved
gcs/gcs-generic.yaml Outdated Show resolved Hide resolved
gcs/gcs-upload.yaml Outdated Show resolved Hide resolved
git/git-batch-merge.yaml Outdated Show resolved Hide resolved
git/git-cli.yaml Outdated Show resolved Hide resolved
@tekton-robot tekton-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 7, 2020
pratap0007 and others added 4 commits July 10, 2020 14:55
…g proposal

**NOTE: This only modifies the content of the yaml, changing
        the location of the file will be done in a different
        commit to make review easier

Changes include:
  - adds version label
  - adds a minimum pipeline versions supported by the task
  - adds tags for task
  - adds display name for task
  - modified description to add a summary

Issue: #386

Signed-off-by: Shiv Verma <[email protected]>
…roposal

**NOTE: This only modifies the content of the yaml, changing
        the location of the file will be done in a different
        commit to make review easier

Changes include:
  - adds version label
  - adds a minimum pipeline versions supported by the task
  - adds tags for task
  - adds display name for task
  - modified description to add a summary

Issue: #386

Signed-off-by: Puneet Punamiya <[email protected]>
according to the new reorg proposal

**NOTE: This only modifies the content of the yaml, changing
        the location of the file will be done in a different
        commit to make review easier

Changes include:
  - adds version label
  - adds a minimum pipeline versions supported by the task
  - adds tags for task
  - modified description to add a summary

Issue: #386

Signed-off-by: Puneet Punamiya <[email protected]>
according to the new reorg proposal

**NOTE: This only modifies the content of the yaml, changing
        the location of the file will be done in a different
        commit to make review easier

Changes include:
  - adds version label
  - adds a minimum pipeline versions supported by the task
  - adds tags for task
  - modified description to add a summary

Issue: #386

Signed-off-by: Puneet Punamiya <[email protected]>
@bobcatfish
Copy link
Contributor

/lgtm
/approve

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Jul 10, 2020
@tekton-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bobcatfish

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@bobcatfish
Copy link
Contributor

Hey @PuneetPunamiya I'm surprised to see the OWNERS file in the versioned directories, can we move them one level up?

image

I'm guessing we'll have folks owning a Task across all versions, probably not a different set for each version (tho folks could add that if they wanted to)

@sthaha
Copy link
Member

sthaha commented Jul 24, 2020

@bobcatfish Good catch! We completely missed it!

@sthaha
Copy link
Member

sthaha commented Jul 24, 2020

@PuneetPunamiya @bobcatfish Hopefully this fixes it - #443

@bobcatfish
Copy link
Contributor

np @sthaha - i missed it too!! I only noticed it when I was adding my own OWNERS file :D

@PuneetPunamiya PuneetPunamiya mentioned this pull request Jul 27, 2020
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants