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
Adds SFTP logging endpoint support #77
Conversation
Conflict fix is at c0afb13 |
c8e4392
to
7d27fe1
Compare
Force-pushed Peter's commit. |
7d27fe1
to
11a0ea9
Compare
Force-pushed rebasing master. |
4512179
to
efaff49
Compare
Force-pushed squashing into single commit. |
efaff49
to
a84a806
Compare
Force-pushed a squashed commit that fixed the failed linting into a single commit. |
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 found a few issues and made comments, but it looks great otherwise. The Uint
and String
helpers are only called for optional fields when their corresponding flag is set. It might be worthwhile to use the NullString
helper for strings instead?
|
||
-s, --service-id=SERVICE-ID Service ID | ||
--version=VERSION Number of service version | ||
-d, --name=NAME The name of the SFTP logging object |
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.
Seems like -n
would be more appropriate.
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.
@ezkl I agree with you. However, using -d
was adopted from a standard set by s3
for the describe
subcommand.
While it may not be a big deal, this change would be backward incompatible --- unless we added -n
--- for anyone using the cli in scripts, etc.
I'm assuming there was a reason for explicitly using -d
for describe
cc @phamann.
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.
Haha very good catch, I think that was a copy/pasta error in the S3 implementation and we should use -n
. I'm also happy with the breaking change to S3, which I can follow up with in a separate PR.
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.
@phamann I can make this change across all logging endpoints after we get them all merged in.
43a648d
to
9420d71
Compare
Force-pushed squash into single commit to include |
9420d71
to
c1314ab
Compare
Force-pushed squashed commit making port option. |
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.
👍 LGTM other than the comments we've discussed.
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.
good work!
Signed-off-by: Colton McCurdy <cmccurdy@fastly.com>
c1314ab
to
3c96d5e
Compare
Force-pushed rebasing master. |
Relevant (Referenced) Link(s)
Validation