Edit Config and Upload Icons
Proposed Ways to Hand-off Config Editing and Icon Upload to the Security team.
Brainstorm/Plan ways the security team can take owner ship of the deployment of new icons and updating Access-Boston’s config file. 2 Step Deploy Plan: The Security will update the config files in S3 via SFTP and the Digital team will restart the Applications.
The first is giving them access to the S3 bucket directory containing the App config `.yml` file via SFTP. Once they make the changes they will create create an ‘Issue’ ticket in our Github project for the Digital team to schedule a deploy to the service.
The second part is triggering a deployment of their applications on AWS's ECS. Depending on the details of the change, we would go corresponding instance in either "AppsProdDeploy" or “AppStagingDeploy” and 'force a new deploy’ by using the ‘Update” the instance button.
Dedicated Git Repository Deploy Plan: The Security team commits a “Pull Request” to a private repository, whose build process will trigger a build/deploy request through Travis-CI and restart the corresponding App containers.
Setup a private repository the Security team can update.
Replicate part of the deploy process (travis, slack, etc) the mono-repo uses update the Apps in AWS
SFTP/S3 and LAMBDA Deploy
Give the Security team's SFTP Access to the S3 bucket path containing the App config files.
Create a Lambda function that gets triggered when the contents of the S3 bucket are updated
Connect the corresponding Access-Boston environment using ECS CLI and ‘force new deploy’ that application.
Resources:
Last updated