pulumi/pkg/engine/lifecycletest
Paul C. Roberts b72399bd28
The `--expect-no-changes` flag checks for output diffs (#15903)
<!--- 
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. -->
This adds a pseudo op `OpOutputChange` to the set of changes that are
recorded in `display.ResourceChanges` to count the number of output
changes, this is then included in the check used to evaluate the
`--expect-no-changes` flag

When resource outputs are registered, they are checked against their
previous value using existing functionality, the total count of changes
is then added

The internal capability is validated with an engine test, the cli is
validated using an integration test

This will break user workflows that depend on the previous behavior

Fixes #15564

## 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. -->
- [X] I have added tests that prove my fix is effective or that my
feature works
<!--- 
User-facing changes require a CHANGELOG entry.
-->
- [X] 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. -->

---------

Co-authored-by: Paul Roberts <proberts@pulumi.com>
2024-05-01 18:30:49 +00:00
..
alias_test.go The `--expect-no-changes` flag checks for output diffs (#15903) 2024-05-01 18:30:49 +00:00
analyzer_test.go The `--expect-no-changes` flag checks for output diffs (#15903) 2024-05-01 18:30:49 +00:00
continue_on_error_test.go Implement up --continue-on-error (#15740) 2024-04-22 11:12:45 +00:00
delete_before_replace_test.go The `--expect-no-changes` flag checks for output diffs (#15903) 2024-05-01 18:30:49 +00:00
golang_sdk_test.go The `--expect-no-changes` flag checks for output diffs (#15903) 2024-05-01 18:30:49 +00:00
import_test.go The `--expect-no-changes` flag checks for output diffs (#15903) 2024-05-01 18:30:49 +00:00
pending_delete_test.go The `--expect-no-changes` flag checks for output diffs (#15903) 2024-05-01 18:30:49 +00:00
provider_test.go The `--expect-no-changes` flag checks for output diffs (#15903) 2024-05-01 18:30:49 +00:00
pulumi_test.go The `--expect-no-changes` flag checks for output diffs (#15903) 2024-05-01 18:30:49 +00:00
refresh_test.go The `--expect-no-changes` flag checks for output diffs (#15903) 2024-05-01 18:30:49 +00:00
resource_reference_test.go deploytest/RegisterResource: return struct instead of values (#15988) 2024-04-19 11:08:56 +00:00
source_query_test.go deploytest/RegisterResource: return struct instead of values (#15988) 2024-04-19 11:08:56 +00:00
step_generator_test.go deploytest/RegisterResource: return struct instead of values (#15988) 2024-04-19 11:08:56 +00:00
target_test.go The `--expect-no-changes` flag checks for output diffs (#15903) 2024-05-01 18:30:49 +00:00
test_plan.go The `--expect-no-changes` flag checks for output diffs (#15903) 2024-05-01 18:30:49 +00:00
transformation_test.go deploytest/RegisterResource: return struct instead of values (#15988) 2024-04-19 11:08:56 +00:00
update_plan_test.go deploytest/RegisterResource: return struct instead of values (#15988) 2024-04-19 11:08:56 +00:00