Week 2.3 Assignment: Implement Secret Server API

Introduction

Your task is to implement a secret server. The secret server can be used to store and share secrets using the random generated URL. But the secret can be read only a limited number of times after that it will expire and won’t be available. The secret may have TTL. After the expiration time the secret won’t be available anymore. You can find the detailed API documentation in the swagger.yaml file. We recommend to use Swagger or any other OpenAPI implementation to read the documentation.

Here is the swagger.yaml, what describes the Secret Server API

Task

Implementation: You have to implement the whole Secret Server API. You can choose the database you want to use, however it would be wise to store the data using encryption. The response can be XML or JSON too. Use a configuration file to switch between the two response type.

Requirements

• Ipmlement the API what listen and server on the endpoints what swagger.yaml describes.

Bonus

As a bonus exercises you can also...

• Use data encryption for stored data
• [] Deploy your server. There are many of free solutions to do this.
• [] Monitor number of requests and their response time.

Installation

git clone https://github.com/smapig/secret-server {GOPATH}/github.com/smapig/secret-server
cd {GOPATH}/github.com/smapig/secret-server
go install
touch .env
go run main.go

Override environment configuration

• Create .env file at root folder
• Put your configure you would like to override in your .env file with syntax YOUR_CONFIG_KEY=YOUR_CONFIG

List override configure

• PORT: Server port to serve (default is 8080).
• SECRET_KEY: Secret key to ecrypt data (default is topsecret).

Demo