Call for Contributing resource types to this repository

[YoussB]

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

[YoussB]

turns out that there is a limit on number of people that can be tagged in an issue, here are the rest:

Resource Type	Maintained By...
Marathon	by @ckaznocha
RSS	by @suhlig
Maven Resource	by @nulldriver
cURL File Resource	by @pivotalservices
Pivnet Resource (rsamban)	by @rsamban
Cloud Foundry Events	by @mevansam
Apache Directory Index	by @mastertinner
Cloud Foundry CLI Resource	by @nulldriver
Counter	by @jinlee
Capistrano	by @SHyx0rmZ
aptly CLI	by @SHyx0rmZ
Prometheus Alertmanager	by @frodenas
Git Bitbucket Pull Request Resource	by @zarplata
Bitbucket Pull Request Resource	by @halter-corp
NPM Cache Resource	by @ymedlop
Gerrit Resource	by @google
Repo Resource	by @google
Trigger jobs using Slack	by @ahelal
Hashicorp Releases	by @starkandwayne
Pushover notifications	by @redfactorlabs
SonarQube static code analysis	by @cathive
SonarQube Notifier	by @elgohr
Blackduck	by @elgohr
Metadata resource	by @SWCE
Spinnaker Resource	by @pivotal-cf
New Relic Deploy Resource	by @crstamps2
Artifactory Resource	by @spring-io
Artifactory Resource	by @emerald-squad
CF Zero Downtime Resource	by @emerald-squad
CF Flyway Resource	by @emerald-squad
FiaaS Resource	by @leboncoin
IRC notifications	by @flavorjones
PhraseApp Trigger	by @tenjaa
Debian/Ubuntu archive uploads	by @seveas
Launchpad PPA packages	by @seveas
Fedora COPR packages	by @seveas
Google Hangouts Notification Resource	by @CloudInn
Slack build alerts	by @arbourd
Spring Initializr Resource	by @jghiloni
HTTP Resource	by @aequitas
Android SDK Resource	by @xaethos
DigitalOcean Worker Provision Resource	by @CloudInn
Knative Service Resource	by @jchesterpivotal
Sentry Releases Resource	by @rubenv
Gate Resource	by @meshcloud
Packer	by @Snapkitchen
Github Webhook Resource	by @homedepot
Ofcourse Resource Generator	by @cloudboss
HTTP PUT Resource	by @lorands
Serverspec Resource	by @opicaud
Ansible Playbook	by @troykinsella
Artifactory Deb	by @troykinsella
Generic Artifactory	by @troykinsella
Docker Compose	by @troykinsella
RubyGems	by @troykinsella
Medium Resource	by @cappyzawa
GitHub List Repos	by @ari-becker
Slack Notifier	by @mockersf
Semver Config Resource	by @brightzheng100
Deploygate Resource	by @YuukiARIA
Romver Resource	by @cappyzawa
RocketChat Notification Resource	by @michaellihs
PCF Ops Manager Installations	by @pjk25
aliyun-oss	by @gugegev5
Maven Stage	by @lorands

[YoussB]

turns out that there is a limit on number of people that can be tagged in an issue, here are the rest:

