Bring back deployment

[humblelistener]

There were a few questions about deployment enablement

1. Would this bootstrap repo continuously deploy? or
2. Would it enable people to set up continuous deployment?

Of course, option 1 encompasses the option 2.

The question is, whether option 2 can be achieved without going through 1, what are the merits & demerits.

I am kind of looking at serverless YAML file for example where a hell a lot of things are comments, though it enables us pretty quickly.

On the other end, why not just deploy it if that is alright.

No right or wrong here, I guess.

[jimmyp]

After the last time we worked on this attempting to achieve 1 we got most of the way there. We have a cluster in the PageUp account in DC0 called Microservice-Bootstrap-Team but it appears the travis build no longer deploys there.

[antonfelich]

Curious as to where you guys got with this. Having finally gotten our infrastructure up and microservice running I'm sure we will have a few pull requests for everybody else to enjoy.

[jimmyp]

My opinion is we need CI and CD on this repo so we can ensure we can easily accept PRs as you suggest.

However we have not discussed it any further than what you see here ;)

[humblelistener]

What have you got? Could you hold us and have a quick conversation @antonfelich ?

[humblelistener]

There are two stories

1. Enabling the consumers of micro service bootstrap to get up and running with CD
2. Enabling custodians to be confident about the state of code base.

[jimmyp]

I will get around to having this conversation eventually