-
Notifications
You must be signed in to change notification settings - Fork 807
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
add custom useragent suffix #910
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: vdhanan The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Pull Request Test Coverage Report for Build 2022
💛 - Coveralls |
940d4ec
to
a17ddc8
Compare
@@ -39,6 +39,8 @@ spec: | |||
- --logtostderr | |||
- --v=2 | |||
env: | |||
- name: CSI_DRIVER_NAME |
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.
Why we want to expose the name as env variable? Feel like it would be more accurate if the useragent is fixed..
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.
yeah I agree, better to just keep it fixed/hardcoded
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.
my thinking was that if the driver's name changed for whatever reason, we'd only have to change it in one place. i don't have a strong preference here, so i'll just hardcode it.
charts/aws-ebs-csi-driver/Chart.yaml
Outdated
@@ -2,7 +2,7 @@ apiVersion: v1 | |||
appVersion: "1.0.0" | |||
name: aws-ebs-csi-driver | |||
description: A Helm chart for AWS EBS CSI Driver | |||
version: 1.2.0 | |||
version: 1.3.0 |
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.
correct me if I'm wrong.. it should be 1.0.3 instead of 1.3.0 as the driver version is still on 1.0.x
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.
I think, if we avoid exposing env variable, then we dont need to change the chart at all
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.
the helm chart version is 1.2.0 on master right now. is that a problem?
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.
In general, the helm chart version doesn't have to and likely won't match the version of the application. That is what appVersion is for to specify the version of the application to use if the user doesn't override it. If the chart keeps getting new features added that work with 1.0.0. of the driver, it will continue to increase in version independent of the driver version.
/lgtm thanks |
Is this a bug fix or adding new feature?
new feature
What is this PR about? / Why do we need it?
modifies the aws sdk client's useragent string to differentiate the ebs csi driver's requests
What testing is done?
turned on debug logs and confirmed that user agent had new string appended