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
The name of the resource is used in the artifact path but white-space is not removed. If the name contains spaces, for example, the shell commands will most likely fail or behave unpredictably
Like other resources where the name is significant, the name should be the name of the artifact. I'd be more inclined to support throwing an error on whitespace, or some proper escaping on the shell commands.
The name of the resource is used in the artifact path but white-space is not removed. If the name contains spaces, for example, the shell commands will most likely fail or behave unpredictably
In the above code, if the name was "Deploying Files for User" then the
command
being sent to the execute resource would be:"cp /tmp/artifacts/Deploying Files for User /home/user"
The spaces will break the shell script and the chef-client will fatally error.
We might try to do a gsub on the name when putting it into artifact_root. Something like:
The text was updated successfully, but these errors were encountered: