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

fix: use kebab case for config file consistently #2130

Merged
merged 2 commits into from
Feb 26, 2024
Merged

fix: use kebab case for config file consistently #2130

merged 2 commits into from
Feb 26, 2024

Conversation

enocom
Copy link
Member

@enocom enocom commented Feb 26, 2024

When specifying keys in the configuration file, one must use kebab case. This commit ensures the instance connection names also use kebab case and updates the README to accurately describe the feature.

When configuring the Proxy with a config file, one must use matching flag names and specify any instances with the special key instance-connection-name, or instance-connection-name-i, where i is the zero-based index of the instance.

Follow-on to #2106

When specifying keys in the configuration file, one must use kebab case.
This commit ensures the instance connection names also use kebab case
and updates the README to accurately describe the feature.

When configuring the Proxy with a config file, one must use matching
flag names and specify any instances with the special key
instance-connection-name, or instance-connection-name-i, where i is the
zero-based index of the instance.
@enocom enocom requested a review from a team as a code owner February 26, 2024 18:31
README.md Outdated Show resolved Hide resolved
Copy link
Collaborator

@jackwotherspoon jackwotherspoon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, one typo to fix

Co-authored-by: Jack Wotherspoon <[email protected]>
@enocom enocom merged commit ee52f07 into main Feb 26, 2024
12 checks passed
@enocom enocom deleted the fix-key-names branch February 26, 2024 19:35
@enocom
Copy link
Member Author

enocom commented Feb 26, 2024

FYI @marklonquist

enocom added a commit to GoogleCloudPlatform/alloydb-auth-proxy that referenced this pull request Mar 26, 2024
enocom added a commit to GoogleCloudPlatform/alloydb-auth-proxy that referenced this pull request Mar 26, 2024
enocom added a commit to GoogleCloudPlatform/alloydb-auth-proxy that referenced this pull request Mar 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants