Skip to content

Commit

Permalink
Add to readme
Browse files Browse the repository at this point in the history
  • Loading branch information
jgreben committed Nov 7, 2023
1 parent 5a8fa35 commit 5821ba2
Show file tree
Hide file tree
Showing 2 changed files with 23 additions and 5 deletions.
3 changes: 2 additions & 1 deletion .gitignore
Original file line number Diff line number Diff line change
@@ -1,4 +1,5 @@
/config/settings/dev.yml
/config/settings/prod.yml
/log/*
*.csv
*.csv
secret.yaml
25 changes: 21 additions & 4 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,17 +22,33 @@ integration with the CyberSource REST APIs through the [CyberSource Ruby SDK](ht
$ SLEEP=0 rspec
```

## Create Persistent Volume
```
kubectl -n ${namespace} apply -f pv-volume.yaml
```

## Setting the API credentials for an API request

Configure the `MERCHANT_ID_KEY` and `MERCHANT_SECRET_KEY` variables in the environment The variables for `STAGE`, `APP_PASSWORD` (for folio) and `APP_USERNAME` are configured using the `db-connect-modules` folio secret.
Configure the `MERCHANT_KEY_ID` and `MERCHANT_SECRET_KEY` variables in the environment The variables for `STAGE`, `APP_PASSWORD` (for folio) and `APP_USERNAME` are configured using the `db-connect-modules` folio secret.

Obtain the `merchantsecretKey`` and `merchantKeyId`` from the CyberSource Business Center.
Obtain the `merchantsecretKey` and `merchantKeyId` from the CyberSource Business Center.
You will need permissions from [email protected] to access the CyberSource Business Center
with the option to generate security keys.

## Create Persistent Volume
### Create secret with the Cybersource credentials
```
kubectl -n ${namespace} apply -f pv-volume.yaml
apiVersion: v1
kind: Secret
metadata:
name: cybersource
type: Opaque
data:
MERCHANT_KEY_ID: base64 encoded accessKey
MERCHANT_SECRET_KEY: base64 encoded secretKey
```
Then:
```
kubectl -n ${namespace} apply -f secret.yaml
```

### Create secret with sendmail config
Expand All @@ -52,6 +68,7 @@ kubectl -n ${namespace} apply -f debug.yaml

Give sendmail a couple of minutes to restart before checking the /home/harvester/harvestlog directory.


## Switching between the sandbox environment and the production environment
CyberSource maintains a complete sandbox environment for testing and development purposes. This sandbox environment is an exact
duplicate of our production environment with the transaction authorization and settlement process simulated. By default, this sample code is
Expand Down

0 comments on commit 5821ba2

Please sign in to comment.