Github user jvwing commented on the issue:
    Our current intentions are specific to S3, as are the implementation and 
tests, so I would prefer starting with S3 alone and refactoring later if/when 
there is demand for a wider option.  Also, I think we can provide a stronger 
user experience as an S3-specific field, helping users either ignore the field 
or pick an appropriate Signer class without Googling for it.  Specifically,
    * Provide the currently supported class names as examples in the 
description text, or
    * Present the options in a drop-down list of the S3 signers.  Something 
similar came up in another PR with respect to server-side encryption and 
enforcing signature v4, and I think a list like "Default Signature", "Signature 
v4", "Signature v2", would be nice.  No, this isn't required, but it seems like 
a nice extra for usability (via extra work for you, I admit it's feature creep).

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

Reply via email to