Akmod

At first glance, it looks like ``data[host]`` ends up being a string (when the bug is triggered). If ``for sid in data[host]`` is iterating over a string, then ``sid`` would...

Verified the issue. States should return ``ret["changes"][name] = {"key": "value"}`` But the vagrant state is returning ``ret["changes"][name] = "a string"``. This is why you only see the issue on the...

Looking at other states, it seems like ``ret["changes"][name] = "a string"`` is pretty common. Therefore, I believe this is something that should be fixed in just the ``profile`` outputter and...

``salt-call --local grains.items --output=profile`` also produces an error

Here we go, the bug is most easily reproduced by running this command: ``` salt-call --local state.sls foo --output=profile ```

To be clear, the file path "/etc/ssl/tok-le-wildcard.key" is a symlink that points to elsewhere on your system, but salt is pointed to the symlink for file.manage?

@speedytom ^^

I could not replicate the issue on any version of salt. Rather, this seems to be a configuration problem. When you write: ``` - source: salt:///etc/ssl/tok-le-wildcard.key ``` Salt looks for...

I was able to reproduce the issue on my machine, working on a fix now.

Instead of using `cmd.run` use `cmd.shell` which does the exact same thing as `cmd.run` except that it sets `python_shell=True` -- which prevents the command from being split and parsed weird....