- Apr 01, 2025
-
-
Dr Abraham Martin authored
chore(deps): update dependency uis/devops/continuous-delivery/ci-templates to v6.8.0 See merge request !24
- Mar 31, 2025
-
-
UIS DevOps Renovate Bot authored
-
Dr Abraham Martin authored
chore(deps): update pre-commit hook pre-commit/pre-commit-hooks to v5 See merge request !27
-
Dr Abraham Martin authored
chore(deps): update dependency uis/devops/continuous-delivery/ci-templates to v6 See merge request !26
-
- Mar 21, 2025
-
-
UIS DevOps Renovate Bot authored
-
- Mar 06, 2025
-
-
UIS DevOps Renovate Bot authored
-
- Sep 17, 2024
-
-
Dr Rich Wareham authored
chore(deps): update Terraform `google` provider to `>= v5` See merge request !23
-
Dr Rich Wareham authored
-
Dr Rich Wareham authored
For terraform modules we generally should only ever specify *minimum* versions. From the docs[1]: > Reusable modules should constrain only their minimum allowed versions > of Terraform and providers, such as >= 0.12.0. This helps avoid known > incompatibilities, while allowing the user of the module flexibility > to upgrade to newer versions of Terraform without altering the module. [1] https://developer.hashicorp.com/terraform/language/expressions/ version-constraints#best-practices
-
- Sep 06, 2024
-
-
Roy Harrington authored
Resolve "Enable specifying monitoring_scoping_project" Closes #13 See merge request !22
- Sep 05, 2024
-
-
Dmitrii Unterov authored
-
- Aug 20, 2024
-
-
Dr Rich Wareham authored
chore(deps): update dependency uis/devops/continuous-delivery/ci-templates to v4.5.0 See merge request !21
-
UIS DevOps Renovate Bot authored
-
Dr Abraham Martin authored
See merge request !20
-
- Aug 19, 2024
-
- Aug 15, 2024
-
-
Dave Hart authored
Add `schedule_retry_config` variable that controls the configuration used to retry a scheduled job that does not complete successfully. It corresponds to the `retry_config` argument of the `google_cloud_scheduler_job` resource. Closes #15
-
- Aug 14, 2024
-
-
Dave Hart authored
Closes #16
-
- Aug 08, 2024
-
-
Dave Hart authored
Add `available_cpu` variable for specifying the number of CPUs to allocate to the Cloud Function. Add validation checks for the variables `available_cpu`, `available_memory_mb` and `timeout`. Closes #14
-
- Jul 24, 2024
-
-
Adam Deacon authored
update CI templates versions See merge request !16
- Jul 23, 2024
-
-
Dmitrii Unterov authored
-
- Jul 08, 2024
-
-
Dr Rich Wareham authored
chore: bump secret manager version number See merge request !15
-
Dr Rich Wareham authored
- Jul 04, 2024
-
-
Dr Rich Wareham authored
fix: ignore changes to docker repository See merge request !14
-
Dr Rich Wareham authored
Cloud Functions creates a docker repository for us when the function is created. It's non-trivial to get that name but ignore changes to the `docker_repository` argument so that we don't get a perma-diff.