mirror of https://github.com/pulumi/pulumi.git
1103 Commits
Author | SHA1 | Message | Date |
---|---|---|---|
![]() |
6b8c85df9f |
enable thelper linter
Enable the thelper linter and add t.Helper() functions to the beginning of each test helper function. This makes the test output a bit more easy to consume. |
|
![]() |
bdebae8bb3
|
Add preview-only flag for destroy and import (#15336)
<!--- 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. --> Figured I could round out #1666 while I was in the area. Fixes #15304 Fixes #15303 Fixes #1666 ## 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. --> |
|
![]() |
0e11f91039
|
Implement preview-only refresh (#15330)
<!--- 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. --> Adds a `preview-only` flag to `pulumi refresh`. Fixes #15301 ## 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. --> |
|
![]() |
3f376fe182
|
Changelog and go.mod updates for v3.104.2 (#15344)
Co-authored-by: github-actions <github-actions@github.com> |
|
![]() |
7bb2a3c2ac
|
Auto-fix encrypted keys in the wrong format due to gocloud.dev upgrade regression (#15334)
When attempting another gocloud.dev upgrade, some users ran into a regression related to the format change of encrypted keys between gocloud versions, which part of the system was not accounting for. This PR addresses the issue and includes a fix that automatically fixes forward state that has an encrypted key in the wrong format, and includes a regression test and test for the auto-fix behavior. Fixes #15329 Co-authored-by: Thomas Gummerer <t.gummerer@gmail.com> |
|
![]() |
93d5605c28
|
Changelog and go.mod updates for v3.104.1 (#15339)
Co-authored-by: github-actions <github-actions@github.com> |
|
![]() |
d1904beb14
|
Revert gocloud.dev upgrade (#15333)
Still regressions happening associated with upgrading gocloud.dev. This reverts https://github.com/pulumi/pulumi/pull/15202. Fixes #15329 |
|
![]() |
e239dc4319
|
Changelog and go.mod updates for v3.104.0 (#15327)
Co-authored-by: github-actions <github-actions@github.com> |
|
![]() |
5457a03549
|
Allows SKIP_CHECKPOINTS without EXPERIMENTAL (#15318)
<!--- 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 This relaxes the requirement on the `PULUMI_SKIP_CHECKPOINTS` env var to also have `PULUMI_EXPERIMENTAL` set. Because `PULUMI_EXPERIMENTAL` introduces other behavior, this decouples the `PULUMI_SKIP_CHECKPOINTS` behavior from that. <!--- Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. --> ## 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> Co-authored-by: Fraser Waters <fraser@pulumi.com> |
|
![]() |
afb287d2fb
|
Rename filestate to DIY (#15314)
This goes through the codebase to try and be consistent about names for the diy/filestate/local/selfmanaged backend. Every reference to this backend should now use the terms "DIY". There are a couple of places that still say "local DIY backend" this is referring to a DIY backend using the local filesystem (i.e. `pulumi login --local`). |
|
![]() |
1b2fb8ee39
|
Fix flakey test (#15311)
TestPreviewImportFile could fail if the two resources registered in the opposite order to what the test expected. https://github.com/pulumi/pulumi/actions/runs/7708946353/job/21009583196 This fixes the resources to always register in the same order via a `dependsOn` option, and then fixes the test to pass for that ordering. |
|
![]() |
fd4ed7f811
|
add tests for aws and gcp (#15291)
Fixes https://github.com/pulumi/pulumi/issues/3760 ## 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. --> - [ ] 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. --> |
|
![]() |
7ba0541e1c
|
Rename self-managed to diy-backend (#15268)
<!--- 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. --> We're moving away from referring to filestate as "self managed" backends, preferring to refer to this as "DIY" backends going forward. ## 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. --> - [ ] 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. --> |
|
![]() |
927b7efef5
|
upgrade gocloud.dev take 2 (#15202)
Another attempt at upgrading gocloud.dev to the latest version. We've identified and added tests for the issues that came up in the last attempt to do the upgrade in https://github.com/pulumi/pulumi/pull/15161 and https://github.com/pulumi/pulumi/pull/15187. The problem with the SAS key appears to have been fixed in gocloud.dev 0.36.0 (The previous upgrade tried 0.28.0), and I've added additional fixes for the azure key vault problem during pulumi refresh in this PR. This needs https://github.com/pulumi/pulumi/pull/15161 to be merged first, but I wanted to open a PR in the meantime. Fixes #15138 Fixes https://github.com/pulumi/pulumi/issues/14647 Fixes https://github.com/pulumi/pulumi/issues/13161 Fixes https://github.com/pulumi/pulumi/issues/14431 Fixes https://github.com/pulumi/pulumi/issues/14541 ## Checklist - [x] I have run `make tidy` to update any new dependencies - [ ] 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. --> |
|
![]() |
d446736e59
|
Unskip tests (#15257)
- Unskip Python tests that needed to be skipped until v3.103.0 of the `pulumi` PyPi package was released with support for Python 3.12. - Unskip Node.js test that needed to be skipped until v3.103.1 of the `@pulumi/pulumi` NPM package was published with a fix for the semver type issue. Fixes #15195 |
|
![]() |
7ff579f95d
|
Changelog and go.mod updates for v3.103.1 (#15256)
Co-authored-by: github-actions <github-actions@github.com> |
|
![]() |
db0bcc2d9f
|
Changelog and go.mod updates for v3.103.0 (#15248)
Co-authored-by: github-actions <github-actions@github.com> |
|
![]() |
7309681b5b
|
Support Python 3.12 (#15190)
Python 3.12 requires `grpcio` 1.59.0 or higher. Unfortunately, there is a regression in `grpcio` 1.58.0 through the latest version (currently 1.60.0) which causes any error returned from a Python gRPC server to be written to stderr, including UNIMPLEMENTED errors. This primarily affects Python dynamic providers, which don't have implementations for `CheckConfig` and `DiffConfig`, resulting in a traceback error being emitted to stderr when the engine calls these, which is visible to users. This `grpcio` regression has been fixed upstream, but the fix has not been released yet. We've been waiting for a 1.60.1 patch release. This has not been great for our Python users who are using Python 3.12. It's particularly bad for new Pulumi users who are using Python 3.12 and are trying to get started with Pulumi. For these users, when trying to install the `pulumi` PyPi package (i.e. via `pulumi new python`) the installation fails with an error because it is pinned to depending on an older version of `grpcio` which doesn't work on Python 3.12. This commit works around the problem by providing default implementations of `CheckConfig` and `DiffConfig` for python dynamic providers and the component provider API, so that no error is emitted to stderr when the engine calls these methods. The default implementations for these are the same behavior that the engine would use if these methods had returned UNIMPLEMENTED. I believe these are the only two methods affected by this. Other methods like `Invoke`, `Call`, `StreamInvoke`, `Construct`, `Attach`, `GetMapping`, and `GetMappings`, continue to return UNIMPLEMENTED for dynamic providers, which I think is OK; I don't believe these will be called by the engine under normal circumstances. Out of an abundance of caution, the `pulumi` package continues to depend on the pinned version of `grpcio` when installing on versions of Python less than 3.12. On Python 3.12 or greater, we now depend on `grpcio` `~=1.60.0`. 1.60.0 doesn't have the fix for the regression, but the workaround should allow things to work on Python 3.12 as before. Once 1.60.1 is released, we can look into updating the `grpcio` dependency to `~=1.60.1` for all versions of Python, and possibly revert the workarounds, if we want. Note: #14474 added a test for dynamic providers to ensure nothing is written to stderr. The test would fail if the workaround in this PR did not work as intended: https://github.com/pulumi/pulumi/pull/14474/files#diff-d92ccd283e08eadab2597825103e45cdaa96fea93324bc4d4d3b1d2b83c51b76 This PR depends on several other smaller PRs: - https://github.com/pulumi/pulumi/pull/15220 - https://github.com/pulumi/pulumi/pull/15221 - https://github.com/pulumi/pulumi/pull/15222 - https://github.com/pulumi/pulumi/pull/15223 - https://github.com/pulumi/pulumi/pull/15224 - https://github.com/pulumi/pulumi/pull/15225 - https://github.com/pulumi/pulumi/pull/15226 Fixes #14258 |
|
![]() |
fd7a9a88c0
|
[tests/integration] Remove `pulumi` from `requirements.txt` (#15226)
In preparation for supporting Python 3.12... These tests have a `requirements.txt` file that depends on the released version of the `pulumi` package, but that package depends on the old `grpcio` package that does not work Python 3.12. Note that `ProgramTest` first installs `requirements.txt` in the virtual environment it creates, then it installs any local dependencies specified via `ProgramTestOptions.Dependencies`. To make these tests work on Python 3.12, remove `pulumi` from `requirements.txt`. After we publish a new `pulumi` package that supports Python 3.12, we could consider reverting this change. Aside: I considered changing `ProgramTest` to install `ProgramTestOptions.Dependencies` deps _before_ `requirements.txt` deps. That would avoid the need to change these `requirements.txt` files and would work for the most part. If the version specified in `requirements.txt` is satisfied by the already installed local version, then pip doesn't install the version from `requirements.txt`. Where this doesn't work is if `requirements.txt` specifies an older version range. Then the local dependency would be uninstalled and the older version from `requirements.txt` would be installed. Which isn't the behavior we want. And there's very likely `requirements.txt` files in other repos in this situation (there were even some in this PR that depend on v2.x!) and I didn't want to change the behavior for those. We'd have to make it an opt-in `ProgramTestOptions` option. It seemed simpler to just modify these `requirements.txt` files. Note: The change to `tests/integration/python/stack_truncate/main_dir_specified/bar/requirements.txt` depends on https://github.com/pulumi/pulumi/pull/15225. It's going to fail without that change. |
|
![]() |
e9ac6f3c9c
|
[tests/integration] Fix `resource_args` for Python 3.12 (#15224)
In preparation for supporting Python 3.12... This test is generating a local example library using SDKgen and then running a program that uses it. When running on Python 3.12, without this fix, we get an error from the generated example library's `_utilities.py` file: ``` ModuleNotFoundError: No module named 'pkg_resources' ``` This is because `_utilities.py` depends on `pkg_resources` from `setuptools`, but our generated provider SDKs do not specify they have a dependency on `setuptools`. The problem on Python 3.12 is because virtual environments created with `python -m venv` no longer include `setuptools` in the virtual environment (https://github.com/python/cpython/issues/95299). This generally isn't a problem with projects created using `pulumi new` because we will explicitly install `setuptools` in the created virtual environment. But it is a problem in this case, because `ProgramTest` is creating the virtual environment, and it doesn't install setuptools in it. To workaround, for now, include `setuptools` in the test program's `requirements.txt`. When we fix Python SDKgen to no longer use `pkg_resources`, we can remove `setuptools` from the test program's `requirements.txt` (https://github.com/pulumi/pulumi/issues/12414). Also remove the `pulumi` dependency in `requirements.txt` as it the currently published package can't be installed on Python 3.12 due to the dependency on `grpcio` that doesn't work on Python 3.12. The test installs the locally built Python SDK, so it's not needed in `requirements.txt` anyway. Aside: This test really should be a runtime SDKgen test, which wouldn't have this problem because it uses the CLI's code for creating the virtual environment, which installs `setuptools`. Also note: While looking at this test, I cleaned up a part of the test that was replacing `${VERSION}` in the generated library's `setup.py`, which is no longer necessary because that's not how the version is replaced anymore. A default placeholder version is included that will work as-is. |
|
![]() |
0eededec61
|
generate unique stack names for tests (#15230)
Tests can run in parallel, e.g. on different PRs/same tests on different platforms, and if a single test gets killed by the CI runner without cleaning up all future tests will fail if the stack name is not unique. Make sure the stack name is unique to avoid these failures. I a CI failure that's `error: stack 'organization/project/testing' already exists`. This PR should hopefully fix it. ## 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. --> - [ ] 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. --> |
|
![]() |
2371602aef
|
Upgrade pulumi-yaml to 1.5.0 (#15214)
Upgrade pulumi-yaml to the latest version, which includes https://github.com/pulumi/pulumi-yaml/pull/546 |
|
![]() |
c71f001e39
|
Add azure login test (#15161)
# Description This is quite an awkward test because it depends on a secret from the environment. However I don't really know how to do this otherwise since we do need this SAS token, and that's a secret we need, so we have to inject it through the environment. /xref #15138 ## 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. --> - [ ] 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. --> |
|
![]() |
a49ea379de
|
Changelog and go.mod updates for v3.102.0 (#15182)
Co-authored-by: github-actions <github-actions@github.com> |
|
![]() |
31c90fd0e0
|
[python/sdk] Allow remote components to use output property called id (#15115)
# Description This PR updates the python SDK to allow remote components to have ID property. Adds an integration test which implements a component that had an output property `id` to ensure that we can have `id` as an output that doesn't get filtered out when serializing and deserializing property maps. Component instantiation looks like this in python ```python import pulumi from component import Component component_a = Component("a", id="hello") pulumi.export("id", component_a.id) ``` Where we expect `component_a.id` to equal `"{resource.ID}-{args.Id}" => "42-hello"` and the 42 is the (constant) ID of the resource created inside the component. ## Checklist - [ ] 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. --> |
|
![]() |
3be1b6289c
|
Remove deprecated Protobufs imports (#15158)
<!--- 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. --> github.com/golang/protobuf is marked deprecated and I was getting increasingly triggered by the inconsistency of importing the `Empty` type from "github.com/golang/protobuf/ptypes/empty" or "google.golang.org/protobuf/types/known/emptypb" as "pbempty" or "empty" or "emptypb". Similar for the struct type. So this replaces all the Protobufs imports with ones from "google.golang.org/protobuf", normalises the import name to always just be the module name (emptypb), and adds the depguard linter to ensure we don't use the deprecated package anymore. ## 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. --> - [ ] 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. --> |
|
![]() |
72bddd809f
|
Update github.com/cloudflare/circl to v1.3.7 (#15151)
<!--- 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. --> Dependabot updated some references to this in https://github.com/pulumi/pulumi/pull/15131. But missed a lot, importantly it didn't update pkg or sdk which are the most important modules in this repo. ## Checklist - [x] I have run `make tidy` to update any new dependencies - [ ] 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. --> - [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. --> |
|
![]() |
bd93fcf91a
|
Bump the go_modules group across 29 directories with 1 update (#15131)
Bumps the go_modules group with 1 update in the /cmd/pulumi-test-language directory: [github.com/cloudflare/circl](https://github.com/cloudflare/circl). Bumps the go_modules group with 1 update in the /sdk/go/pulumi-language-go directory: [github.com/cloudflare/circl](https://github.com/cloudflare/circl). Bumps the go_modules group with 1 update in the /sdk/nodejs/cmd/pulumi-language-nodejs directory: [github.com/cloudflare/circl](https://github.com/cloudflare/circl). Bumps the go_modules group with 1 update in the /sdk/python/cmd/pulumi-language-python directory: [github.com/cloudflare/circl](https://github.com/cloudflare/circl). Bumps the go_modules group with 1 update in the /tests directory: [github.com/cloudflare/circl](https://github.com/cloudflare/circl). Bumps the go_modules group with 1 update in the /tests/benchmarks/go-alias-norm directory: [github.com/cloudflare/circl](https://github.com/cloudflare/circl). Bumps the go_modules group with 1 update in the /tests/integration/about/go directory: [github.com/cloudflare/circl](https://github.com/cloudflare/circl). Bumps the go_modules group with 1 update in the /tests/integration/config_basic/go directory: [github.com/cloudflare/circl](https://github.com/cloudflare/circl). Bumps the go_modules group with 1 update in the /tests/integration/config_missing/go directory: [github.com/cloudflare/circl](https://github.com/cloudflare/circl). Bumps the go_modules group with 1 update in the /tests/integration/config_secrets_warn/go directory: [github.com/cloudflare/circl](https://github.com/cloudflare/circl). Bumps the go_modules group with 1 update in the /tests/integration/construct_component/go directory: [github.com/cloudflare/circl](https://github.com/cloudflare/circl). Bumps the go_modules group with 1 update in the /tests/integration/construct_component_configure_provider/testcomponent-go directory: [github.com/cloudflare/circl](https://github.com/cloudflare/circl). Bumps the go_modules group with 1 update in the /tests/integration/construct_component_methods/go directory: [github.com/cloudflare/circl](https://github.com/cloudflare/circl). Bumps the go_modules group with 1 update in the /tests/integration/construct_component_methods_errors/go directory: [github.com/cloudflare/circl](https://github.com/cloudflare/circl). Bumps the go_modules group with 1 update in the /tests/integration/construct_component_methods_provider/go directory: [github.com/cloudflare/circl](https://github.com/cloudflare/circl). Bumps the go_modules group with 1 update in the /tests/integration/construct_component_methods_resources/go directory: [github.com/cloudflare/circl](https://github.com/cloudflare/circl). Bumps the go_modules group with 1 update in the /tests/integration/construct_component_methods_unknown/go directory: [github.com/cloudflare/circl](https://github.com/cloudflare/circl). Bumps the go_modules group with 1 update in the /tests/integration/construct_component_output_values/go directory: [github.com/cloudflare/circl](https://github.com/cloudflare/circl). Bumps the go_modules group with 1 update in the /tests/integration/construct_component_plain/go directory: [github.com/cloudflare/circl](https://github.com/cloudflare/circl). Bumps the go_modules group with 1 update in the /tests/integration/construct_component_provider/go directory: [github.com/cloudflare/circl](https://github.com/cloudflare/circl). Bumps the go_modules group with 1 update in the /tests/integration/construct_component_provider_explicit/go directory: [github.com/cloudflare/circl](https://github.com/cloudflare/circl). Bumps the go_modules group with 1 update in the /tests/integration/construct_component_provider_propagation/go directory: [github.com/cloudflare/circl](https://github.com/cloudflare/circl). Bumps the go_modules group with 1 update in the /tests/integration/construct_component_resource_options/go directory: [github.com/cloudflare/circl](https://github.com/cloudflare/circl). Bumps the go_modules group with 1 update in the /tests/integration/construct_component_unknown/go directory: [github.com/cloudflare/circl](https://github.com/cloudflare/circl). Bumps the go_modules group with 1 update in the /tests/integration/construct_nested_component/go directory: [github.com/cloudflare/circl](https://github.com/cloudflare/circl). Bumps the go_modules group with 1 update in the /tests/integration/deleted_with/go directory: [github.com/cloudflare/circl](https://github.com/cloudflare/circl). Bumps the go_modules group with 1 update in the /tests/integration/rotate_passphrase directory: [github.com/cloudflare/circl](https://github.com/cloudflare/circl). Bumps the go_modules group with 1 update in the /tests/integration/state_rename_parent directory: [github.com/cloudflare/circl](https://github.com/cloudflare/circl). Updates `github.com/cloudflare/circl` from 1.3.3 to 1.3.7 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/cloudflare/circl/releases">github.com/cloudflare/circl's releases</a>.</em></p> <blockquote> <h2>CIRCL v1.3.7</h2> <h3>What's Changed</h3> <ul> <li>build(deps): bump golang.org/x/crypto from 0.3.1-0.20221117191849-2c476679df9a to 0.17.0 by <a href="https://github.com/dependabot"><code>@dependabot</code></a> in <a href="https://redirect.github.com/cloudflare/circl/pull/467">cloudflare/circl#467</a></li> <li>kyber: remove division by q in ciphertext compression by <a href="https://github.com/bwesterb"><code>@bwesterb</code></a> in <a href="https://redirect.github.com/cloudflare/circl/pull/468">cloudflare/circl#468</a></li> <li>Releasing CIRCL v1.3.7 by <a href="https://github.com/armfazh"><code>@armfazh</code></a> in <a href="https://redirect.github.com/cloudflare/circl/pull/469">cloudflare/circl#469</a></li> </ul> <h3>New Contributors</h3> <ul> <li><a href="https://github.com/dependabot"><code>@dependabot</code></a> made their first contribution in <a href="https://redirect.github.com/cloudflare/circl/pull/467">cloudflare/circl#467</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/cloudflare/circl/compare/v1.3.6...v1.3.7">https://github.com/cloudflare/circl/compare/v1.3.6...v1.3.7</a></p> <h2>CIRCL v1.3.6</h2> <h3>What's Changed</h3> <ul> <li>internal: add TurboShake{128,256} by <a href="https://github.com/bwesterb"><code>@bwesterb</code></a> in <a href="https://redirect.github.com/cloudflare/circl/pull/430">cloudflare/circl#430</a></li> <li>Kangaroo12 draft -10 by <a href="https://github.com/bwesterb"><code>@bwesterb</code></a> in <a href="https://redirect.github.com/cloudflare/circl/pull/431">cloudflare/circl#431</a></li> <li>Add K12 as XOF by <a href="https://github.com/bwesterb"><code>@bwesterb</code></a> in <a href="https://redirect.github.com/cloudflare/circl/pull/437">cloudflare/circl#437</a></li> <li>xof/k12: Fix a typo in the package documentation by <a href="https://github.com/cjpatton"><code>@cjpatton</code></a> in <a href="https://redirect.github.com/cloudflare/circl/pull/438">cloudflare/circl#438</a></li> <li>Set CIRCL version for generated assembler code. by <a href="https://github.com/armfazh"><code>@armfazh</code></a> in <a href="https://redirect.github.com/cloudflare/circl/pull/440">cloudflare/circl#440</a></li> <li>Add tkn20 benchmarks by <a href="https://github.com/tanyav2"><code>@tanyav2</code></a> in <a href="https://redirect.github.com/cloudflare/circl/pull/442">cloudflare/circl#442</a></li> <li>Add partially blind RSA implementation by <a href="https://github.com/chris-wood"><code>@chris-wood</code></a> in <a href="https://redirect.github.com/cloudflare/circl/pull/445">cloudflare/circl#445</a></li> <li>Update doc.go by <a href="https://github.com/nadimkobeissi"><code>@nadimkobeissi</code></a> in <a href="https://redirect.github.com/cloudflare/circl/pull/447">cloudflare/circl#447</a></li> <li>tss/rsa: key generation for threshold RSA (safe primes) by <a href="https://github.com/armfazh"><code>@armfazh</code></a> in <a href="https://redirect.github.com/cloudflare/circl/pull/450">cloudflare/circl#450</a></li> <li>Bumping Go version for CI jobs. by <a href="https://github.com/armfazh"><code>@armfazh</code></a> in <a href="https://redirect.github.com/cloudflare/circl/pull/457">cloudflare/circl#457</a></li> <li>Spelling by <a href="https://github.com/jsoref"><code>@jsoref</code></a> in <a href="https://redirect.github.com/cloudflare/circl/pull/456">cloudflare/circl#456</a></li> <li>blindrsa: updating blindrsa to be compliant with RFC9474 by <a href="https://github.com/armfazh"><code>@armfazh</code></a> in <a href="https://redirect.github.com/cloudflare/circl/pull/464">cloudflare/circl#464</a></li> <li>Releasing CIRCL v1.3.6 by <a href="https://github.com/armfazh"><code>@armfazh</code></a> in <a href="https://redirect.github.com/cloudflare/circl/pull/465">cloudflare/circl#465</a></li> </ul> <h3>New Contributors</h3> <ul> <li><a href="https://github.com/nadimkobeissi"><code>@nadimkobeissi</code></a> made their first contribution in <a href="https://redirect.github.com/cloudflare/circl/pull/447">cloudflare/circl#447</a></li> <li><a href="https://github.com/jsoref"><code>@jsoref</code></a> made their first contribution in <a href="https://redirect.github.com/cloudflare/circl/pull/456">cloudflare/circl#456</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/cloudflare/circl/compare/v1.3.3...v1.3.6">https://github.com/cloudflare/circl/compare/v1.3.3...v1.3.6</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href=" |
|
![]() |
664b1b9ca5
|
Changelog and go.mod updates for v3.101.1 (#15134)
Co-authored-by: github-actions <github-actions@github.com> |
|
![]() |
c48ed3ba49
|
Revert "upgrade gocloud.dev to latest version" (#15128)
Reverts pulumi/pulumi#15011 /xref https://github.com/pulumi/pulumi/issues/15126 /xref https://github.com/pulumi/pulumi/issues/15127 |
|
![]() |
b37906a1cd
|
Changelog and go.mod updates for v3.101.0 (#15123)
Co-authored-by: github-actions <github-actions@github.com> |
|
![]() |
6c7bb23a70
|
Changelog and go.mod updates for v3.100.0 (#15057)
Co-authored-by: github-actions <github-actions@github.com> Co-authored-by: Justin Van Patten <jvp@justinvp.com> |
|
![]() |
d7b1a1d9b1
|
upgrade gocloud.dev to latest version (#15011)
Upgrade gocloud.dev to the latest version. This requires a bit of a workaround, since `gocloud.dev` changed its expectations how the encryption key is stored for Azure. In v0.27.0 and earlier, gocloud.dev accepted an encryption key that was wrapped in base64.RawURLEncoding (and produced one that was wrapped as such. However in v0.28.0 that changed and the encryption key was no longer wrapped in gocloud.dev, and as such it also didn't expect a wrapped key anymore . To keep compatibility we'll keep wrapping the azure key for gocloud.dev in an inner encoding, which seems to be the path of least resistance. Alternatively we could introduce a `v2` encoding by prefixing the string, but that ends up being messier than just keeping the strings compatible. ## 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. --> Tests were introduced in https://github.com/pulumi/pulumi/pull/14649, I've updated them slightly to cover the new code as well. - [ ] 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. --> |
|
![]() |
40b45ecc85
|
Add test for azure secrets (#14649)
Add a test showing the problems we ran into when upgrading from gocloud.dev 0.27.0 to 0.28.0 and 0.29.0. It's a little bit awkward, since the issue only happens when upgrading form an encrypted key generated with the old version of gocloud.dev to a newer version of gocloud.dev. Fixes https://github.com/pulumi/pulumi/issues/11986 --------- Co-authored-by: Thomas Gummerer <t.gummerer@gmail.com> |
|
![]() |
37e6ad44d0
|
Upgrade go-git to v5.11.0 (#15013)
Bumps github.com/go-git/go-git/v5 to 5.11.0 to address https://github.com/go-git/go-git/security/advisories/GHSA-mw99-9chc-xw7r Co-authored-by: Roy Reznik <roy@wiz.io> |
|
![]() |
c07baf6f3b
|
Upgrade pulumi-java and pulumi-yaml (#15007)
Upgrade pulumi-java to v0.9.9 and upgrade pulumi-yaml to v1.4.5. |
|
![]() |
ed92af8a5e
|
Changelog and go.mod updates for v3.99.0 (#14978)
Co-authored-by: github-actions <github-actions@github.com> |
|
![]() |
3560333ae6
|
Clean up uses of .Error() (#14965)
Combination of a few cleanups. 1. Don't call .Error() on errors that are being passed to "%s" format functions. Format will call `Error()` itself. 2. Don't call assert.Error then assert.Equal/Contains, just use assert.ErrorEqual/ErrorContains instead. 3. Use "%w" if appropriate, instead of "%v"/"%s". |
|
![]() |
58248fada6
|
Upgrade pulumi-yaml to 1.4.4 (#14963)
Upgrade `pulumi-yaml` to the latest version, which includes https://github.com/pulumi/pulumi-yaml/pull/533. |
|
![]() |
53244f09ae
|
Bump golang.org/x/crypto to 0.17.0 (#14962)
Bumps [golang.org/x/crypto](https://github.com/golang/crypto) to 0.17.0. Replaces all the dependabot PRs in the repo with this single PR. Also bumped `github.com/pulumi/pulumi/sdk/v3` in `tests/integration/transformations/go/simple/go.mod` from v3.97.0 to v3.98.0 to use esc v0.6.1, and avoid the appdash issue. |
|
![]() |
9853228bc9
|
Update esc to v0.6.2 (#14960)
Update to the latest version of esc. |
|
![]() |
bfa0ad15bf
|
Changelog and go.mod updates for v3.98.0 (#14951)
Co-authored-by: github-actions <github-actions@github.com> |
|
![]() |
b0c276ece0
|
Update esc to v0.6.1 (#14939)
First step in addressing https://github.com/pulumi/pulumi/issues/14873 Note: I suspect I'll need to temporarily disable some codegen tests to get this merged, and then once we release v3.98.0 and the next version of esc, we can re-enable. |
|
![]() |
97d94658c1
|
Refactor transformation tests and add Go test (#14851)
This removes the dynamic resources from the transformation tests and just uses the testprovider instead. As such we can now also write the Go transform test in pretty much exactly the same way in the same place. I've removed the golang_sdk test from lifecycletest has it's now covered by this integration test. |
|
![]() |
810367c1a2
|
Add LogicalName to import system (#14745)
<!--- 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. --> Fixes https://github.com/pulumi/pulumi/issues/14618. This adds a new field to the import file "logicalName", which if set is used as the logical name (https://www.pulumi.com/docs/concepts/resources/names/#logicalname) of the resource. The original "name" field is then used just for codegen purposes (i.e. the source name). If either field is not set then the other field is used to fill it in. If neither field is set it's an error. Further the import system _no longer_ renames resources to try and make unique names, but it also no longer errors just because two resources of different types have the same name. The rules for uniqueness now match what's valid when writing a Pulumi program, but it is the users responsibility to make names unique and the import system will error if you try to import two resources that would end up with the same URN. ## 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. --> |
|
![]() |
797ab3d099
|
Replace some more uses of assert.Contains(err.Error()) with assert.ErrorContains (#14863) | |
![]() |
35757a1a9d
|
Changelog and go.mod updates for v3.97.0 (#14853)
Co-authored-by: github-actions <github-actions@github.com> |
|
![]() |
05f64755af
|
Split up acceptance tests (#14830)
See if this helps with windows job timeouts. |
|
![]() |
9ee43459c2
|
Changelog and go.mod updates for v3.96.2 (#14809)
Co-authored-by: github-actions <github-actions@github.com> |
|
![]() |
3fdf871124
|
Use the yaml converter plugin rather than Eject (#14437)
<!--- 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. --> We add some hooks to ensure we always use the version of pulumi-converter-yaml that matches the version of yaml we've linked the CLI to, this preserves the behaviour we have today that eject code matches the gen code. At some point it will make sense to decouple these and often just default to the the latest converter instead. This unlinks one part of the yaml codebase from the cli. We still need to do codegen and docgen, but this at least means breaking changes can be made to the eject interface without breaking the build because of the circular dependency cycle. ## 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 - Covered by `TestYamlConvertSmoke` <!--- 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. --> |