You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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?
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.
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 alocal.File
resource might offer a simpler and more consistent way to manage a file within the resource lifecycle.The text was updated successfully, but these errors were encountered: