mirror of https://github.com/pulumi/pulumi.git
f278fa9696
File backends currently do not support indicating whether an operation is currently in progress or not. In the `stack ls --json` output we always end up with a "updateInProgress = false" field, even when an update is in progress. This is misleading. Disable showing this erroneous and misleading output. Fixes #10677 Based on Luke's comments in that issue, I believe we should merge this as bug fix for the issue, and then open a separate feature request tracking the implementation of tracking whether an update is in progress in the file backend. ## 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 - [x] 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. --> |
||
|---|---|---|
| .. | ||
| backend.go | ||
| backend_legacy_test.go | ||
| backend_test.go | ||
| bucket.go | ||
| bucket_test.go | ||
| doc.go | ||
| lock.go | ||
| meta.go | ||
| meta_test.go | ||
| pool.go | ||
| pool_test.go | ||
| snapshot.go | ||
| stack.go | ||
| state.go | ||
| store.go | ||
| store_test.go | ||