Credential management

[sunng87]

Credential management

[liquidz]

@sunng87 Thanks for your suggestion!
My main usage is to deploy from GitHub Actions, so I was expecting the password to be stored as secrets in GitHub.

But it is certainly bad to handle plain passwords when deploying from local, so I agree to be able to use GPG as same as leiningen :)

[liquidz]

@sunng87 Just released v0.3.82. Thank you so much!
https://github.com/liquidz/build.edn/releases/tag/0.3.82

[sunng87]

Just realized the credential is set and used in upstream deps_deploy. I will create an issue there too.

[liquidz]

@sunng87 Just updated dev branch.
It is still a work in progress for now, but it should work.

In dev branch, build.edn file can have deploy-repository key.

build.edn/src/build_edn/schema.clj

Lines 35 to 40 in 658cb38

	(def ?deploy-repository
	[:map
	[:id string?]
	[:username {:optional true} string?]
	[:password {:optional true} string?]
	[:url {:optional true} string?]])

e.g.

{:deploy-repository {:id "clojars"}}

Default :id is "clojars", so if you'd like to use clojars.org, the above settings is optional.

If ~/.m2/settings-security.xml exists, build.edn will decrypt password by deps-deploy.maven-settings.
And if corresponding settings does not exists in ~/.m2/settings.xml, build.edn will refer environmental variables as before.

[sunng87]

@liquidz I confirm it works with maven encrypted password. Thank you for super fast response!