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

Allow relative paths #5

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

endemics
Copy link
Contributor

This PR builds on top #4 and allows to manage multiple paths/repositories with a single sign-package lambda.

Gildas Le Nadan added 5 commits February 17, 2020 13:55
If set, its value will be used to replace the path of the unsigned RPM
(the RPM name will keep the same). This allows to upload the signed
RPM in the same bucket as the unsigned RPM.
…allows to use the bucket from the event directly
…allows to use the bucket from the event directly
…BDA_S3_BASE_PATH

along with LAMBDA_S3_TARGET_PATH.
This allows to manage unsigned RPMs for multiple target repositories, e.g.
with LAMBDA_S3_BASE_PATH set to /unsigned/, and
LAMBDA_S3_TARGET_PATH set to /incoming/,
if you copy an unsigned package to /unsigned/<repo1>/package-1.2.3-1.el7.centos.x86_64.rpm,
the signed package will be copied to /incoming/<repo1>/package-1.2.3-1.el7.centos.x86_64.rpm,
while /unsigned/<repo2>/package-1.3.1-1.el7.centos.x86_64.rpm will be copied to
/incoming/<repo2>/package-1.3.1-1.el7.centos.x86_64.rpm.
Replace <repo1> by "production" and <repo2> by "staging" and you should understand
the rationale :)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant