You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In general credentials files should be structured as CSV, e.g., credentials.csv:
KEY1,VALUE1
KEY2,VALUE2
...
or as JSON, e.g., credentials.json
{
"KEY1" : "VALUE1",
"KEY2" : "VALUE2",
...
}
where the key provided depends on the credential implementation in the pipeline, e.g. username,MYNAME, password,MYPWD, etc. For example, the weather pipeline needs APIKEY and EMAIL. These should be delivered as environment variables exported to the shell that runs openfido.sh, e.g., export OPENFIDO_SECRET_APIKEY="MYAPIKEY" and export OPENFIDO_SECRET_EMAIL="my.email@example.com" so they can be used in the script.
The text was updated successfully, but these errors were encountered:
Some pipelines require credential to function. There is no mechanism in either CLI and openfido-client to manage those credentials locally.
Recommend the following:
openfido credential PRODUCT {add,delete} FILENAME
.Upload credentials
to theSettings
dialog. Dialog layout:In general credentials files should be structured as CSV, e.g.,
credentials.csv
:or as JSON, e.g.,
credentials.json
where the key provided depends on the credential implementation in the pipeline, e.g.
username,MYNAME
,password,MYPWD
, etc. For example, theweather
pipeline needsAPIKEY
andEMAIL
. These should be delivered as environment variables exported to the shell that runsopenfido.sh
, e.g.,export OPENFIDO_SECRET_APIKEY="MYAPIKEY"
andexport OPENFIDO_SECRET_EMAIL="my.email@example.com"
so they can be used in the script.The text was updated successfully, but these errors were encountered: