Bryce Lampe
Bryce Lampe
We started logging the pod's termination message in v4.16. See the [release notes](https://github.com/pulumi/pulumi-kubernetes/releases/tag/v4.16.0) for details about how to setup that termination message. Please let us know how this has worked...
@antdking I'm curious how you would expect the UX to work around this? I can imagine a couple options: 1. Introduce some additional annotations like `skipAwaitCreate`, `skipAwaitDelete`, `skipAwaitUpdate`. 2. Modify...
Question for @antdking, @oktocat and others: do we need a distinction between creates and updates, or are we really just interested in something like `skipAwaitDelete` to compliment `skipAwait`? In other...
@antdking @oktocat FYI we do have an (undocumented) `pulumi.com/deletionPropagationPolicy` annotation which can take values of `orphan` or `background`. Pulumi defaults to [foreground](https://kubernetes.io/docs/concepts/architecture/garbage-collection/#foreground-deletion) deletion, which waits for all dependents to be...
We've discussed this a bit and decided it's probably a bug that `skipAwait` affects deletion at all. Given that the `pulumi.com/deletionPropagationPolicy` annotation exists as a workaround for slow deletes, it's...
@Throne3d does your fine-grained token belong to an organization? If so, try setting `KMC_FRK_OWNER` to the name of your GitHub organization. (I just ran into something similar in https://github.com/microsoft/winget-create/issues/470.)
Something I've done in the past: In the "root" stack's config, declare something like ``` $ cat root/Pulumi.production.yaml ... dependsOn: - pulumi/foo/production - pulumi/bar/production ``` These dependent stacks can have...
> I'm not confident this is actually correct. I don't see annotations being emitted to tell the SDK to serialise/deserialise to the wire protocol with the hyphenated names. > >...
@ajmal-yazdani can you please provide more details? What is this a screenshot of? Is this all of your code? What Pulumi operations are you performing? >> Output of pulumi about...
> Should such a rollback be possible? I don't think this is currently possible. The v2 `documentdb:SqlResourceSqlDatabase` resource has no knowledge of v3 `cosmosdb:SqlResourceSqlDatabase` semantics. Similarly the engine doesn't do...