darkhelm/notifications-api
1
0
Fork 0
mirror of https://github.com/GSA/notifications-api.git synced 2025-12-14 01:02:09 -05:00
Code Issues Packages Projects Releases Wiki Activity

Notes about push command, URLs for Sandbox

Browse Source
This commit is contained in:
John Skiles Skinner
2024-07-22 15:41:38 -07:00
parent bce064fa0c
commit 3eb34158e3
2 changed files with 7 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
docs/all.md
View File

@@ -449,7 +449,10 @@ If this is the first time you have used Terraform in this repository, you will f
```
cf push --vars-file deploy-config/sandbox.yml --var NEW_RELIC_LICENSE_KEY=$NEW_RELIC_LICENSE_KEY
```
The real `push` command has more var arguments than the single one above. Get their values from a Notify team member.
1. Visit the URL of the app you just deployed
* Admin https://notify-sandbox.app.cloud.gov/
* API https://notify-api-sandbox.app.cloud.gov/
# Database management
@@ -1385,7 +1388,7 @@ After pushing the Admin app, you might see this in the logs
{"name": "app", "levelname": "ERROR", "message": "API unknown failed with status 503 message Request failed", "pathname": "/home/vcap/app/app/__init__.py", ...
```
This indicates that the Admin and API apps are unable to talk to each other because of either a missing route or a missing network policy. The apps require [container-to-container networking](https://cloud.gov/docs/management/container-to-container/) to communicate. List `cf network-policies` and compare the output to other deployed envrionments. If you find a policy is missing, you might have to create a network policy with something like:
This indicates that the Admin and API apps are unable to talk to each other because of either a missing route or a missing network policy. The apps require [container-to-container networking](https://cloud.gov/docs/management/container-to-container/) to communicate. List `cf network-policies` and compare the output to our other deployed envs. If you find a policy is missing, you might have to create a network policy with something like:
```
cf add-network-policy notify-admin-sandbox notify-api-sandbox --protocol tcp --port 61443
```

2
terraform/README.md
View File

@@ -134,6 +134,8 @@ These steps assume shared [Terraform state credentials](#terraform-state-credent
This command *will deploy your changes* to the cloud. This is a healthy part of testing your code in the sandbox, or if you are creating a new environment (a new directory). **Do not** apply in environments that people are relying upon.
If you need to go on to deploy application code on top of the resources you just instantiated, you will [use `cf push`](https://github.com/GSA/notifications-api/blob/main/docs/all.md#deploying-to-the-sandbox)
1. Remove the space deployer service instance when you are done manually running Terraform.
```bash
# <SPACE_NAME> and <ACCOUNT_NAME> have the same values as used above.