mirror of https://github.com/pulumi/pulumi.git
2ef87d86d0
11803: Display text-based diff if yaml/json diff is semantically equal r=aq17 a=aq17 Fixes #11799 https://github.com/pulumi/pulumi/pull/9380 and https://github.com/pulumi/pulumi/pull/9484 introduced changes that render JSON/YAML parsable strings as objects in diffs – therefore, examples such as`"foo:\n bar: {}\n baz: {}\n"` and `"#foo\nfoo:\n bar: {}\n baz: {}\n"` are recognized as equal. This change causes the display to fall back to showing the text-based diff if the JSON/YAML rendering does not indicate any diff. It also prints all object keys even if the value is empty, i.e. `bar: {}` or `bar: ""` will be printed instead of `bar` being omitted. 11893: update package details anchors r=sean1588 a=sean1588 fixes: https://github.com/pulumi/registry/issues/1819 OK taking this for round 2. The first [PR](https://github.com/pulumi/pulumi/pull/11861) to make this change I ended up reverting because there were some pages (the function pages and module pages) still being generated with empty href tags. I have addressed this and updated the change to define the DisplayName and RepositoryName props on the `packageDetails` struct for the individual module pages and function pages. This updates the repository anchor in the Package Details section of the api docs pages. I updated it to display `<package name> repository` for the anchor text in place of the url that was previously shown there. ![image](https://user-images.githubusercontent.com/16751381/213036900-2938a9ad-1992-4170-9b83-0fbbcef409a0.png) So now this will show the following on the following pages: 1. the root index package pages 2. the module pages 3. the resource pages 4. the function pages 11903: ApplyT: Coerce new type wrappers r=abhinav a=abhinav Adds support to ApplyT to automatically coerce new type wrappers when calling the provided functions. With this change, the following is valid: var idout pu.IDOutput = ... idout.ApplyT(func(id string) string { // ... }) Note that this does not use `To{Type}Output` methods at this time. We will likely want to add that in the future given #11750. We can do that in a backwards compatible way. This coerces only those values that are defined with language-level type wrappers in the following form: type ID string This *does not* coerce types with different undedrlying representations. Specifically, the following conversons are not supported even though they're supported by Go using the `T(v)` syntax. string => int string => []byte []byte => string The choice to convert between these types should be made explicitly by the user so that they get the semantics they want. Resolves #11784 11922: ci: freeze 3.52.1 for release r=dixler a=dixler Patch release to provide better stack traces for python https://github.com/pulumi/pulumi/issues/11887 Co-authored-by: aq17 <aqiu@pulumi.com> Co-authored-by: Sean Holung <sean.holung@gmail.com> Co-authored-by: Robbie McKinstry <robbie@pulumi.com> Co-authored-by: Abhinav Gupta <abhinav@pulumi.com> Co-authored-by: Kyle Dixler <kyle@pulumi.com> |
||
---|---|---|
.. | ||
go | ||
nodejs | ||
proto | ||
python | ||
README.md | ||
go.mod | ||
go.sum |