We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
While dealing with the outstanding Dependabot Pull request I found many with issues or needing advice on how to proceed.
I have created this ticket so that we can agree on a way forwad
Open Dependabots as of 31/12/24
analytical-platform:
PR#6481 : terraform(deps): Bump terraform-aws-modules/iam/aws from 5.48.0 to 5.52.0 in /terraform/aws/analytical-platform-data-production/airflow > Plan: 2 to add, 0 to change, 0 to destroy. I would have expected changes. Also Warning: Argument is deprecated
PR#6462 : terraform(deps): Bump terraform-aws-modules/s3-bucket/aws from 4.2.2 to 4.3.0 in /terraform/aws/analytical-platform-data-production/data-engineering-pipelines > Note: Objects have changed outside of Terraform 4 in total. Plan: 0 to add, 4 to change, 0 to destroy which are the objects changed outside terraform
PR#6460 : terraform(deps): Bump hashicorp/helm from 2.16.1 to 2.17.0 in /terraform/aws/analytical-platform-data-production/airflow > Plan: 2 to add, 0 to change, 0 to destroy. I would have expected changes also Warning: Argument is deprecated
PR#6436 : terraform(deps): Bump hashicorp/aws from 5.82.1 to 5.82.2 in /terraform/aws/analytical-platform-data-production/data-engineering-pipelines > Note: Objects have changed outside of Terraform 4 in total. Plan: 0 to add, 4 to change, 0 to destroy which are the objects changed outside terraform
PR#6428 : terraform(deps): Bump hashicorp/aws from 5.82.1 to 5.82.2 in /terraform/aws/analytical-platform-data-production/airflow > fails static analysis and terraform plan has 2 to add i would have expected changes also Warning: Argument is deprecated. Note This had passed static analysis until i updated the out-of-date brach to see if it helped with the terraform plan.
analytical-platform-cloud-development-environment-base: > 5 outstanding dependabot pr's multiple triviy issues
analytical-platform-jupyterlab: > 5 outstanding dependabot pr's multiple triviy issues
analytical-platform-visual-studio-code: > build fails wait for maintenance ticket ?
analytical-platform-ingestion-notify: > lambda/python from 3.12 to 3.13 how do we procceed ?
analytical-platform-ingestion-scan: > lambda/python from 3.12 to 3.13 how do we procceed ?
analytical-platform-ingestion-transfer: > lambda/python from 3.12 to 3.13 how do we procceed ?
analytical-platform-jml-report: > lambda/python from 3.12 to 3.13 how do we procceed ?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
User Story
While dealing with the outstanding Dependabot Pull request I found many with issues or needing advice on how to proceed.
I have created this ticket so that we can agree on a way forwad
Open Dependabots as of 31/12/24
analytical-platform:
PR#6481 :
terraform(deps): Bump terraform-aws-modules/iam/aws from 5.48.0 to 5.52.0 in /terraform/aws/analytical-platform-data-production/airflow > Plan: 2 to add, 0 to change, 0 to destroy. I would have expected changes. Also Warning: Argument is deprecatedPR#6462 :
terraform(deps): Bump terraform-aws-modules/s3-bucket/aws from 4.2.2 to 4.3.0 in /terraform/aws/analytical-platform-data-production/data-engineering-pipelines > Note: Objects have changed outside of Terraform 4 in total. Plan: 0 to add, 4 to change, 0 to destroy which are the objects changed outside terraformPR#6460 :
terraform(deps): Bump hashicorp/helm from 2.16.1 to 2.17.0 in /terraform/aws/analytical-platform-data-production/airflow > Plan: 2 to add, 0 to change, 0 to destroy. I would have expected changes also Warning: Argument is deprecatedPR#6436 :
terraform(deps): Bump hashicorp/aws from 5.82.1 to 5.82.2 in /terraform/aws/analytical-platform-data-production/data-engineering-pipelines > Note: Objects have changed outside of Terraform 4 in total. Plan: 0 to add, 4 to change, 0 to destroy which are the objects changed outside terraformPR#6428 :
terraform(deps): Bump hashicorp/aws from 5.82.1 to 5.82.2 in /terraform/aws/analytical-platform-data-production/airflow > fails static analysis and terraform plan has 2 to add i would have expected changes also Warning: Argument is deprecated. Note This had passed static analysis until i updated the out-of-date brach to see if it helped with the terraform plan.
analytical-platform-cloud-development-environment-base: > 5 outstanding dependabot pr's multiple triviy issues
PR#82 :
github-actions(deps): Bump super-linter/super-linter from 7.2.0 to 7.2.1PR#81 :
github-actions(deps): Bump anchore/sbom-action from 0.17.8 to 0.17.9PR#80 :
github-actions(deps): Bump ministryofjustice/github-actions from 18.5.0 to 18.6.0PR#79 :
github-actions(deps): Bump actions/attest-build-provenance from 1.4.4 to 2.1.0PR#78 :
github-actions(deps): Bump actions/attest-sbom from 1.4.1 to 2.1.0analytical-platform-jupyterlab: > 5 outstanding dependabot pr's multiple triviy issues
analytical-platform-visual-studio-code: > build fails wait for maintenance ticket ?
PR#187 :
github-actions(deps): Bump anchore/sbom-action from 0.17.8 to 0.17.9PR#186 :
github-actions(deps): Bump super-linter/super-linter from 7.2.0 to 7.2.1PR#185 :
github-actions(deps): Bump ministryofjustice/github-actions from 18.5.0 to 18.6.0PR#184 :
github-actions(deps): Bump actions/attest-build-provenance from 1.4.4 to 2.1.0PR#183 :
github-actions(deps): Bump actions/attest-sbom from 1.4.1 to 2.1.0analytical-platform-ingestion-notify: > lambda/python from 3.12 to 3.13 how do we procceed ?
PR#376 : Bump the boto group across 1 directory with 2 updatesPR#375 : Bump mypy from 1.13.0 to 1.14.1PR#365 : Bump notifications-python-client from 10.0.0 to 10.0.1PR#320 : Bump lambda/python from 3.12 to 3.13analytical-platform-ingestion-scan: > lambda/python from 3.12 to 3.13 how do we procceed ?
PR#381 : Bump the boto group across 1 directory with 2 updatesPR#377 : Bump mypy from 1.13.0 to 1.14.0PR#330 : Bump lambda/python from 3.12 to 3.13analytical-platform-ingestion-transfer: > lambda/python from 3.12 to 3.13 how do we procceed ?
PR#372 : ⬆️ Bump the boto group across 1 directory with 2 updatesPR#371 : ⬆️ Bump mypy from 1.13.0 to 1.14.1PR#322 : ⬆️ Bump lambda/python from 3.12 to 3.13analytical-platform-jml-report: > lambda/python from 3.12 to 3.13 how do we procceed ?
Definition of Done
The text was updated successfully, but these errors were encountered: