-
Notifications
You must be signed in to change notification settings - Fork 23.7k
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
Cannot set cache headers in s3 and aws_s3 module #31232
Labels
affects_2.4
This issue/PR affects Ansible v2.4
aws
bug
This issue/PR relates to a bug.
cloud
deprecated
This issue/PR relates to a deprecated module.
module
This issue/PR relates to a module.
support:core
This issue/PR relates to code supported by the Ansible Engineering Team.
Comments
ansibot
added
affects_2.4
This issue/PR affects Ansible v2.4
aws
bug_report
cloud
deprecated
This issue/PR relates to a deprecated module.
module
This issue/PR relates to a module.
needs_triage
Needs a first human triage before being processed.
support:core
This issue/PR relates to code supported by the Ansible Engineering Team.
labels
Oct 3, 2017
ryansb
removed
the
needs_triage
Needs a first human triage before being processed.
label
Oct 3, 2017
+1 Have the some bug here |
s-hertel
added a commit
to s-hertel/ansible
that referenced
this issue
Oct 10, 2017
) * Module option metadata are extra arguments rather than S3 object metadata: update ExtraArgs variable. * Remove hyphens from ExtraArgs to maintain backwards compatibility * Map lowercase extra args to CamelCase * Maintain backwards compatibility by guessing at content type rather than always defaulting to binary/octet-stream. * Fix ExtraArgs for non-hyphenated options * Simplify logic
s-hertel
added a commit
that referenced
this issue
Oct 10, 2017
BondAnthony
pushed a commit
to BondAnthony/ansible
that referenced
this issue
Oct 14, 2017
) * Module option metadata are extra arguments rather than S3 object metadata: update ExtraArgs variable. * Remove hyphens from ExtraArgs to maintain backwards compatibility * Map lowercase extra args to CamelCase * Maintain backwards compatibility by guessing at content type rather than always defaulting to binary/octet-stream. * Fix ExtraArgs for non-hyphenated options * Simplify logic
mtb-xt
pushed a commit
to mtb-xt/ansible
that referenced
this issue
Oct 15, 2017
) * Module option metadata are extra arguments rather than S3 object metadata: update ExtraArgs variable. * Remove hyphens from ExtraArgs to maintain backwards compatibility * Map lowercase extra args to CamelCase * Maintain backwards compatibility by guessing at content type rather than always defaulting to binary/octet-stream. * Fix ExtraArgs for non-hyphenated options * Simplify logic
This was referenced Jan 31, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
affects_2.4
This issue/PR affects Ansible v2.4
aws
bug
This issue/PR relates to a bug.
cloud
deprecated
This issue/PR relates to a deprecated module.
module
This issue/PR relates to a module.
support:core
This issue/PR relates to code supported by the Ansible Engineering Team.
ISSUE TYPE
COMPONENT NAME
s3 and aws_s3
ANSIBLE VERSION
CONFIGURATION
vanilla
OS / ENVIRONMENT
ubuntu 16.04
SUMMARY
Setting
Cache-Control
headers inmetadata
will result in setting the metadata key:aws_s3 x-amz-meta-cache-control
on AWS. This makes it impossible to set theCache-Control
header on the s3 object. TheContent-Type
was set automatically before. Now it defaults tobinary/octet-stream
STEPS TO REPRODUCE
Try to put a file to s3
EXPECTED RESULTS
I expect the
Cache-Control
header to be setACTUAL RESULTS
aws_s3 x-amz-meta-cache-control
was set notCache-Control
The text was updated successfully, but these errors were encountered: