Use pre-generated RSA keys for signing packages #3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Keys are stored as Repository secrets within Drone.
An environment statement similar to the below would need to be added to the build step of the aports .drone.yml:
The secret within the drone console would be named
pkg_sign_key
and would contain the multiline RSA key you want to use such as from ~/.abuild/.rsaThis would allow adding a step to upload the package post build such as to an AWS S3 container or via scp to a filestore so it can be used on your own systems that container the corressponding public key.
If the required configuraion doesnt exist it will revert to previous behaviour and auto gen keys on build.