"rdk create" do not throw an error when an existing rule name

[jongogogo]

I think it should be the default behavior when running rdk create with an exisitng rule locally. The rdk should throw a "rule already exist"

[bmorrissirromb]

Depending on what you're asking, this behavior may exist already.

If you run rdk create in a directory that already has a folder with the rule name, you'll receive the following error:

Running create!
Local Rule directory already exists.

However, if you're looking for rdk create to check if there is already a rule deployed in Config with the given rule name, that is not supported currently.