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

Support: Aptly API Publishing and batch options #931

Open
cloudy-dayzz opened this issue Nov 25, 2020 · 0 comments
Open

Support: Aptly API Publishing and batch options #931

cloudy-dayzz opened this issue Nov 25, 2020 · 0 comments

Comments

@cloudy-dayzz
Copy link

cloudy-dayzz commented Nov 25, 2020

Hello!
I am struggling to publish to s3 from aptly API. I believe this is due to incorrect signingOptions in my json.

This is when calling the API from a remote location

My setup is as below.

A local repo named "test", which publishes to an s3 repository.

I am able to successfully add files to the repository, doing the following :

curl -sSF file=@${DEB} ${APTLY_BASE_URL}/api/files/${CI_COMMIT_TAG};
curl -sSX POST ${APTLY_BASE_URL}/api/repos/test/file/${CI_COMMIT_TAG};
curl -X POST -H 'Content-Type: application/json' --data @../templates/upload_to_aptly.json ${APTLY_BASE_URL}/api/publish

My JSON looks like so (Sanitized):

    "Sources": [
        {"Name": "test"}
        ],
        "Architectures": ["amd64"],
        "Distribution": "test",
        "Storage": "s3",
        "Signing": {
        "Batch": "true",
        "PassPhrase": "XXXXX"
        }
    }

I receive the following error message:
{error":"unable to publish: unable to detached sign file: exit status 2"}

What I believe is happening is that the publish API is not respecting my Signing options, as if I keep watch on the aptly server, it brings up the prompt to enter my passphrase.

Please can you let me know where i'm going wrong?!

Thanks.

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

No branches or pull requests

1 participant