rainist / bento

Deliver food (env) to Travis

bento

food (env) to be delivered (via slack) to travis

Why?

• adding common set of env into every travis repository is sometimes inevitable.
• repetitive means automatable
• eliminate the needs of confirming from admin (and possibly actually them inputing for requester)
• and none of the requesters and admins need to see the senstive values any more unnecessarily

Interface

• slack

possibly more later

Target

• travis

possibly more later

Stragtegy

• Lambda like serverless function way
• providing the deployment in k8s via kubeless is first-class citizen

Components

set-env

http service which actually performs setting environments variables into travis

set-env-web

web interface to support easy operations

bento's Issues

Show which ENVs are going to set

Currently, performers have no idea which ENVs are going to set. So why not showing the list so performers can understand much better of what they are going to do.

Let's show name, rewrite, public, obscured value as a table for now.

Allow adding custom ENV in Web UI

Even though it's convenient to be able to set same predefined ENV in every desired travis repository, adding custom ENV to each repo would be even more powerful since it can get rid of the extra step of accessing travis-ci.com to set the custom ENV.

[Bug] Notify success via slack when it is not success

This code below is the problem.

bento/functions/set-env/handler.js

Lines 69 to 73 in 09c0297

	await emitResponse(res, result)
	if(slackWebhookURL) {
	await notifySuccess(rawRepo, who).catch(console.error)
	}

emitResponse should return value for success and branch to notifySuccess or notifyFail accordingly