-
Notifications
You must be signed in to change notification settings - Fork 0
Scripts aws deploy revision #37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: internal_executor
Are you sure you want to change the base?
Conversation
jesus-serranop
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
| @@ -1,8 +1,8 @@ | |||
| #!/bin/bash | |||
| sudo chmod 777 /home/ubuntu/projects/executor/gradlew | |||
| # sudo chmod 777 /home/ubuntu/projects/executor/gradlew | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is this change needed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I's now needed right now, that's why I commented out.
At the first time I added this line because when trying to execute a test after the deploy it causes an error of permissions since the aws agent starts the deploy as root and the support project starts the execution as ubuntu user.
Now it's changing the owner of the executor project to ubuntu in line 3 of the deploy_scripts/config_files
napoles-mk
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, minor comment.
Brief summary of the problem and the fix.
Configuration required for the codeDeploy revision.
Added Appspec file and scripts.
Task or/and GitHub covered by this fix
https://github.com/muuklabs/support/issues/677
Tests executed
NA
Answer the following questions:
Does the PR have any dependency with BE or FE? If so, specify which PR
No
In case of a dependency, could you describe what would happen if not delivered together? (eg. FE will crash, code will not compile, etc)
NA
Did you update the extension? if that’s the case did you update the extension on remote Pupp project?
NA
Did you add a new lib package (package.json)? If so, did you update the open source spreadsheet?
NA
Did you link the defect to this PR (Github only)
Yes
If you are adding a new FE view or any significant UI change, have you shared the new UI to the team already?
NA
Did you include or update the unit tests?
NA
Did you execute the npm tests ?
NA
Did you test it in both environments (dev/prod)?
NA
if you update the routes... Did you update the sample.txt ?
NA