Skip to content

Conversation

@MunemHashmi
Copy link

Summary

  • Allow CopyToRemote to accept `StringAsset` (text content) in addition to `FileAsset` and `FileArchive`
  • Enables copying generated content like config files, certificates, or scripts directly to remote hosts

Changes

  • Modified `Check()` to allowAdd StringAsset support to CopyToRemote text-based assets
  • Added `copyTextContent()` function for SFTP text transfer
  • Added helper methods and tests
  • Updated documentation

Fixes #825

Allow CopyToRemote to accept StringAsset (text content) in addition to
FileAsset and FileArchive. This enables users to copy generated content
like configuration files, certificates, or scripts directly to remote
hosts without writing to a temporary local file first.

Fixes pulumi#825
@github-actions
Copy link

PR is now waiting for a maintainer to run the acceptance tests.
Note for the maintainer: To run the acceptance tests, please comment /run-acceptance-tests on the PR

@guineveresaenger guineveresaenger self-assigned this Feb 5, 2026
@guineveresaenger guineveresaenger added this to the 0.132 milestone Feb 5, 2026
@guineveresaenger
Copy link
Contributor

Hi @MunemHashmi - thank you so much for this pull request. Apologies for the delay in getting back to you - we must have missed this due to the holidays.

Before we consider your changes, could you please do the following?

  1. rebase (it's a renamed function and safer file permissions)
  2. run make build to generate the schema and provider SDKs and commit the resulting changes.

Please let us know if you'd like help with either of the above. Thank you again!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add support for using pulumi.asset.StringAsset in CopyToRemote

2 participants