OnTrack deployement on GCP #5
Open
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Deploy OnTrack on GCP
Description
Deploy OnTrack on GCP
#Features include:
##Type of change
-[ ] Bug fix (api server does not get started when a cached version of server.pid is available)
-[ ] New feature (Proxy Configuration for GCP account)
-[ ] This change requires a documentation update
-[ ] How Has This Been Tested: Setup has been tested at 2 level 1. On a local machine with localhost setup 2. Created a test vm instance and fixed all the issues on test infra.
-[ ] Please describe the tests that you ran to verify your changes. Service on GCP is deployed the first time. To test open the following link https://34.129.127.168 in a browser. A certificate warning will be displayed. Also, make sure VM instances on google cloud are up and running.
Testing Checklist:
Tested container deployment successfully
Checklist:
My code follows the style guidelines of this project
I have performed a self-review of my own code
I have made corresponding changes to the documentation
My changes generate no new warnings