Validate API key #504
Merged
Validate API key #504
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
|
@dremin quick question - so if the validate-flex-account job fails (process exists with non-zero), the jobs that depends/needs this step (e.g. perform-initial-serverless-release) will not run, correct? |
Yup! Here is an example run that shows what happens: https://github.com/twilio-professional-services/flex-project-template/actions/runs/7997394623/job/21841779364 |
djayanna
approved these changes
Feb 22, 2024
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.
Summary
Before we deploy anything, we need to make sure that we are on a Flex account, and that the provided API key and secret are for the same account as the provided account SID. This can help prevent accidental deployments to the wrong account when setting up an environment.
Checklist