Improve stability and functionality of self-managed state backends
This epic tracks overall improvements to non-Pulumi Console [backends](https://www.pulumi.com/docs/intro/concepts/state/) to make them more reliable and feature-complete. - [ ] #2055 Fix code duplication between httpstate and filestate backends - [x] #2522 Project name in stack identity inconsistent between backends - [ ] #2801 Failed to load checkpoint after write failure to S3 backend - [x] #2814 Using S3 backend with multiple projects is unpleasant - [ ] #2996 Feature request: persist the filestate backend URL in Pulumi.<stackname>.yaml - [x] #3194 Specifying an incorrect API service backend for pulumi login results in a confusing error message - [x] #3395 StackReference doesn't support multiple backends - [ ] #3683 Be able to move/transfer a stack from a backend to another - [ ] #3714 [bug] s3 backend deletes state early and then tries to JSON parse html - [ ] #3760 Add test coverage for all supported filestate backends - [x] #3120 Simple project support for local backends - [ ] #2058 Feature: Store release history in Kubernetes using CRDs - [ ] #4665 Support configuration for pluggable backends and secrets providers - [ ] #4679 S3 state provider will remove stack data on connection lost while `pulumi up` - [ ] #5036 Concurrent Stack Updates Results in Reference Error with s3 Backend - [ ] https://github.com/pulumi/pulumi-az-pipelines-task/issues/47 Read backend config from Pulumi.yaml - [ ] #6074 Pulumi eats bandwidth (when using S3 backend) - [ ] #8571 Don't touch loca
Posted by leezen on May 11, 2020, 4:58 AM
Tags
Related issues
Raise real-world problems, find people facing the same issue, and discuss solutions.3,500 issues0 comments
support (Sysadmin)
Support connecting to remote devcontainers (devcontainer on remote host)
Option to use Waffle menu or links displayed normally
I also attempted to package ROCM on musl.
But why is there no such pushback agains linux kernel?
OpenCode Support
Upcoming changes to the tado° API
Allow Mac users to use Apple native containerization
Support for the Containerization Framework on macOS
Improve stability and functionality of self-managed state backends
This epic tracks overall improvements to non-Pulumi Console [backends](https://www.pulumi.com/docs/intro/concepts/state/) to make them more reliable and feature-complete. - [ ] #2055 Fix code duplication between httpstate and filestate backends - [x] #2522 Project name in stack identity inconsistent between backends - [ ] #2801 Failed to load checkpoint after write failure to S3 backend - [x] #2814 Using S3 backend with multiple projects is unpleasant - [ ] #2996 Feature request: persist the filestate backend URL in Pulumi.<stackname>.yaml - [x] #3194 Specifying an incorrect API service backend for pulumi login results in a confusing error message - [x] #3395 StackReference doesn't support multiple backends - [ ] #3683 Be able to move/transfer a stack from a backend to another - [ ] #3714 [bug] s3 backend deletes state early and then tries to JSON parse html - [ ] #3760 Add test coverage for all supported filestate backends - [x] #3120 Simple project support for local backends - [ ] #2058 Feature: Store release history in Kubernetes using CRDs - [ ] #4665 Support configuration for pluggable backends and secrets providers - [ ] #4679 S3 state provider will remove stack data on connection lost while `pulumi up` - [ ] #5036 Concurrent Stack Updates Results in Reference Error with s3 Backend - [ ] https://github.com/pulumi/pulumi-az-pipelines-task/issues/47 Read backend config from Pulumi.yaml - [ ] #6074 Pulumi eats bandwidth (when using S3 backend) - [ ] #8571 Don't touch loca
Comments (0)
No comments yet. Start the discussion.