https://pulumi.com logo
#general
Title
# general
w

worried-engineer-33884

02/05/2020, 9:58 PM
We are having an issue where --target-dependents in a pulumi destroy execution does not always find/destroy dependents.  In this example there is a glue workflow Trigger resource that references this Crawler, but it is not detected/deleted when the crawler is destroyed. After the crawler is destroyed, any subsequent operation fails with:
Copy code
failed to verify snapshot: resource urn:pulumi:dev0::ucboitlake::aws:glue/trigger:Trigger::undergrad-admissions-crawler-trigger dependency urn:pulumi:dev0::ucboitlake::aws:glue/crawler:Crawler::undergrad-admissions-crawler refers to missing resource
The Trigger is defined like this:
Copy code
export const undergradAdmissionsCrawlerTrigger = new aws.glue.Trigger(
    "undergrad-admissions-crawler-trigger",
    {
        actions: [
            {
                crawlerName: catalog.undergradAdmissionsCrawler.name,
            },
        ],
        predicate: {
            conditions: [
                {
                    jobName: jobs.admissionsActionsTransformationJob.name,
                    state: "SUCCEEDED",
                },
                {
                    jobName: jobs.admissionsSlateTransformationJob.name,
                    state: "SUCCEEDED",
                },
            ],
        },
        type: "CONDITIONAL",
        workflowName: admissionsTransformationWorkflow.name,
    },
);
Note the reference to
undergradAdmissionsCrawler.name
which does create a dependency in the stack (verified via
pulumi stack export
) but does not seem to get picked up by
--target-dependents
cc @dazzling-memory-8548
g

gentle-diamond-70147

02/06/2020, 3:39 PM
Can you open an issue on GitHub?
w

worried-engineer-33884

02/06/2020, 4:03 PM
2 Views