concourse/resource-types

A place where the concourse resource types live.

Table of Contents

• Concourse Resource Types
  • Submitting a Resource Type
  • Where to get help

Concourse Resource Types

Welcome to the Concourse resource types repository! Here you can publish your resource type. Upon approval, it will be live in the Concourse docs site under the ‘Resource Types’ section.

On this page, you’ll find details on how to contribute a resource type to the repository. You can find instructions on building a resource type here.

Submitting a Resource Type

Resource types can be submitted directly to this repo through a fork-and-PR workflow:

1. Fork the Concourse Resource Types repo into your Github account.

2. Add a yaml file for your resource type directly in the same folder as this README.md.

   Follow the schema: [OWNER_NAME]-[RESOURCE_TYPE_NAME].yml for file name (e.g. concourse-git-resource.yml)

   ...
   /README.md
   /your-new-yaml.yml
   ...
   

3. Populate your file with the resource type name, repo url and the description of the resource type. For example:

   name: git
   repo: https://github.com/concourse/git-resource
   ## Add the full url of the image if it is not listed under dockerhub
   container_image: concourse/git-resource
   description: |
       tracks commits in a branch of a Git repository

4. Commit your work, making sure your commit has a signature certifying agreement to the DCO. For more information, see signing your work.

5. When you're ready, push your code and submit a pull request!

6. Your pull request will be reviewed by one or more maintainers, and you might receive feedback or requests for additional changes to your code.

   In order to approve a resource type, we check the following:

   • You are the primary maintainer of the resource type or affiliated to the maintaining org.
   • The repository url of the resource type is valid.
   • The container image of the resource type exits.

7. When a maintainer accepts your changes, they will merge your pull request.

Where to get help

There are two main channels that the Concourse community uses for getting help and discussing potential changes.

1. Get help in Discord in the #resource-types channel. Click here to get access.
2. Discuss new ideas in the Concourse forums.

resource-types's Issues

Call for Contributing resource types to this repository

Hey Folks,

As we move into the resource marketplace for Concourse (AKA project dutyfree), we are requesting the resource type contributors to add their resources here.

I am tagging all the contributors that were listed under the original Concourse wiki and awaiting your kind feedback.

The whole contrinution process is explained in this repo's readme. We will value any feedback around the process and/or the documentation as well.

Resource Type	Maintained By...
Slack Reading and Posting	by @jleben
Slack notifications	by @cloudfoundry-community
Github Pull Requests	by @telia-oss
GitLab Merge Requests	by @swisscom
OpenStack Swift	by @sapcc
Key Value resource	by @SWCE
Key Value resource	by @moredhel
Flowdock notifications	by @starkandwayne
Email	by @pivotal-cf
Formatted Email	by @santoshjpawar
Email with integrated MTA	by @mdomke
Bintray	by @jamiemonserrate
Perforce	by @olhtbr
BOSH Errands	by @starkandwayne
BOSH Config: cloud-config and runtime-config	by @EMC-Dojo
BOSH Release	by @dpb587
Pool Trigger	by @SFMobile
Pivotal Network (Pivnet)	by @pivotal-cf
FTP	by @aequitas
lftp, access resources via ftp, http, sftp and fish	by @openSUSE
Cloudformation	by @pivotal-cf-experimental
Generic HTTP API	by @aequitas
Hockey App	by @seadowg
Concourse Pipelines	by @robdimsdale
Twitter	by @ECSTeam
HipChat Notifications	by @cloudfoundry-community
Matrix Notifications	by @freelock
Smuggler: generic resource framework	by @redfactorlabs
GitHub Commit Status	by @dpb587
GitHub Deployment	by @ahume
AMI Updates	by @jdub
Debian/Ubuntu Sources Updates	by @jdub
Open Build Service	by @SUSE
Travis-ci	by @Orange-OpenSource
Bitbucket Notifications	by @Karunamon
Terraform	by @ljfranklin
bbl (BOSH Bootloader) state	by @cloudfoundry
Azure Blobstore	by @pivotal-cf
Rsync	by @mrsixw
Rsync: rsyncd, for local net	by @chemist
PyPI Packages	by @cf-platform-eng
Devpi Server: PyPI mirror and package server	by @mdomke
Jira Integration	by @danrspencer
Google Drive	by @jpatel-pivotal
Google Calendar	by @henrytk
pagerduty Notifications	by @FidelityInternational
Telegram	by @w32blaster
Telegram	by @carlo-colombo
Telegram	by @Cuttlerat
Google Cloud Storage	by @frodenas
Fly	by @troykinsella
Kubernetes	by @jcderr
Kubernetes	by @zlabjp
K8s-Kubernetes	by @srinivasa-vasu
Kubernetes Helm	by @linkyard
Helm Chart resource	by @linkyard
Helm Chart repository (ChartMuseum) resource	by @cathive
Vault	by @Docurated
AWS Key Management Service	by @everpeace

Please provide an optional more table-like listing of the resources.

Personally speaking I find the grid style very difficult to scan. I would love the option for a more traditional table layout.