diff options
| author | Joey Hess <joeyh@joeyh.name> | 2017-11-22 15:29:36 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2017-11-22 15:29:36 -0400 |
| commit | 0d97c489c9c4cd987e4c41f4d7a1fa3189fb0e97 (patch) | |
| tree | 3996e7a3af9a33af1d065334620dd3223a50f2ab /doc | |
| parent | 57511235196176e05f9028942152a1e40461471c (diff) | |
response
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/forum/How_to_add_a_privdata_for_Gitlab_cookies/comment_1_17d2452b602a867862e688ad39f50ebe._comment | 21 |
1 files changed, 21 insertions, 0 deletions
diff --git a/doc/forum/How_to_add_a_privdata_for_Gitlab_cookies/comment_1_17d2452b602a867862e688ad39f50ebe._comment b/doc/forum/How_to_add_a_privdata_for_Gitlab_cookies/comment_1_17d2452b602a867862e688ad39f50ebe._comment new file mode 100644 index 00000000..0a10baaf --- /dev/null +++ b/doc/forum/How_to_add_a_privdata_for_Gitlab_cookies/comment_1_17d2452b602a867862e688ad39f50ebe._comment @@ -0,0 +1,21 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2017-11-22T19:14:32Z" + content=""" +Privdata uses the combination of the Context and the PrivDataField +to identify the piece of private data to use. So, you don't +need to add a new constructor to PrivDataField as long as you can +find a context that is sufficiently specific for your needs. +The gitlab url (without the password) would make a fine context. + +So, I'd suggest something like `withPrivData (Password "thegitlaburl") (Context "thegitlaburl")` + +See the example in the haddock for withPrivData to for how to use that. + +(The only possible problem with that is you're claiming it's a password +when it's really an API key. Propellor won't care, but it you wanted +to store the actual gitlab password too, then you'd need to use a different +username. It may make sense to add a new constructor to PrivDataField for +an API key or something like that.) +"""]] |