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.

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

[v2 CLI flag] --instances_metadata #1259

Closed
enocom opened this issue Jul 12, 2022 · 2 comments
Closed

[v2 CLI flag] --instances_metadata #1259

enocom opened this issue Jul 12, 2022 · 2 comments
Labels
priority: p3 Desirable enhancement or 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 Jul 12, 2022

This is a feature request for adding the --instances_metadata flag to v2.

Its description is:

If provided, it is treated as a path to a metadata value which
is polled for a comma-separated list of instances to connect to. For example,
to use the instance metadata value named 'cloud-sql-instances' you would
provide 'instance/attributes/cloud-sql-instances'. Not compatible with -fuse

If this is a useful flag that you'd like to see ported to v2, add a 👍 to this request.

@enocom enocom added priority: p3 Desirable enhancement or fix. May not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design. v2 labels Jul 12, 2022
@enocom enocom changed the title [v2 CLI flag] --instances-metadata [v2 CLI flag] --instances_metadata Jul 12, 2022
@enocom
Copy link
Member Author

enocom commented Sep 14, 2022

This might be covered by #1045.

@enocom enocom removed their assignment Oct 13, 2022
@github-actions github-actions bot removed the v2 label Nov 4, 2022
@enocom
Copy link
Member Author

enocom commented Nov 18, 2022

We're looking at adding support for dynamically configuring instance connection names from multiple sources (secret manager, pub/sub topics connected to a secret, and possibly instance metadata). Let's track that work over on #1045.

@enocom enocom closed this as completed Nov 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p3 Desirable enhancement or 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
Development

No branches or pull requests

1 participant