unee-t / frontend

Meteor front end

https://case.dev.unee-t.com/

GNU Affero General Public License v3.0

9 stars 17 forks source link

Changing Secret - Procedure needs to be documented #899

Open franck-boullier opened 4 years ago

franck-boullier commented 4 years ago

The Problem:

As described in https://github.com/unee-t/frontend/pull/894#issuecomment-583918837, changing a secret across the env amongst the frontend, backend and the all the lambdas presents a lot of challenges and it would take quite some work to automate.

We need to make sure that if we have to change a secret (ex: API_ACCESS_TOKEN) this is properly documented to make sure that everything will be working as expected

kaihendry commented 4 years ago

I think the solution is to simply do a tagged release if you want to update the env variables.

I.e. travis on a tagged release does a {dev,demo,prod} deploy via https://github.com/unee-t/frontend/blob/master/deploy.sh since the script fetches all the env afresh from ssm when it's run.