cds-snc / cds-snc/github-backup
Dependency Dashboard
- Vorherrschende Sprache
- HCL
- Sterne
- 0
- Forks
- 0
- Ø Merge
- 3 T. 3 Std.
- Gemergte PRs (30 T.)
- 2
Beschreibung
This issue lists Renovate updates and detected dependencies. Read the [Dependency Dashboard](https://docs.renovatebot.com/key-concepts/dashboard/) docs to learn more.
[View this repository on the Mend.io Web Portal](https://developer.mend.io/github/cds-snc/github-backup).
## Pending Approval
The following branches are pending approval. To create them, click on a checkbox below.
- [ ] chore(deps): update actions/checkout action to v7
- [ ] chore(deps): update actions/dependency-review-action action to v5
- [ ] chore(deps): update aws-actions/configure-aws-credentials action to v6
- [ ] chore(deps): update cds-snc/terraform-plan action to v5
- [ ] chore(deps): update terraform github.com/cds-snc/terraform-modules to v11
- [ ] 🔐 **Create all pending approval PRs at once** 🔐
## Pending Status Checks
The following updates await pending status checks. To force their creation now, click on a checkbox below.
- [ ] chore(deps): update mcr.microsoft.com/devcontainers/base:bullseye docker digest to d233ca1
- [ ] chore(deps): update terraform aws to v6.64.0
- [ ] chore(deps): update terraform github.com/cds-snc/terraform-modules to v12
## Open
The following updates have all been created. To force a retry/rebase of any, click on a checkbox below.
- [ ] [chore(deps): lock file maintenance](../pull/33)
## Detected Dependencies
devcontainer (1)
.devcontainer/devcontainer.json (3)
- `mcr.microsoft.com/devcontainers/base bullseye@sha256:6c9ed5e39f498694fcd2eb2ac4a28eeea16ab0e5f6c44393d692e6cbb2eef08b` → [Updates: `bullseye`]
- `ghcr.io/devcontainers/features/aws-cli 1`
- `ghcr.io/devcontainers/features/terraform 1`
github-actions (5)
.github/workflows/dependency-review.yml (2)
- `actions/checkout v5.1.0@fbc6f3992d24b796d5a048ff273f7fcc4a7b6c09` → [Updates: `v7.0.1`]
- `actions/dependency-review-action v4.9.0@2031cfc080254a8a887f58cffee85186f0e49e48` → [Updates: `v5.0.0`].github/workflows/labels.yml (1)
- `cds-snc/labels v1`
.github/workflows/shellcheck.yml (1)
- `actions/checkout v5.1.0@fbc6f3992d24b796d5a048ff273f7fcc4a7b6c09` → [Updates: `v7.0.1`]
.github/workflows/terraform-apply.yml (3)
- `actions/checkout v5.1.0@fbc6f3992d24b796d5a048ff273f7fcc4a7b6c09` → [Updates: `v7.0.1`]
- `cds-snc/terraform-tools-setup v1.3.0@36df0d7572a15921998170395475093c183d720a`
- `aws-actions/configure-aws-credentials v5.1.1@61815dcd50bd041e203e49132bacad1fd04d2708` → [Updates: `v6.2.4`].github/workflows/terraform-plan.yml (4)
- `actions/checkout v5.1.0@fbc6f3992d24b796d5a048ff273f7fcc4a7b6c09` → [Updates: `v7.0.1`]
- `cds-snc/terraform-tools-setup v1.3.0@36df0d7572a15921998170395475093c183d720a`
- `aws-actions/configure-aws-credentials v5.1.1@61815dcd50bd041e203e49132bacad1fd04d2708` → [Updates: `v6.2.4`]
- `cds-snc/terraform-plan v3.7.0@39b0058bcf977fbd8b067b84d5a9f6165e356c32` → [Updates: `v5.0.4`]
renovate-config (1)
renovate.json
terraform (3)
terraform/iam.tf (1)
- `github.com/cds-snc/terraform-modules v11.4.7` → [Updates: `v12.0.0`]
terraform/provider.tf (1)
- `aws ~> 6.0` → [Updates: `~> 6.0`]
terraform/s3.tf (1)
- `github.com/cds-snc/terraform-modules v10.11.4` → [Updates: `v11.4.7`]
---
- [ ] Check this box to trigger a request for Renovate to run again on this repository
Beitragsleitfaden
Rechercherichtung
Beginne damit, die ausstehenden Genehmigungs- und Statusprüfungs-Einträge im Dashboard zu überprüfen, und untersuche anschließend .devcontainer/devcontainer.json, die aufgelisteten .github/workflows-Dateien sowie terraform/iam.tf, terraform/provider.tf und terraform/s3.tf. Der verknüpfte Pull Request 33 zeigt, dass die Arbeit bereits im Gange ist; für den Abschluss müssten die ausgewählten Aktualisierungen erstellt oder zusammengeführt werden und ihre Checks erfolgreich sein.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- aws, docker, github-actions, terraform
- Bereich
- cloud, devops, infrastructure
- Issue-Typ
- Refactoring
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Muss geklärt werden
- Anfängerfreundlichkeit
- 15/100