-
Notifications
You must be signed in to change notification settings - Fork 189
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
Adding GitHub token into all env files #2863
Conversation
tools/autodeployment/deploy.sh
Outdated
@@ -34,7 +34,7 @@ fi | |||
echo "GIT_COMMIT=$2" >> $ENV_FILE | |||
|
|||
echo "Building $ENV Container" | |||
docker-compose --env-file $ENV_FILE --project-name=$ENV build | |||
GITHUB_TOKEN={$GITHUB_TOKEN} docker-compose --env-file $ENV_FILE --project-name=$ENV build |
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.
is there anyway we can see the value of GITHUB_TOKEN
here?
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.
It would have to be set outside the script. @manekenpix can speak to what's possible in the env of the build machines.
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 think it should be set in here so the autodeployment
server can see it, and then passed into the script.
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.
Oh, you already did, the only step left is passing it to the script here
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.
Not sure if it belongs in this PR, but we could also document this change in our docs
I made some changes. Still not sure how to test this out? |
@TDDR Ping me on slack for testing your PR on |
I somehow deleted the previous two commits I had originally shared when I did a |
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 👍
We'll have to update the docs to reflect these changes, here or in a different PR.
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.
Nice work on this. I know it wasn't easy to test. I appreciate you all sticking with it and getting it done.
@TDDR, let's rebase this and ping the Sheriffs after |
a789d2d
Nice |
Issue This PR Addresses
Fixes #2799
Description
This is my attempt at getting the ball rolling for issue #2799.
From what I can tell, adding the
GITHUB_TOKEN=
to theenv.example
will auto-populate the GitHub token.I then expose that token in the Docker-compose by adding it to the top level
environment
The thing I am least certain of is my attempt to use the token in the
deploy.sh
file. I am fairly sure that is wrong, but I'm not sure what exactly needs to happen, or how to test it.Steps to test the PR
@manekenpix had to take down staging in order to test this.
Checklist