-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Quick & dirty setup of a read only airbyte instance #1802
Access has been restricted
You have triggered a rate limit.
Please wait a few minutes before you try again;
in some cases this may take up to an hour.
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
started looking at this but going to need more time to go through in detail. putting it down for now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good.
. tools/lib/lib.sh | ||
|
||
TUNNEL_PORT=${TUNNEL_PORT:-4242} | ||
SSH_KEY=${SSH_KEY:-~/.ssh/airbyte-app.pem} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this ssh key shared somewhere?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
now it is. In lastpass shared-engineering
What
Quick & dirty setup of a read only airbyte instance
How
We expose airbyte through a public LB and we disable all the
write
api 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)