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

move to using our own / forked versions of concourse resources #1806

Open
gumaerc opened this issue May 15, 2023 · 0 comments
Open

move to using our own / forked versions of concourse resources #1806

gumaerc opened this issue May 15, 2023 · 0 comments
Labels
enhancement New feature or request tech debt

Comments

@gumaerc
Copy link
Contributor

gumaerc commented May 15, 2023

Currently, we are using a number of 3rd party Concourse resources:

  • jgriff/http-resource
  • ghcr.io/cludden/concourse-keyval-resource
  • governmentpaas/s3-resource
  • arbourd/concourse-slack-alert-resource

We should, at a bare minimum, fork these repositories and point to those forks in our pipelines. These repositories do not have a lot of stars, are controlled by 3rd parties and could be removed at any point. By forking them, the repository will only go away if we remove it and we have greater control over the code.

@gumaerc gumaerc added enhancement New feature or request tech debt labels May 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request tech debt
Projects
None yet
Development

No branches or pull requests

1 participant