No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

other things I've tried:
```&gt; pulumi config set --path 'aws:defaultTags.tags.["user:Project"]' my_project
error: invalid configuration key: could not parse aws:defaultTags.tags.["user:Project"] as a configuration key (configuration keys should be of the form `&lt;namespace&gt;:&lt;name&gt;`)```
--
```&gt; pulumi config set --path 'aws:defaultTags.tags.user:Project' my_project
# same error as above```
--
```&gt; pulumi config set --path 'aws:defaultTags.tags.test' true
error: defaultTags.tags: expected a map```

Hello <@U03CLBPHR0D>, the following commands:
```$ pulumi config set --path 'aws:defaultTags.tags.key' value
$ pulumi config set --path 'aws:defaultTags.tags.otherkey' othervalue```
give me the following stack config:
```config:
  aws:defaultTags:
    tags:
      key: value
      otherkey: othervalue```
The problem for you is that your `key` contains a colon (`user:Project`). This seems to confuse our argument parsing. Can you file an issue for this?
<https://github.com/pulumi/pulumi/issues>

 Hey Ringo, that’s the same format I used for the last command, but I still got the error. This was with a blank yaml so that might be the difference 