pulumiservice.TtlSchedule can be created without pulumiservice.DeploymentSettings (and subsequent up
s will error out)
#449
Labels
Milestone
up
s will error out)
#449
What happened?
It's possible to include a
pulumiservice.TtlSchedule
resource in a stack without a correspondingpulumiservice.DeploymentSettings
resource. Runningpulumi up
with just the former will stand up the stack without any error. But then both 1) the TTL schedule will not work and 2) subsequentup
s will return an error like:There should be better error handling and messaging.
Example
(see above)
Output of
pulumi about
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered: