https://pulumi.com
Join Slack
I’m trying to use <https://www.pulumi.com/docs/pulumi-cloud/deployments/ttl/> =&gt; I have a stack f...
# pulumi-deployments
d
I’m trying to use https://www.pulumi.com/docs/pulumi-cloud/deployments/ttl/ => I have a stack for which I created a 
pulumiservice*.*TtlSchedule
resource… I set it to destroy after the timestamp but nothing happened…
Pulumi copilot says: “The resource has the ‘deleteAfterDestroy’ property set to true, which means it should delete the stack after the specified timestamp. However, it appears that the TTL schedule has not yet triggered as expected. It may be useful to check if the Pulumi service is experiencing any delays or issues with executing TTL schedules.”
The resource has the following outputs:
Copy code
deleteAfterDestroy, true
scheduleId, <uuid>
timestamp, 2024-11-19T17:36:05Z (which is in the past)
I will note that while I don’t have a deployment configuration resource for this stack I have deployed it via REST API
f
If you go into Pulumi Cloud for that deployment schedule, what does it say for "Next expected execution"?
d
Where would I find the deployment schedule in the cloud?
I created a 
pulumiservice.TtlSchedule
resource, but I haven’t configured a deployment
So this only works if I have a corresponding 
pulumiservice.DeploymentSettings
?
f
Correct - you need to have Deployments configured as that's the mechanism for how the TTL is executed
The announcement blog post is a good summary.
So you are saying that you received no error upon creating the 
pulumiservice.TtlSchedule
without the stack's Deployment configured? That seems odd (i.e. an issue) to me
d
So the first time the stack runs I don’t see an error—it just creates the TtlSchedule resource, but I just noticed that when I run 
up
again, I get:
Copy code
Diagnostics:
  pulumiservice:index:TtlSchedule (mystack-ttl-schedule):
    error: failed to update ttl schedule e29c5797-6c39-4477-9243-35f5eea2a90e (timestamp=2024-11-22 01:47:05 +0000 UTC, deleteAfterDestroy=true): 404 API error: Not Found: ScheduledAction 'e29c5797-6c39-4477-9243-35f5eea2a90e' not found

  pulumi:pulumi:Stack (mystack):
    error: update failed
So I guess it doesn’t properly report back on the initial creation
f
Hmmm yeah, looks like it. Would you have a few mins to file an issue in https://github.com/pulumi/pulumi-pulumiservice/issues/new?template=bug.yaml
d
definitely!
21 Views
Open in Slack
PreviousNext
Powered by

Pulumi Community

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.

Powered by