Bryce Lampe

Results 81 issues of Bryce Lampe

There are situations where Pulumi can plan a Create/Delete that result in a resource being created and then immediately deleted in the same operation. I'm proposing that we detect these...

kind/enhancement
area/engine

### Expected behavior Running `assets:precompile` twice should produce identical asset manifests when none of the underlying assets have been modified. ### Actual behavior https://github.com/rails/sprockets/blob/2c38d99930421c22896a65e1d384edf90830f4c3/lib/sprockets/manifest.rb#L174 `mtime` is always modified. This produces...

This replaces the old Docker provider with the new Docker Build provider. User-facing AWSX types are unchanged. Behavior is unchanged, except we will now automatically store and use an inline...

### Proposed changes ### Related issues (optional)

Followup to my comment [here](https://github.com/pulumi/pulumi-kubernetes/pull/2947#discussion_r1588192130), this removes our custom `ValueOpts` in favor of upstream's `value.Options` to handle merging. Upstream expects to work with files on disk, so we fetch any...

impact/no-changelog-required

See Levi's comment here: https://github.com/pulumi/pulumi-kubernetes/issues/1567#issuecomment-1758759758

kind/enhancement

This exposes opt-in provider configuration to disable upsert behavior. When this is set we will use CSA for creation and surface "already exists" errors when we attempt to overwrite something....

### Proposed changes User feedback [here](https://github.com/pulumi/pulumi-kubernetes/issues/2948) indicates that upsert behavior is actually desirable, and the concern is more along the lines of preventing accidental resource deletions. I agree with all...

A user was expecting to find `snapshot.storage.k8s.io` resources in the provider. This API went GA in 1.20 and many distributions enable it by default. Users can generate types themselves using...

customer/feedback
kind/enhancement
area/custom-resources

The API server can return a 429 instructing the client to retry, but client-go needs to be explicitly configured to respect that response. We should enable that configuration expose it...

kind/enhancement