switch to CI key #50
Merged
switch to CI key #50
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In an effort to increase our dogfooding, we are using our CI keys wherever possible. This PR switches from using a personal auth token to a dedicated CI key. I already created the according CI key and set it as the value of the secret `LOCALSTACK_API_KEY`.
alexrashed
force-pushed
the
switch-to-ci-key
branch
from
af88503 to
3d7d281
Compare
alexrashed
force-pushed
the
switch-to-ci-key
branch
from
f85cd86 to
e269bef
Compare
whummer
approved these changes
Feb 5, 2024
There was a problem hiding this comment.
Thanks for tackling this @alexrashed !
I just realized that the tests for the aws-replicator tests are failing - will take a look at that shortly! (in a follow-up PR)
alexrashed
force-pushed
the
switch-to-ci-key
branch
from
e269bef to
3d7d281
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In an effort to increase our dogfooding, we are using our CI keys wherever possible. This PR switches from using a personal auth token to a dedicated CI key.
I already created the according CI key and set it as the value of the secret
LOCALSTACK_API_KEY.