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 a local.File resource #152

Open
lukehoban opened this issue Oct 28, 2022 · 2 comments
Open

Add a local.File resource #152

lukehoban opened this issue Oct 28, 2022 · 2 comments
Labels
kind/enhancement Improvements or new features

Comments

@lukehoban
Copy link
Contributor

There are some common cases where users want to manage a file on disk as part of local deployments. For these cases, a local.File resource could be useful. This would serve a similar use case as https://registry.terraform.io/providers/hashicorp/local/latest/docs/resources/file.

This can be accomplished today via local.Command or via using file I/O in the Pulumi programming language of choice. But a local.File resource might offer a simpler and more consistent way to manage a file within the resource lifecycle.

@lukehoban lukehoban added kind/enhancement Improvements or new features needs-triage Needs attention from the triage team labels Oct 28, 2022
@iwahbe iwahbe removed the needs-triage Needs attention from the triage team label Oct 31, 2022
@julsemaan
Copy link
Contributor

julsemaan commented May 25, 2024

I do have interest in contributing this feature as well as this is also a need I do have and use the same workaround that is described here.

I guess, is the right place for this in this plugin? Or should this be a new plugin? I see there is a copy file functionality for 'remote' so I'll guess it could be acceptable for this functionality to exist in this plugin?

@EronWright
Copy link

A secondary use-case for a File resource is to be able to draw a dependency on an externally-managed file. I'd like to use a get method to read an external file, then use the file's path and/or content to configure another resource. During preview, the output properties would assumedly have unknown values.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement Improvements or new features
Projects
None yet
Development

No branches or pull requests

4 participants