https://pulumi.com logo
Join Slack
Powered by
This message was deleted.
# general
s
This message was deleted.
i
My 
Component
usage looks like:
Copy code
export const certManager = new CertManager(
  'certmanager',
  {
    cloudflareApiKey: new Config('cloudflare').require('apikey'),
    email: output(stack.identity.getOutput('email')),
    namespace,
    staging: new Config('certmanager').requireBoolean('staging'),
  },
  opts({ dependsOn: [clusterAdminBinding, namespace] }),
)
It is erroring on these specific dependencies. Both dependencies can be created fine. Do I need to propagate the 
dependsOn
inside my 
Component
definition to every child?
I printed my resolved 
opts
just to be sure, they look good to me:
Copy code
options: { providers:
       { kubernetes:
          Provider {
            __pulumiResource: true,
            __providers: {},
            __protect: false,
            urn: [OutputImpl],
            id: [OutputImpl],
            cluster: [OutputImpl],
            context: [OutputImpl],
            kubeconfig: [OutputImpl],
            namespace: [OutputImpl],
            __pulumiCustomResource: true } },
      dependsOn:
       [ ClusterRoleBinding {
           __pulumiResource: true,
           __providers: {},
           __protect: false,
           urn: [OutputImpl],
           id: [OutputImpl],
           apiVersion: [OutputImpl],
           kind: [OutputImpl],
           metadata: [OutputImpl],
           roleRef: [OutputImpl],
           subjects: [OutputImpl],
           __pulumiCustomResource: true,
           __inputs: [Object] },
         Namespace {
           __pulumiResource: true,
           __providers: {},
           __protect: false,
           urn: [OutputImpl],
           id: [OutputImpl],
           apiVersion: [OutputImpl],
           kind: [OutputImpl],
           metadata: [OutputImpl],
           spec: [OutputImpl],
           status: [OutputImpl],
           __pulumiCustomResource: true,
           __inputs: [Object] } ] }
c
@important-leather-28796 component resources are not respected by depends on this is a known bug cc @microscopic-florist-22719
work around is to depend on a specific resource in your component that you care about.
m
@creamy-potato-29402 I don’t think that’s the scenario here
@important-leather-28796 it sounds like you’re having trouble with resources inside the component starting to create before the resources listed in the component’s 
dependsOn
are ready
Is that right?
i
children of a Component seem to start being created before top level dependsOn - or so it seems
I just noticed the console printout to be missing my component at the top, it is pictured associated with a stack
m
Okay, that’s what I thought. That’s super weird, and definitely shouldn’t happen assuming everything is correctly parented
Oh interesting
That is very strange.
i
Component is 
'af:pulumi:CertManager'
- not sure where I could be making an error here. I’ll try to simplify and see if preview is correct at some point
m
yeah, your component definition looks correct to me
i
destroy tree looks right
m
also possible if a bit unlikely that the CLI rendering did something weird here
i
preview is good, running again
tree looks good now. Is there a bug to follow on the depends? I’ll just create a helper for now to propagate them
Didn’t seem to matter. Chaining my 
dependsOn
yields the same errors.
I’d understand if I messed up the cluster role binding, but the namespace is a no-brainer.
m
well, they should propagate
i
visually, the timing seems fine and the clusterRoleBinding/namespace are done, but I’m still unable to get the chart to run.
m
so just to be clear, what you're trying to do is expected to work. the 
dependsOn
on the parent component should prevent its child resources from being created before they are ready.
b
Is 
namespace
a 
Namespace
resource instance? If so, can you use it in helm values like that?
i
namespace as passed in to the 
Component
is a resource instance.
inside the component it is destructured:
Copy code
const { cloudflareApiKey, email, namespace: namespaceObject, staging = false } = args
    const namespace = namespaceObject.metadata.name
and I added 
dependsOn: [namespaceObject, crds]
to the chart
b
Oh, ok, cause in the first snippet you had 
namespace
in both helm values and 
dependsOn
.
i
right, I tried to be careful there but I believe it is accurate - ts types help here.
b
What's strange is it looks like it resolves 
namespaceObject.metadata.name
before actually creating the namespace...
i
so something else is wrong. the namespace is clearly created and 
info
on creation is still failing on the retries e.g. 
Retry #5; creation failed: namespaces "development" not found
it does seem to resolve correctly as indicated by the retry message
i’ll change the namespace name to static just for kicks - that is a stack name at the moment
b
Although it feels like that should just create stuff in 
default
namespace and not complain about not finding 
development
namespace.
i
makes sense
adding a transform to the helm chart for namespaces had no effect
it is clear to me that the namespace 
development
exists, I need to look again at permissions or something else.
I’ll pick this up tomorrow, approach is to go god-mode on permissions and see if things start working….then back up from there. The namespace exists, so something else is up.
6 Views
Open in Slack
PreviousNext
Powered by