generated from webtechnicom/Stripe-Connect
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
0 parents
commit dba08a5
Showing
24 changed files
with
648 additions
and
0 deletions.
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,170 @@ | ||
# This workflow will build a docker container, publish it to Google Container Registry, and deploy it to GKE when a release is created | ||
# | ||
# To configure this workflow: | ||
# | ||
# 1. Ensure that your repository contains the necessary configuration for your Google Kubernetes Engine cluster, including deployment.yml, kustomization.yml, service.yml, etc. | ||
# | ||
# 2. Set up secrets in your workspace: GKE_PROJECT with the name of the project and GKE_SA_KEY with the Base64 encoded JSON service account key (https://github.com/GoogleCloudPlatform/github-actions/tree/docs/service-account-key/setup-gcloud#inputs). | ||
# | ||
# 3. Change the values for the GKE_ZONE, GKE_CLUSTER, IMAGE, and DEPLOYMENT_NAME environment variables (below). | ||
# | ||
# For more support on how to run the workflow, please visit https://github.com/google-github-actions/setup-gcloud/tree/master/example-workflows/gke | ||
|
||
name: Build and Deploy to GKE | ||
|
||
on: | ||
release: | ||
types: [created] | ||
|
||
env: | ||
PROJECT_ID: ${{ secrets.GKE_PROJECT }} | ||
GKE_CLUSTER: cluster-1 # TODO: update to cluster name | ||
GKE_ZONE: us-central1-c # TODO: update to cluster zone | ||
DEPLOYMENT_NAME: gke-test # TODO: update to deployment name | ||
IMAGE: static-site | ||
|
||
jobs: | ||
setup-build-publish-deploy: | ||
name: Setup, Build, Publish, and Deploy | ||
runs-on: ubuntu-latest | ||
environment: production | ||
|
||
steps: | ||
- name: Checkout | ||
uses: actions/checkout@v2 | ||
|
||
# Setup gcloud CLI | ||
- uses: google-github-actions/[email protected] | ||
with: | ||
service_account_key: ${{ secrets.GKE_SA_KEY }} | ||
project_id: ${{ secrets.GKE_PROJECT }} | ||
|
||
# Configure Docker to use the gcloud command-line tool as a credential | ||
# helper for authentication | ||
- run: |- | ||
gcloud --quiet auth configure-docker | ||
# Get the GKE credentials so we can deploy to the cluster | ||
- uses: google-github-actions/[email protected] | ||
with: | ||
cluster_name: ${{ env.GKE_CLUSTER }} | ||
location: ${{ env.GKE_ZONE }} | ||
credentials: ${{ secrets.GKE_SA_KEY }} | ||
|
||
# Build the Docker image | ||
- name: Build | ||
run: |- | ||
docker build \ | ||
--tag "gcr.io/$PROJECT_ID/$IMAGE:$GITHUB_SHA" \ | ||
--build-arg GITHUB_SHA="$GITHUB_SHA" \ | ||
--build-arg GITHUB_REF="$GITHUB_REF" \ | ||
. | ||
# Push the Docker image to Google Container Registry | ||
- name: Publish | ||
run: |- | ||
docker push "gcr.io/$PROJECT_ID/$IMAGE:$GITHUB_SHA" | ||
# Set up kustomize | ||
- name: Set up Kustomize | ||
run: |- | ||
curl -sfLo kustomize https://github.com/kubernetes-sigs/kustomize/releases/download/v3.1.0/kustomize_3.1.0_linux_amd64 | ||
chmod u+x ./kustomize | ||
# Deploy the Docker image to the GKE cluster | ||
- name: Deploy | ||
run: |- | ||
./kustomize edit set image gcr.io/PROJECT_ID/IMAGE:TAG=gcr.io/$PROJECT_ID/$IMAGE:$GITHUB_SHA | ||
./kustomize build . | kubectl apply -f - | ||
kubectl rollout status deployment/$DEPLOYMENT_NAME | ||
kubectl get services -o wide | ||
# This workflow will build and push a new container image to Amazon ECR, | ||
# and then will deploy a new task definition to Amazon ECS, when a release is created | ||
# | ||
# To use this workflow, you will need to complete the following set-up steps: | ||
# | ||
# 1. Create an ECR repository to store your images. | ||
# For example: `aws ecr create-repository --repository-name my-ecr-repo --region us-east-2`. | ||
# Replace the value of `ECR_REPOSITORY` in the workflow below with your repository's name. | ||
# Replace the value of `aws-region` in the workflow below with your repository's region. | ||
# | ||
# 2. Create an ECS task definition, an ECS cluster, and an ECS service. | ||
# For example, follow the Getting Started guide on the ECS console: | ||
# https://us-east-2.console.aws.amazon.com/ecs/home?region=us-east-2#/firstRun | ||
# Replace the values for `service` and `cluster` in the workflow below with your service and cluster names. | ||
# | ||
# 3. Store your ECS task definition as a JSON file in your repository. | ||
# The format should follow the output of `aws ecs register-task-definition --generate-cli-skeleton`. | ||
# Replace the value of `task-definition` in the workflow below with your JSON file's name. | ||
# Replace the value of `container-name` in the workflow below with the name of the container | ||
# in the `containerDefinitions` section of the task definition. | ||
# | ||
# 4. Store an IAM user access key in GitHub Actions secrets named `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`. | ||
# See the documentation for each action used below for the recommended IAM policies for this IAM user, | ||
# and best practices on handling the access key credentials. | ||
|
||
on: | ||
release: | ||
types: [created] | ||
|
||
name: Deploy to Amazon ECS | ||
|
||
jobs: | ||
deploy: | ||
name: Deploy | ||
runs-on: ubuntu-latest | ||
|
||
steps: | ||
- name: Checkout | ||
uses: actions/checkout@v2 | ||
|
||
- name: Configure AWS credentials | ||
uses: aws-actions/configure-aws-credentials@v1 | ||
with: | ||
aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }} | ||
aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }} | ||
aws-region: us-east-2 | ||
|
||
- name: Login to Amazon ECR | ||
id: login-ecr | ||
uses: aws-actions/amazon-ecr-login@v1 | ||
|
||
- name: Build, tag, and push image to Amazon ECR | ||
id: build-image | ||
env: | ||
ECR_REGISTRY: ${{ steps.login-ecr.outputs.registry }} | ||
ECR_REPOSITORY: my-ecr-repo | ||
IMAGE_TAG: ${{ github.sha }} | ||
run: | | ||
# Build a docker container and | ||
# push it to ECR so that it can | ||
# be deployed to ECS. | ||
docker build -t $ECR_REGISTRY/$ECR_REPOSITORY:$IMAGE_TAG . | ||
docker push $ECR_REGISTRY/$ECR_REPOSITORY:$IMAGE_TAG | ||
echo "::set-output name=image::$ECR_REGISTRY/$ECR_REPOSITORY:$IMAGE_TAG" | ||
- name: Fill in the new image ID in the Amazon ECS task definition | ||
id: task-def | ||
uses: aws-actions/amazon-ecs-render-task-definition@v1 | ||
with: | ||
task-definition: task-definition.json | ||
container-name: sample-app | ||
image: ${{ steps.build-image.outputs.image }} | ||
|
||
- name: Deploy Amazon ECS task definition | ||
uses: aws-actions/amazon-ecs-deploy-task-definition@v1 | ||
with: | ||
task-definition: ${{ steps.task-def.outputs.task-definition }} | ||
service: sample-app-service | ||
cluster: default | ||
wait-for-service-stability: true | ||
- name: Cache | ||
uses: actions/[email protected] | ||
with: | ||
# A list of files, directories, and wildcard patterns to cache and restore | ||
path: | ||
# An explicit key for restoring and saving the cache | ||
key: | ||
# An ordered list of keys to use for restoring the cache if no cache hit occurred for key | ||
restore-keys: # optional | ||
# The chunk size used to split up large files during upload, in bytes | ||
upload-chunk-size: # optional |
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,80 @@ | ||
# This workflow will build and push a new container image to Amazon ECR, | ||
# and then will deploy a new task definition to Amazon ECS, when a release is created | ||
# | ||
# To use this workflow, you will need to complete the following set-up steps: | ||
# | ||
# 1. Create an ECR repository to store your images. | ||
# For example: `aws ecr create-repository --repository-name my-ecr-repo --region us-east-2`. | ||
# Replace the value of `ECR_REPOSITORY` in the workflow below with your repository's name. | ||
# Replace the value of `aws-region` in the workflow below with your repository's region. | ||
# | ||
# 2. Create an ECS task definition, an ECS cluster, and an ECS service. | ||
# For example, follow the Getting Started guide on the ECS console: | ||
# https://us-east-2.console.aws.amazon.com/ecs/home?region=us-east-2#/firstRun | ||
# Replace the values for `service` and `cluster` in the workflow below with your service and cluster names. | ||
# | ||
# 3. Store your ECS task definition as a JSON file in your repository. | ||
# The format should follow the output of `aws ecs register-task-definition --generate-cli-skeleton`. | ||
# Replace the value of `task-definition` in the workflow below with your JSON file's name. | ||
# Replace the value of `container-name` in the workflow below with the name of the container | ||
# in the `containerDefinitions` section of the task definition. | ||
# | ||
# 4. Store an IAM user access key in GitHub Actions secrets named `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`. | ||
# See the documentation for each action used below for the recommended IAM policies for this IAM user, | ||
# and best practices on handling the access key credentials. | ||
|
||
on: | ||
release: | ||
types: [created] | ||
|
||
name: Deploy to Amazon ECS | ||
|
||
jobs: | ||
deploy: | ||
name: Deploy | ||
runs-on: ubuntu-latest | ||
|
||
steps: | ||
- name: Checkout | ||
uses: actions/checkout@v2 | ||
|
||
- name: Configure AWS credentials | ||
uses: aws-actions/configure-aws-credentials@v1 | ||
with: | ||
aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }} | ||
aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }} | ||
aws-region: us-east-2 | ||
|
||
- name: Login to Amazon ECR | ||
id: login-ecr | ||
uses: aws-actions/amazon-ecr-login@v1 | ||
|
||
- name: Build, tag, and push image to Amazon ECR | ||
id: build-image | ||
env: | ||
ECR_REGISTRY: ${{ steps.login-ecr.outputs.registry }} | ||
ECR_REPOSITORY: my-ecr-repo | ||
IMAGE_TAG: ${{ github.sha }} | ||
run: | | ||
# Build a docker container and | ||
# push it to ECR so that it can | ||
# be deployed to ECS. | ||
docker build -t $ECR_REGISTRY/$ECR_REPOSITORY:$IMAGE_TAG . | ||
docker push $ECR_REGISTRY/$ECR_REPOSITORY:$IMAGE_TAG | ||
echo "::set-output name=image::$ECR_REGISTRY/$ECR_REPOSITORY:$IMAGE_TAG" | ||
- name: Fill in the new image ID in the Amazon ECS task definition | ||
id: task-def | ||
uses: aws-actions/amazon-ecs-render-task-definition@v1 | ||
with: | ||
task-definition: task-definition.json | ||
container-name: sample-app | ||
image: ${{ steps.build-image.outputs.image }} | ||
|
||
- name: Deploy Amazon ECS task definition | ||
uses: aws-actions/amazon-ecs-deploy-task-definition@v1 | ||
with: | ||
task-definition: ${{ steps.task-def.outputs.task-definition }} | ||
service: sample-app-service | ||
cluster: default | ||
wait-for-service-stability: true |
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,21 @@ | ||
composer require stripe/stripe-php | ||
$stripe = new \Stripe\StripeClient("pk_live_51AXJ0vFCL1ycm3RcEzn0xodUBXt9InPZHaW6ZqrHGiXPUPsmWGT9U27OtFMn7gxFtaemBMBfXUmKnsoWUETNefs100MaPY8r0N"); | ||
$ch = $stripe->charges->capture( | ||
'ch_1HPcNZFCL1ycm3Rc3bqlrwwV', | ||
[], | ||
['api_key' => 'pk_live_51AXJ0vFCL1ycm3RcEzn0xodUBXt9InPZHaW6ZqrHGiXPUPsmWGT9U27OtFMn7gxFtaemBMBfXUmKnsoWUETNefs100MaPY8r0N] | ||
); | ||
$ch = $stripe->charges->capture( | ||
'ch_1HPcNZFCL1ycm3Rc3bqlrwwV', | ||
[], | ||
['stripe_account' => 'acct_1AXJ0vFCL1ycm3Rc'] | ||
); | ||
/ Set your secret key. Remember to switch to your live secret key in production! | ||
// See your keys here: https://dashboard.stripe.com/account/apikeys | ||
\Stripe\Stripe::setApiKey('pk_live_51AXJ0vFCL1ycm3RcEzn0xodUBXt9InPZHaW6ZqrHGiXPUPsmWGT9U27OtFMn7gxFtaemBMBfXUmKnsoWUETNefs100MaPY8r0N'); | ||
|
||
$account = \Stripe\Account::create([ | ||
'country' => 'US', | ||
'type' => 'express', | ||
'requested_capabilities' => ['card_payments', 'transfers'], | ||
]); |
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,3 @@ | ||
stripe feedback | ||
stripe help login | ||
stripe version |
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,37 @@ | ||
{ | ||
"_meta": { | ||
"template_version": 0 | ||
}, | ||
"fixtures": [ | ||
{ | ||
"name": "cust_bender", | ||
"path": "/v1/customers", | ||
"method": "post", | ||
"params": { | ||
"name": "Bender Bending Rodriguez", | ||
"email": "[email protected]", | ||
"source": "tok_visa", | ||
"address": { | ||
"line1": "1 Planet Express St", | ||
"city": "New New York" | ||
} | ||
} | ||
}, | ||
{ | ||
"name": "char_bender", | ||
"path": "/v1/charges", | ||
"method": "post", | ||
"params": { | ||
"customer": "${cust_bender:id}", | ||
"amount": 100, | ||
"currency": "usd", | ||
"capture": false | ||
} | ||
}, | ||
{ | ||
"name": "capt_bender", | ||
"path": "/v1/charges/${char_bender:id}/capture", | ||
"method": "post" | ||
} | ||
] | ||
} |
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,54 @@ | ||
stripe post /v1/payment_intents \ | ||
-d amount=2000 \ | ||
-d currency=usd \ | ||
-d "payment_method_types[]=card" | ||
{ | ||
"id": "pi_1HP4JjIV32DS3o2YiorBT1JK", | ||
"object": "payment_intent", | ||
"amount": 1000, | ||
"amount_capturable": 0, | ||
"amount_received": 0, | ||
"application": null, | ||
"application_fee_amount": null, | ||
"canceled_at": null, | ||
"cancellation_reason": null, | ||
"capture_method": "automatic", | ||
"charges": { | ||
"object": "list", | ||
"data": [], | ||
"has_more": false, | ||
"url": "/v1/charges?payment_intent=pi_1HP4JjIV32DS3o2YiorBT1JK" | ||
}, | ||
"client_secret": "pi_1HP4JjIV32DS3o2YiorBT1JK_secret_Tpvk6IsQqaDn21wtSQw4xPqj6", | ||
"confirmation_method": "automatic", | ||
"created": 1599561891, | ||
"currency": "usd", | ||
"customer": null, | ||
"description": "Created by stripe.com/docs demo", | ||
"invoice": null, | ||
"last_payment_error": null, | ||
"livemode": false, | ||
"metadata": {}, | ||
"next_action": null, | ||
"on_behalf_of": null, | ||
"payment_method": null, | ||
"payment_method_options": { | ||
"card": { | ||
"installments": null, | ||
"network": null, | ||
"request_three_d_secure": "automatic" | ||
} | ||
}, | ||
"payment_method_types": [ | ||
"card" | ||
], | ||
"receipt_email": null, | ||
"review": null, | ||
"setup_future_usage": null, | ||
"shipping": null, | ||
"statement_descriptor": null, | ||
"statement_descriptor_suffix": null, | ||
"status": "requires_payment_method", | ||
"transfer_data": null, | ||
"transfer_group": null | ||
} |
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,3 @@ | ||
stripe config --set color on | ||
stripe config --unset color | ||
stripe config --list |
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,6 @@ | ||
stripe delete /v1/customers/cus_I0NDTFXEN4dY7P | ||
{ | ||
"id": "cus_I0NDTFXEN4dY7P", | ||
"object": "customer", | ||
"deleted": true | ||
} |
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,2 @@ | ||
# stripe | ||
repository |
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,3 @@ | ||
stripe login | ||
stripe login --project-name=rocket-rides | ||
stripe login --interactive |
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
stripe listen --api-key pk_live_51GlK6hIV32DS3o2Yo0Pkhr9ejAVrC4gvJO7zCeCRcXN6ZOuS2K6roTR9R4khtOYM0nM7x1frTIORnmtgfodPzTBt00sY7fLvr5 |
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,2 @@ | ||
stripe completion | ||
stripe completion --shell zsh |
Oops, something went wrong.