Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Support shorter ways to specify an instance #126

Open
enocom opened this issue Sep 12, 2022 · 1 comment
Open

Support shorter ways to specify an instance #126

enocom opened this issue Sep 12, 2022 · 1 comment
Assignees
@enocom
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.

Comments

@enocom
Copy link
Member

enocom commented Sep 12, 2022 •
edited by jackwotherspoon
Loading

Right now a user must provide a full instance URI to launch the proxy. This is onerous, error-prone, and painful. The proxy should support some kind of shorthand to make it easier to launch the proxy.

One option would be to use something like Cloud SQL's instance connection name, e.g.,

alloydb-auth-proxy project:region:cluster:instance-name

Related to #26.
@enocom enocom added type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design. priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. labels Sep 12, 2022
@kurtisvg
Copy link
Contributor

Maybe tangential, but we should create a request to the UI / API teams to make whatever instance resource name we expose be easily discoverable/copypastable like it is Cloud SQL

@enocom enocom added priority: p2 Moderately-important priority. Fix may not be included in next release. and removed priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. labels May 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@enocom enocom

Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@enocom @kurtisvg