-
Notifications
You must be signed in to change notification settings - Fork 2
Home
- Wait for the pipe to build and deploy
- Test Web site to make sure it is functioning
- Test Api to make sure it is still working
Test: https://sloth-api-test.azurewebsites.net/swagger/index.html
Prod: https://sloth-api-production.azurewebsites.net/swagger/index.html
- If everything is good in test, promote to Prod with the pipe
Hooks can call back into the team's application when the web job indicates the money has posted. Currently, only registration test has this functionality. The other teams use web jobs to call into sloth.
Go to Payment Configuration -> Key Management and click "Generate Key". Create a key of type "API Cert/Secret" and then choose "Shared Secret" on the next step. Write down the KeyID and Secret, which need to be added into sloth to allow it to access the reports.
KFS uses SFTP for scrubber upload. A public/private keypair is required to access the server. Create the keypair and send the public key to the KFS team and then input the private key into Sloth.
Creating the keypair:
ssh-keygen -t rsa
- Choose a filename and leave the password blank
- To get public key in correct format:
ssh-keygen -e -f <privatekey>
- To get private key in correct format:
ssh-keygen -p -N "" -m pem -f <privatekey>
. This changes the file in situ.
When setting up the KFS source, the Source Name and Type must match what the other application (registration for example) uses to create the transactions.
Registration Example: https://www.screencast.com/t/Vnsd84nUQ1GJ
SELECT dbo.Transactions.MerchantTrackingNumber, dbo.Teams.Name, COUNT(*) AS test FROM dbo.Transactions INNER JOIN dbo.Sources ON dbo.Transactions.SourceId = dbo.Sources.Id INNER JOIN dbo.Teams ON dbo.Sources.TeamId = dbo.Teams.Id where dbo.Teams.Name = 'Payments' GROUP BY dbo.Transactions.MerchantTrackingNumber, dbo.Teams.Name order by test asc