It looks like resource naming got more strict? I'm...
# general
t
It looks like resource naming got more strict? I'm trying to make a new
CustomResource
and it complains about what I pass to
super
call... E.g.
Copy code
class MyFunctionApp extends pulumi.CustomResource {
    constructor(name: string, options: MyAppServiceOptions) {
        super("azure:mikhail:MyFunctionApp", name);
gets
unrecognized resource type (Check): azure:mikhail:MyFunctionApp
s
Not sure if this changed specifically, but it seems like it would be a bad idea to prefix the name with “someone elses” namespace? Not that azure is about launch Mikhail-as-a-service, but in the general case 🙂
t
I can't do mikhailmyMyThing either
It complains
no resource plugin 'mikhail' found in the workspace
s
Ah, not sure on that one - I’ve not had to create a CustomResource yet, only ComponentResources
t
Ah, that's probably my problem
Mistyped Component as Custom 😂
Solved
s
Aha! Easy mistake I guess!