Quick & dirty setup of a read only airbyte instance #1802
Merged
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
cgardens
reviewed
Jan 25, 2021
cgardens
approved these changes
Jan 26, 2021
| . tools/lib/lib.sh | ||
|
|
||
| TUNNEL_PORT=${TUNNEL_PORT:-4242} | ||
| SSH_KEY=${SSH_KEY:-~/.ssh/airbyte-app.pem} |
There was a problem hiding this comment.
is this ssh key shared somewhere?
There was a problem hiding this comment.
now it is. In lastpass shared-engineering
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.
What
Quick & dirty setup of a read only airbyte instance
How
We expose airbyte through a public LB and we disable all the
writeapi calls (accessible via demo.airbyte.io)We expose an admin version of airbyte through a tunnel so we can update configs
I wanted to do it on GCP and use the Identity Aware Proxy to have some basic auth and enable admin through the same lb but the frontend currently doesn't propagate cookies in api calls (see #1756)
I have a poor memory and I don't what to have to go through the AWS console nor try to remember how to create a tunnel so:
To establish the tunnel:
To ssh on the instance:
We can update the configuration with terraform (through terraform cloud)