PR#341: C3I: Clarify which user to use for the API key - waiverdb - Pagure.io

waiverdb

#341 C3I: Clarify which user to use for the API key

Merged 4 years ago by gnaponie. Opened 4 years ago by csomh.

csomh/waiverdb api-key-docs into master

C3I: Clarify which user to use for the API key

Hunor Csomortáni • 4 years ago

d8a272e

openshift/docs/pipeline-deployment.md

file modified

+2 -1

		`@@ -124,7 +124,8 @@`
		`#### Configure a Pagure API Key`
		`This section is not required if updating Pagure PR status is not needed.`

		`- - Go to your Pagure repository settings, and locate to the 'API Keys' section.`
		+ - Login as `factory2jenkins` to Pagure.io (gnaponie and lholecek knows the password).
lholecek commented 4 years ago Well ... so what's the password? :) How about put it in the factory2-secrets repo in other_credentials.yml?
		`+ - Go to the repository settings, and locate to the 'API Keys' section.`
		- Click on the `Create new key` button to add new API key with the following permissions:
		`- Flag a commit`
		`- Comment on a pull-request`

csomh commented 4 years ago

Signed-off-by: Hunor Csomortáni csomh@redhat.com

csomh commented 4 years ago

@gnaponie @lholecek ptal

lholecek commented on line 6 of openshift/docs/pipeline-deployment.md 4 years ago

Well ... so what's the password? :)

How about put it in the factory2-secrets repo in other_credentials.yml?

lholecek commented 4 years ago

Well ... so what's the password? :)
How about put it in the factory2-secrets repo in other_credentials.yml?

Never mind, I "know" the password now. :)

+1

gnaponie commented 4 years ago

/me and lholecek got the power.

+1 \o/

Pull-Request has been merged by gnaponie

4 years ago

Metadata

Assignee

None

Tags

No Tags

Flags

Changes Summary 1

file changed

openshift/docs/pipeline-deployment.md

Powered by Pagure 5.13.3

Documentation • File an Issue • About • SSH Hostkey/Fingerprint

© Red Hat, Inc. and others.