Skip to content
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): lock file maintenance #299

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 22, 2024

This PR contains the following updates:

Update Change
lockFileMaintenance All locks refreshed

Review

  • Updates have been tested and work
  • If updates are AWS related, versions match the infrastructure (e.g. Lambda runtime, database, etc.)

🔧 This Pull Request updates lock files to use the latest dependency versions.


Configuration

📅 Schedule: Branch creation - "before 4am on Monday" in timezone America/Montreal, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 4 times, most recently from 5bf2af6 to d62d183 Compare July 30, 2024 19:28
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from 684bad2 to 6f32a9f Compare September 16, 2024 20:47
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from 90f55e3 to b4d7459 Compare September 26, 2024 14:33
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from 5be2ca7 to 588737f Compare October 1, 2024 13:00
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 4 times, most recently from 4378fbb to 7feae12 Compare October 15, 2024 18:26
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from 98ef7fd to 2c9afd8 Compare October 30, 2024 15:06
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 4 times, most recently from e680aa5 to ffc89cd Compare November 12, 2024 14:46
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from ffc89cd to 17a56d5 Compare November 13, 2024 20:55
Copy link

Plan for org_account/cost_usage_report

✅   Terraform Init: success
✅   Terraform Validate: success
✅   Terraform Format: success
❌   Terraform Plan: failed
❌   Conftest: failed

Show plan
Error: Error acquiring the state lock

Error message: operation error DynamoDB: PutItem, https response error
StatusCode: 400, RequestID:
AED4F59R1QN2Q3BN28OMKE8EVVVV4KQNSO5AEMVJF66Q9ASUAAJG,
ConditionalCheckFailedException: The conditional request failed
Lock Info:
  ID:        9733c0e8-bd6f-1300-154c-91f9336e29b9
  Path:      cds-aws-lz-production-tf/cost_usage_report/terraform.tfstate
  Operation: OperationTypePlan
  Who:       runner@fv-az735-713
  Version:   1.7.2
  Created:   2024-11-13 20:56:08.874815463 +0000 UTC
  Info:      


Terraform acquires a state lock to protect the state from being written
by multiple users at the same time. Please resolve the issue above and try
again. For most commands, you can disable locking with the "-lock=false"
flag, but this is not recommended.
time=2024-11-13T20:56:14Z level=error msg=terraform invocation failed in /home/runner/work/cds-aws-lz/cds-aws-lz/terragrunt/org_account/cost_usage_report
time=2024-11-13T20:56:14Z level=error msg=1 error occurred:
	* [/home/runner/work/cds-aws-lz/cds-aws-lz/terragrunt/org_account/cost_usage_report] exit status 1


Copy link

Plan for org_account/aft

✅   Terraform Init: success
✅   Terraform Validate: success
✅   Terraform Format: success
❌   Terraform Plan: failed
❌   Conftest: failed

Show plan
Error: Error acquiring the state lock

Error message: operation error DynamoDB: PutItem, https response error
StatusCode: 400, RequestID:
77B1KVLNBB08OUV1AV4B6RVQ5NVV4KQNSO5AEMVJF66Q9ASUAAJG,
ConditionalCheckFailedException: The conditional request failed
Lock Info:
  ID:        a3bf3f5a-d39d-c4f6-ff00-888058fdc711
  Path:      cds-aws-lz-production-tf/aft/terraform.tfstate
  Operation: OperationTypeApply
  Who:       runner@fv-az1114-447
  Version:   1.7.2
  Created:   2024-11-13 20:55:44.645764603 +0000 UTC
  Info:      


Terraform acquires a state lock to protect the state from being written
by multiple users at the same time. Please resolve the issue above and try
again. For most commands, you can disable locking with the "-lock=false"
flag, but this is not recommended.
time=2024-11-13T20:56:17Z level=error msg=terraform invocation failed in /home/runner/work/cds-aws-lz/cds-aws-lz/terragrunt/org_account/aft
time=2024-11-13T20:56:17Z level=error msg=1 error occurred:
	* [/home/runner/work/cds-aws-lz/cds-aws-lz/terragrunt/org_account/aft] exit status 1


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants