-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(deps): bump github.com/aws/constructs-go/constructs/v10 from 10.3.0 to 10.4.2 #8
base: main
Are you sure you want to change the base?
Conversation
Bumps [github.com/aws/constructs-go/constructs/v10](https://github.com/aws/constructs-go) from 10.3.0 to 10.4.2. - [Release notes](https://github.com/aws/constructs-go/releases) - [Commits](aws/constructs-go@constructs/v10.3.0...constructs/v10.4.2) --- updated-dependencies: - dependency-name: github.com/aws/constructs-go/constructs/v10 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
✅ Successfully planned Terraform CDK Stack 'stack'Show Plannpm warn deprecated [email protected]: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
[2024-10-15T20:25:29.429] [ERROR] default - go: downloading github.com/cdktf/cdktf-provider-local-go/local/v10 v10.1.1
go: downloading github.com/aws/constructs-go/constructs/v10 v10.4.2
go: downloading github.com/aws/jsii-runtime-go v1.103.1
[2024-10-15T20:25:29.475] [ERROR] default - go: downloading github.com/hashicorp/terraform-cdk-go/cdktf v0.20.9
[2024-10-15T20:25:29.598] [ERROR] default - go: downloading github.com/Masterminds/semver/v3 v3.3.0
stack Initializing the backend...
stack Successfully configured the backend "local"! Terraform will automatically
use this backend unless the backend configuration changes.
stack Initializing provider plugins...
- Finding hashicorp/local versions matching "2.5.2"...
stack - Installing hashicorp/local v2.5.2...
stack - Installed hashicorp/local v2.5.2 (signed by HashiCorp)
Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.
Terraform has been successfully initialized!
You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.
If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.
stack - Fetching hashicorp/local 2.5.2 for linux_amd64...
stack - Retrieved hashicorp/local 2.5.2 for linux_amd64 (signed by HashiCorp)
- Obtained hashicorp/local checksums for linux_amd64; All checksums for this platform were already tracked in the lock file
stack Success! Terraform has validated the lock file and found no need for changes.
stack Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
+ create
Terraform will perform the following actions:
stack # local_file.file (file) will be created
+ resource "local_file" "file" {
+ content = "Hello, World!"
+ content_base64sha256 = (known after apply)
+ content_base64sha512 = (known after apply)
+ content_md5 = (known after apply)
+ content_sha1 = (known after apply)
+ content_sha256 = (known after apply)
+ content_sha512 = (known after apply)
+ directory_permission = "0777"
+ file_permission = "0777"
+ filename = "hello.txt"
+ id = (known after apply)
}
Plan: 1 to add, 0 to change, 0 to destroy.
Changes to Outputs:
+ filename = "hello.txt"
─────────────────────────────────────────────────────────────────────────────
Saved the plan to: plan
To perform exactly these actions, run the following command to apply:
terraform apply "plan"
|
…cts-go/constructs/v10-10.4.2
✅ Successfully applied Terraform CDK Stack 'stack'Show Runnpm warn deprecated [email protected]: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
[2024-10-15T20:25:27.928] [ERROR] default - go: downloading github.com/cdktf/cdktf-provider-local-go/local/v10 v10.1.1
[2024-10-15T20:25:27.930] [ERROR] default - go: downloading github.com/aws/jsii-runtime-go v1.103.1
go: downloading github.com/aws/constructs-go/constructs/v10 v10.4.2
[2024-10-15T20:25:28.049] [ERROR] default - go: downloading github.com/hashicorp/terraform-cdk-go/cdktf v0.20.9
[2024-10-15T20:25:28.151] [ERROR] default - go: downloading github.com/Masterminds/semver/v3 v3.3.0
stack Initializing the backend...
stack Successfully configured the backend "local"! Terraform will automatically
use this backend unless the backend configuration changes.
stack Initializing provider plugins...
- Finding hashicorp/local versions matching "2.5.2"...
stack - Installing hashicorp/local v2.5.2...
stack - Installed hashicorp/local v2.5.2 (signed by HashiCorp)
Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.
stack Terraform has been successfully initialized!
You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.
If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.
stack - Fetching hashicorp/local 2.5.2 for linux_amd64...
stack - Retrieved hashicorp/local 2.5.2 for linux_amd64 (signed by HashiCorp)
- Obtained hashicorp/local checksums for linux_amd64; All checksums for this platform were already tracked in the lock file
stack Success! Terraform has validated the lock file and found no need for changes.
stack Terraform used the selected providers to generate the following execution plan.
Resource actions are indicated with the following symbols:
+ create
Terraform will perform the following actions:
stack # local_file.file (file) will be created
+ resource "local_file" "file" {
+ content = "Hello, World!"
+ content_base64sha256 = (known after apply)
+ content_base64sha512 = (known after apply)
+ content_md5 = (known after apply)
+ content_sha1 = (known after apply)
+ content_sha256 = (known after apply)
+ content_sha512 = (known after apply)
+ directory_permission = "0777"
+ file_permission = "0777"
+ filename = "hello.txt"
+ id = (known after apply)
}
Plan: 1 to add, 0 to change, 0 to destroy.
Changes to Outputs:
+ filename = "hello.txt"
stack local_file.file (file): Creating...
stack local_file.file (file): Creation complete after 0s [id=0a0a9f2a6772942557ab5355d76af442f8f65e01]
stack Apply complete! Resources: 1 added, 0 changed, 0 destroyed.
Outputs:
filename = "hello.txt"
stack
filename = hello.txt
|
@dependabot rebase |
Looks like this PR has been edited by someone other than Dependabot. That means Dependabot can't rebase it - sorry! If you're happy for Dependabot to recreate it from scratch, overwriting any edits, you can request |
…cts-go/constructs/v10-10.4.2
@dependabot rebase |
Looks like this PR has been edited by someone other than Dependabot. That means Dependabot can't rebase it - sorry! If you're happy for Dependabot to recreate it from scratch, overwriting any edits, you can request |
Bumps github.com/aws/constructs-go/constructs/v10 from 10.3.0 to 10.4.2.
Commits
52e7ddc
chore(release): v10.4.2e8917bc
chore(release): v10.4.106859ce
chore(release): v10.4.0427429d
chore(release): v10.3.27d4429e
chore(release): v10.3.1You can trigger a rebase of this PR by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)