pulumi/pkg/resource
Abhinav Gupta e6cc299d86
pkg/deploytest: Don't zero CustomTimeouts < 1 minute
deploytest.ResourceMonitor currently zeroes out any custom timeout value
smaller than 60 seconds because it does integer division on it.
Further, it alawys uses a non-nil CustomTimeouts
even when the input was nil.
This causes undesirable breaks in unit tests that use this type.

This change fixes both issues in CustomTimeouts. Now:

- The RegisterResourceRequest.CustomTimeouts field is non-nil
  only if the input CustomTimeouts was non-nil
- time.Duration and float divison is used to accurately format
  the specified duration as a string
2023-04-14 15:05:51 -07:00
..
analyzer all: Reformat with gofumpt 2023-03-03 09:00:24 -08:00
deploy pkg/deploytest: Don't zero CustomTimeouts < 1 minute 2023-04-14 15:05:51 -07:00
edit all: Reformat with gofumpt 2023-03-03 09:00:24 -08:00
graph all: Reformat with gofumpt 2023-03-03 09:00:24 -08:00
provider all: Reformat with gofumpt 2023-03-03 09:00:24 -08:00
stack This commit adds the `Created` and `Modified` timestamps to pulumi state that are optional. 2023-03-27 09:28:26 -07:00
testdata ci: radical idea - what if slow tests & no stdout makes GH consider runner dead? 2022-03-06 14:52:13 -08:00