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

Ok, and to follow up: is there some technique or approach to make Unit tests for Pulumi Components to avoid such situations?

One could check the shape of Type to match aaa:bbb:ccc

Hm, this means that I'll got an error on `up`  or `preview`, but it would be nice to ensure of Components stability on early time (before one will pushed to Nuget\npm feed).

In general, this particular case with signature is not so important.
If the Pulumi is positioned with the really GREAT(!) advantage of using natural programming languages, I believe that there should be also room for  natural developing process (with Unit tests in the toolbox).

As an idea: there is some Mock (or Stub) Framework that could abstract out of the real cloud providers and their real resources, just to ensure of the Pulumi side work is correct.
Have the Pulumi team ever been thought about this thing?

Yes, have a look at
<https://www.pulumi.com/blog/unit-testing-infrastructure-in-nodejs-and-mocha/>
and
<https://www.pulumi.com/blog/testing-your-infrastructure-as-code-with-pulumi/>

These are TypeScript but the same can be applied to .NET

There is <https://github.com/pulumi/pulumi/issues/3633> to track .NET testing

Great job! Thanks a lot!
I'm newby with Pulumi (just met at the last week), and not so familiar with all related resources to lern about Pulumi better.
(just started to read the main blog, watch PulumiTV and explore Docs and this Slack channel)

That's great Omar! .NET is still in preview, so docs are lacking. Feel free to ask more questions here!