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
Copy file name to clipboardExpand all lines: docs/credentials.md
+2-5Lines changed: 2 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,9 +1,8 @@
1
1
# Creating cloud credentials
2
2
3
-
4
3
## S3 data server
5
4
6
-
- In general, the credentials you need from your S3 account are the `AccessKey` and the `SecretKey`. These are akin to user names and passwords.
5
+
- In general, the credentials you need from your S3 account are the `AccessKey` and the `SecretKey`. These are akin to user names and passwords.
7
6
- How you obtain these credentials will depend on your provider (e.g. AWS S3, MINIO, OSN - see below)
8
7
- Paste the access key and the secret key as _Repository secrets_ in your _FaaSr-workflow_ as per the instructions in the [workflow repo] documentation
9
8
@@ -13,6 +12,7 @@ If you don't already have one, you need to generate a GitHub Personal Access Tok
13
12
[Details on how to create a PAT are available here](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens#creating-a-personal-access-token-classic)
14
13
15
14
In summary:
15
+
16
16
- In the upper-right corner of any page, click your profile photo, then click Settings.
17
17
- In the left sidebar, click Developer settings.
18
18
- In the left sidebar, click Personal access tokens.
@@ -29,14 +29,12 @@ In summary:
29
29
- Paste the access key and the secret key under the names `AWS_AccessKey` and `AWS_SecretKey`, respectively, as _Repository secrets_ in your _FaaSr-workflow_ as per the instructions in the [workflow repo] documentation
30
30
- Paste your ARN as `AWS_ARN` as _Repository secrets_ in your _FaaSr-workflow_
31
31
32
-
33
32
## OpenWhisk
34
33
35
34
- You need an API key from your provider to configure for use in FaaSr
36
35
- How you obtain this will depend on your cloud provider.
37
36
- Paste the API key under the name `OW_APIkey` as a _Repository secret_ in your _FaaSr-workflow_ as per the instructions in the [workflow repo] documentation
38
37
39
-
40
38
## Google Cloud Platform
41
39
42
40
- You need a private secret key to use Google Cloud Platform (GCP) with FaaSr
@@ -54,5 +52,4 @@ TBD
54
52
- For researchers in the US, you can [request an allocation](https://www.openstoragenetwork.org/get-involved/get-an-allocation/) of 10+ TB S3 storage.
55
53
- If your request is approved, you will be assigned one S3 bucket, and can then copy the access and secret keys provided to you for use with FaaSr
Copy file name to clipboardExpand all lines: docs/tutorial.md
+19-7Lines changed: 19 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,10 @@
1
1
# Tutorial
2
2
3
-
This document guides you through a simple tutorial that uses GitHub Actions and a free S3 data store (Minio Play). The pre-requisite for this tutorial is a GitHub account.
3
+
This document guides you through a simple tutorial that uses GitHub Actions and a free S3 data store (Minio Play).
4
+
5
+
## Prerequisites
6
+
7
+
For this tutorial, all you need is a GitHub account. It is also recommended that your refer to the [Setting up the FaaSr-workflow repo](./workflow_repo.md) documentation for details about the FaaSr-workflow repository.
4
8
5
9
## Configure your FaaSr-workflow repository
6
10
@@ -12,13 +16,16 @@ This is a one-time step you go through to set up your [workflow repository] to h
12
16
13
17
## Configure your GitHub PAT
14
18
15
-
You need a personal access token in your repository secrets to run this tutorial.
19
+
You need a personal access token in your repository secrets to run this tutorial.
16
20
17
-
Follow the steps outlined in the [credentials] documentation to obtain your PAT. Copy this PAT so you can paste it as a secret in the next step
21
+
Follow the steps outlined in the [GitHub Actions credentials] documentation to obtain your PAT. Copy this PAT so you can paste it as a secret in the next step
18
22
19
23
## Configure your repository secrets
20
24
21
-
Before you can register and invoke workflows, you need to create secrets storing credentials for the cloud providers you will use. The following assumes that you already have obtained [cloud credentials] for those.
25
+
Before you can register and invoke workflows, you need to create secrets storing credentials for the cloud providers you will use.
26
+
27
+
!!! note "Guest S3 Credentials"
28
+
Note that for this tutorial we are using guest credentials for a free S3 data store offered by MinIO. In practice, you will use your own credentials (see the [credentials](./credentials.md) documentation for more information).
22
29
23
30
- In the _FaaSr-workflow_ repo you just forked, click on the _Settings_ tab (top of the page, to the right)
24
31
- Scroll down; on the left pane, click on the pull-down _Secrets and variables_ and select _Actions_
@@ -56,7 +63,13 @@ The tutorial.json file is available in the FaaSr-Functions repository; you will
56
63
57
64
## Invoke the workflow
58
65
59
-
- After register, you can [invoke the workflow]
66
+
!!! question "What code am I running?"
67
+
For this tutorial, function code is sourced from the [FaaSr-Functions](https://github.com/FaaSr/FaaSr-Functions) repository. See [Creating Functions](./functions.md) for more information on how FaaSr runs function code.
68
+
69
+
!!! warning
70
+
Run only [workflows and code that you trust](./security.md#only-reuse-workflowsfunctions-that-you-trust) with FaaSr. Always check that you trust the provenance of the workflow or code that you are running.
71
+
72
+
- After register, you can [invoke the workflow]
60
73
- Click on _Actions_
61
74
- Click on `(FAASR INVOKE)` (left)
62
75
- Click on the `Run workflow` drop-down; enter `tutorial.json` and click on `Run workflow`
@@ -83,9 +96,8 @@ The tutorial.json workflow is based on two R functions (start, compute_sum). Ano
0 commit comments