Resource Type	Maintained By...
Marathon	by @ckaznocha
RSS	by @suhlig
Maven Resource	by @nulldriver
cURL File Resource	by @pivotalservices
Pivnet Resource (rsamban)	by @rsamban
Cloud Foundry Events	by @mevansam
Apache Directory Index	by @mastertinner
Cloud Foundry CLI Resource	by @nulldriver
Counter	by @jinlee
Capistrano	by @SHyx0rmZ
aptly CLI	by @SHyx0rmZ
Prometheus Alertmanager	by @frodenas
Git Bitbucket Pull Request Resource	by @zarplata
Bitbucket Pull Request Resource	by @halter-corp
NPM Cache Resource	by @ymedlop
Gerrit Resource	by @google
Repo Resource	by @google
Trigger jobs using Slack	by @ahelal
Hashicorp Releases	by @starkandwayne
Pushover notifications	by @redfactorlabs
SonarQube static code analysis	by @cathive
SonarQube Notifier	by @elgohr
Blackduck	by @elgohr
Metadata resource	by @SWCE
Spinnaker Resource	by @pivotal-cf
New Relic Deploy Resource	by @crstamps2
Artifactory Resource	by @spring-io
Artifactory Resource	by @emerald-squad
CF Zero Downtime Resource	by @emerald-squad
CF Flyway Resource	by @emerald-squad
FiaaS Resource	by @leboncoin
IRC notifications	by @flavorjones
PhraseApp Trigger	by @tenjaa
Debian/Ubuntu archive uploads	by @seveas
Launchpad PPA packages	by @seveas
Fedora COPR packages	by @seveas
Google Hangouts Notification Resource	by @CloudInn
Slack build alerts	by @arbourd
Spring Initializr Resource	by @jghiloni
HTTP Resource	by @aequitas
Android SDK Resource	by @xaethos
DigitalOcean Worker Provision Resource	by @CloudInn
Knative Service Resource	by @jchesterpivotal
Sentry Releases Resource	by @rubenv
Gate Resource	by @meshcloud
Packer	by @Snapkitchen
Github Webhook Resource	by @homedepot
Ofcourse Resource Generator	by @cloudboss
HTTP PUT Resource	by @lorands
Serverspec Resource	by @opicaud
Ansible Playbook	by @troykinsella
Artifactory Deb	by @troykinsella
Generic Artifactory	by @troykinsella
Docker Compose	by @troykinsella
RubyGems	by @troykinsella
Medium Resource	by @cappyzawa
GitHub List Repos	by @ari-becker
Slack Notifier	by @mockersf
Semver Config Resource	by @brightzheng100
Deploygate Resource	by @YuukiARIA
Romver Resource	by @cappyzawa
RocketChat Notification Resource	by @michaellihs
PCF Ops Manager Installations	by @pjk25
aliyun-oss	by @gugegev5
Maven Stage	by @lorands

[YoussB]

part 3:

Resource Type	Maintained By...
weblate wlc commands	by @cioplenu
HipChat Notification Resource	by @jgriff

[ari-becker]

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.

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

Hi, my name is @ari-becker and I have a hyphen in my GitHub username :) I'm guessing that the hyphen in your file name schema isn't meant to be a formal separator between owner name and resource type name?

Get help in Discord in the #resource-types channel

Which is currently archived?

[YoussB]

Hey @ari-becker,

greatly appreciating your feedback!

• About the handle, I was intending to use hyphen as a separator between the resource type owner and the resource type name. There should be no problem about having a hyphen in the owner's name atm since this will only be currently used for tidying up the repo. We care more about the contents.

• we've just un-archived the channel, thanks for the catch.

[brightzheng100]

I've sent the PR #8, thanks.

[seadowg]

I was about to deprecate my resource as https://www.hockeyapp.net has shut down. Won't run through the process and feel free to delete any references to it!

[seveas]

Hi @YoussB,

The three resource types that have my handle on them are up for adoption. I'm afraid I never could get concourse running stable enough (which is more a statement about the (lack of) effort I put into it than about Concourse 😄) and have abandoned it in favor of GitHub actions these days.

[ari-becker]

Hey @ari-becker,

greatly appreciating your feedback!

* About the handle, I was intending to use hyphen as a separator between the resource type owner and the resource type name. There should be no problem about having a hyphen in the owner's name atm since this will only be currently used for tidying up the repo. We care more about the contents.

* we've just un-archived the channel, thanks for the catch.

Cool, I've opened #16 , thanks

[Karunamon]

Please repoint Bitbucket Notifications to the version owned by @SHyx0rmZ. Mine is very, very deprecated and they've basically taken it over.

[YoussB]

@SHyx0rmZ would you mind creating a PR with your resource against this repo?

[tremblaysimon]

@YoussB I don't know how it works, but I think some organization listed here will not receive properly the notifications (since the repo owner is an organization and not a person).

Hopefully people will see the blog post on concourse ci web site a few days ago and will do the changes!

[YoussB]

@tremblaysimon, I agree.
We're trying to announce the website in all the possible ways.
I hope we can get all the owners to submit their resource types. I will think about the resource types with org owners, thanks for that.