-
Notifications
You must be signed in to change notification settings - Fork 70
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
Issue617 refactor service #622
Conversation
Nice to see you're working on this @dhblum! Thanks a lot for the implementation and requesting review. I'll do so asap, hopefully by the end of this week. |
|
||
# Job queue configuration | ||
BOPTEST_JOB_QUEUE_URL=http://goaws:4100/queue/local-queue1 | ||
AWS_ACCESS_KEY_ID=xxxxxxxxxxxxxxxxxxxx |
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'd suggest replacing the secrets with environment variables so we can readily use it. Something like:
AWS_ACCESS_KEY_ID=&AWS_ACCESS_KEY_ID
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.
@kbenne Thoughts?
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.
Looking good to me @dhblum! just added a couple of small suggestions.
Thank you @javiarrobas! I'll take a look at your comments/suggestions, also with @kbenne, who plans to also see if he can replicate the migration but in a way to maintain the Service git history (in this PR I just simply moved files from that repo into this one). |
Co-authored-by: Javier <javier.arroyo@kuleuven.be>
…roject1-boptest into issue617_refactorService
Co-authored-by: Javier <javier.arroyo@kuleuven.be>
…roject1-boptest into issue617_refactorService
Closing, continuing in #652. |
This is a proposal for #617. So far, it:
api.py
docker-compose.yml
and other Dockerfiles to work with the new directly structure.See #617 for remaining todos, especially documentation/readme updates.
@kbenne @javiarrobas Care to provide initial review?