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

Add permission attribute to WebDownload and S3Download actions #72

Open
robgero opened this issue Jun 15, 2022 · 0 comments
Open

Add permission attribute to WebDownload and S3Download actions #72

robgero opened this issue Jun 15, 2022 · 0 comments
Labels

Comments

@robgero
Copy link

robgero commented Jun 15, 2022

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Tell us about your request
What do you want us to build?

It would be nice to specify the permission for the downloaded file when using the WebDownload and S3Download actions.

It could look something like:

name: DownloadMyKey
action: S3Download
inputs:
    - source: s3://mybucket/path/to/privatekey
      destination: /home/user/privatekey
      permissions: 400

and

name: DownloadMyExecutable
action: WebDownload
inputs:
    - source: https://example.com/executable
      destination: /home/user/executable
      permissions: 550

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
What outcome are you trying to achieve, ultimately, and why is it hard/impossible to do right now? What is the impact of not having this problem solved? The more details you can provide, the better we'll be able to understand and solve the problem.

This is not hard/impossible to workaround. It would just be cleaner if I was able to specify the permission in the YAML.

Are you currently working around this issue?
How are you currently solving this problem?

Add commands to the user-data to fix the permissions on the files.

Additional context
Anything else we should know?

See how the CreateFile action works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant