pulumi

History

Ian Wahbe 27b9be60ae A property.Value implementation to replace resource.PropertyValue (#15145 ) <!--- Thanks so much for your contribution! If this is your first time contributing, please ensure that you have read the [CONTRIBUTING](https://github.com/pulumi/pulumi/blob/master/CONTRIBUTING.md) documentation. --> # Description <!--- Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. --> The plan is to gradually replace resource.PropertyValue both internally (in `pulumi/pulumi`) and in providers with this implementation. This representation eliminates certain classes of bugs inherent with the old representation: - Modifiers (computed, secret, dependencies) live in a separate space from values, so there is no longer a problem with different nestings. - Equality is well defined and encapsulated. - The distinction between `Output`, `Secret` and `Computed`. - Names have been normalized (Input/Computed, Map/Object). This is our chance to have a property value representation that we like, so please leave comments if you think we can improve the API here. ## Checklist - [X] I have run `make tidy` to update any new dependencies - [X] I have run `make lint` to verify my code passes the lint check - [ ] I have formatted my code using `gofumpt` <!--- Please provide details if the checkbox below is to be left unchecked. --> - [ ] I have added tests that prove my fix is effective or that my feature works <!--- User-facing changes require a CHANGELOG entry. --> - [ ] I have run `make changelog` and committed the `changelog/pending/<file>` documenting my change <!-- If the change(s) in this PR is a modification of an existing call to the Pulumi Cloud, then the service should honor older versions of the CLI where this change would not exist. You must then bump the API version in /pkg/backend/httpstate/client/api.go, as well as add it to the service. --> - [ ] Yes, there are changes in this PR that warrants bumping the Pulumi Cloud API version <!-- @Pulumi employees: If yes, you must submit corresponding changes in the service repo. -->	2024-03-14 19:58:59 +00:00
..
equal_test.go	A property.Value implementation to replace resource.PropertyValue (#15145 )	2024-03-14 19:58:59 +00:00
rapid.go	A property.Value implementation to replace resource.PropertyValue (#15145 )	2024-03-14 19:58:59 +00:00

A property.Value implementation to replace resource.PropertyValue (#15145 )

<!--- 
Thanks so much for your contribution! If this is your first time
contributing, please ensure that you have read the
[CONTRIBUTING](https://github.com/pulumi/pulumi/blob/master/CONTRIBUTING.md)
documentation.
-->

# Description

<!--- Please include a summary of the change and which issue is fixed.
Please also include relevant motivation and context. -->

The plan is to gradually replace resource.PropertyValue both internally
(in `pulumi/pulumi`) and in providers with this implementation.

This representation eliminates certain classes of bugs inherent with the
old representation:

- Modifiers (computed, secret, dependencies) live in a separate space
from values, so there is no longer a problem with different nestings.

- Equality is well defined and encapsulated.

- The distinction between `Output`, `Secret` and `Computed`.

- Names have been normalized (Input/Computed, Map/Object).

This is our chance to have a property value representation that we like,
so please leave comments if you think we can improve the API here.

## Checklist

- [X] I have run `make tidy` to update any new dependencies
- [X] I have run `make lint` to verify my code passes the lint check
  - [ ] I have formatted my code using `gofumpt`

<!--- Please provide details if the checkbox below is to be left
unchecked. -->
- [ ] I have added tests that prove my fix is effective or that my
feature works
<!--- 
User-facing changes require a CHANGELOG entry.
-->
- [ ] I have run `make changelog` and committed the
`changelog/pending/<file>` documenting my change
<!--
If the change(s) in this PR is a modification of an existing call to the
Pulumi Cloud,
then the service should honor older versions of the CLI where this
change would not exist.
You must then bump the API version in
/pkg/backend/httpstate/client/api.go, as well as add
it to the service.
-->
- [ ] Yes, there are changes in this PR that warrants bumping the Pulumi
Cloud API version
<!-- @Pulumi employees: If yes, you must submit corresponding changes in
the service repo. -->

2024-03-14 19:58:59 +00:00

equal_test.go

A property.Value implementation to replace resource.PropertyValue (#15145 )

2024-03-14 19:58:59 +00:00

rapid.go

A property.Value implementation to replace resource.PropertyValue (#15145 )

2024-03-14 19:58:59 +00:00