WIP: Feature/multiple apps #9
Conversation
|
This pull request has been linked to Shortcut Story #21775: [Workflows] shared github workflow should support deploying n apps to n clusters. |
| @@ -44,7 +48,7 @@ jobs: | |||
| uses: rtCamp/action-slack-notify@v2 | |||
| if: failure() && (github.ref_name == 'development' || github.ref_name == 'master' || github.ref_name == 'production') | |||
| env: | |||
| SLACK_CHANNEL: taas-dev | |||
| SLACK_CHANNEL: taas-github | |||
There was a problem hiding this comment.
I think failed deploys should be kept in #taas-dev
Github channel is spammed allot by github stuff and this would easily drown
| required: true | ||
| type: string | ||
| deploy_dirs: |
There was a problem hiding this comment.
Why would we need multiple deploy dirs.
Can you gave a example of how the file structure would look with this change
There was a problem hiding this comment.
i think this will work fine too:
global service:
deploys/
base/
overlays/
euc1-testing/
euc1-staging/
euc1/
euw1/
sharded service:
deploys/
base/
overlays/
euc1-testing/
euc1-staging/
euc1-shared01/
euc1-shared02/
euw1-agents01/
There was a problem hiding this comment.
multiple deploy dirs are for multiple apps in the same cluster
deploy-app1/
base/
overlays/
euc1-testing/
deploy-app2/
base/
overlays/
euc1-testing/
|
Can you make a PR on a k8s app to show how it would look implemented (and show how to migrate if needed) |
|
[sc-21775]