-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
ci: Move global credentials to web configuration #55304
Conversation
(rust_highfive has picked a reviewer for you, use r? to override) |
ci: Move global credentials to web configuration This commit moves a number of our encrypted credentials stored in configuration files in this repository to env vars on the web UI. This will hopefully make it easier to rotate credentials in the future as well as quickly change them if the need arises. (quicker than landing a PR that is). This also updates the travis deployment process to always use the `aws` command line tool which we're already installing on Linux and should enable us to avoid all `dpl` gem issues as well as have greater control over what's going where.
.travis.yml
Outdated
@@ -21,12 +36,14 @@ matrix: | |||
|
|||
- env: IMAGE=dist-x86_64-linux DEPLOY=1 | |||
if: branch = try OR branch = auto | |||
after_success: *DEPLOY |
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.
🤔 Could we put that &DEPLOY
reference into the global after_success
section (which is configured to do nothing if $DEPLOY
and $DEPLOY_ALT
are undefined), so we don't need to add these dozen lines inside the matrix:
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.
Sure thing, sounds reasonable to me!
☀️ Test successful - status-travis |
This commit moves a number of our encrypted credentials stored in configuration files in this repository to env vars on the web UI. This will hopefully make it easier to rotate credentials in the future as well as quickly change them if the need arises. (quicker than landing a PR that is). This also updates the travis deployment process to always use the `aws` command line tool which we're already installing on Linux and should enable us to avoid all `dpl` gem issues as well as have greater control over what's going where.
52f02da
to
3c25f80
Compare
Ok try builds look good! Appears that files were indeed successfully uploaded |
@bors r+ |
📌 Commit 3c25f80 has been approved by |
@bors r- Failed in #55433 (comment)
|
I've asked a question to see whether this way of configuration actually should work, and will reevaluate based on the answer |
@bors: r=kennytm Ok I think I may have messed up the keys. In any case I wouldn't recommend rolling this up |
📌 Commit 3c25f80 has been approved by |
ci: Move global credentials to web configuration This commit moves a number of our encrypted credentials stored in configuration files in this repository to env vars on the web UI. This will hopefully make it easier to rotate credentials in the future as well as quickly change them if the need arises. (quicker than landing a PR that is). This also updates the travis deployment process to always use the `aws` command line tool which we're already installing on Linux and should enable us to avoid all `dpl` gem issues as well as have greater control over what's going where.
💔 Test failed - status-appveyor |
@bors: retry 3 hr time limit |
ci: Move global credentials to web configuration This commit moves a number of our encrypted credentials stored in configuration files in this repository to env vars on the web UI. This will hopefully make it easier to rotate credentials in the future as well as quickly change them if the need arises. (quicker than landing a PR that is). This also updates the travis deployment process to always use the `aws` command line tool which we're already installing on Linux and should enable us to avoid all `dpl` gem issues as well as have greater control over what's going where.
☀️ Test successful - status-appveyor, status-travis |
This commit moves a number of our encrypted credentials stored in
configuration files in this repository to env vars on the web UI. This
will hopefully make it easier to rotate credentials in the future as
well as quickly change them if the need arises. (quicker than landing a
PR that is).
This also updates the travis deployment process to always use the
aws
command line tool which we're already installing on Linux and should
enable us to avoid all
dpl
gem issues as well as have greater controlover what's going where.