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

Unify env_details file #850

Open
carpawell opened this issue Sep 12, 2024 · 0 comments
Open

Unify env_details file #850

carpawell opened this issue Sep 12, 2024 · 0 comments
Labels
enhancement Improving existing functionality I3 Minimal impact S4 Routine U4 Nothing urgent

Comments

@carpawell
Copy link
Member

Is your feature request related to a problem? Please describe.

I'm always frustrated when I see the same things named differently, especially when I am trying to do it often and trying to do it fast.

Describe the solution you'd like

It would be nice to make it more standard: for main services it has "RPC", "Endpoint" or "Address" names for the same things. A control port is named "GRPC address" or "Control gRPC endpoint" depending on the service. Metrics are either "Metrics address" or "Prometheus address".

Describe alternatives you've considered

Nothing was considered.

Additional context

#849 (comment)

@carpawell carpawell added I2 Regular impact feature Completely new functionality labels Sep 12, 2024
@roman-khimov roman-khimov added enhancement Improving existing functionality U4 Nothing urgent S4 Routine I3 Minimal impact and removed I2 Regular impact feature Completely new functionality labels Sep 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Improving existing functionality I3 Minimal impact S4 Routine U4 Nothing urgent
Projects
None yet
Development

No branches or pull requests

2 participants