Enable specifying monitoring_scoping_project

The Cloud Run module has a monitoring_scoping_project variable which can be used to set the project for alerting policies to match the alerting notification channels and thereby no-longer need the google.monitoring provider.

Implement a similar strategy in this module for consistency. This will be a breaking change.

added teamCloud label

added meetingbacklog refinement label

added workflowNeeds Refinement label

removed meetingbacklog refinement label

added priority2 Medium workflowbacklog labels and removed workflowNeeds Refinement label

changed iteration to Cloud Team Sprints Aug 28, 2024 - Sep 10, 2024

https://gitlab.developers.cam.ac.uk/uis/devops/apsua/infrastructure/-/issues/3 was raised on the APSUA Cloud Infrastructure project because of this issue remaining unresolved. We should probably increase the priority of this issue so that future projects that use the GCP Scheduled Script module don't run into the same problem

assigned to @du228

mentioned in merge request !22 (merged)

added workflowReview Required label and removed workflowbacklog label

mentioned in commit 90c5ec57

closed with merge request !22 (merged)

added workflowDone label and removed workflowReview Required label

reopened

added workflowNeeds Deployment label and removed workflowDone label

Release-it failed on merge https://gitlab.developers.cam.ac.uk/uis/devops/infra/terraform/gcp-scheduled-script/-/jobs/1692798

🚀 Let's release gcp-scheduled-script (3.4.2...4.0.0)
Changelog:
## [4.0.0](https://gitlab.developers.cam.ac.uk/uis/devops/infra/terraform/gcp-scheduled-script/compare/3.4.2...4.0.0) (2024-09-06)
### ⚠ BREAKING CHANGES
* remove separate monitoring provider configuration
### Features
* remove separate monitoring provider configuration ([f782261](https://gitlab.developers.cam.ac.uk/uis/devops/infra/terraform/gcp-scheduled-script/commit/f78226184df3e7aefd8fd28619f9bb630e2bf5af))
Changeset:
 M CHANGELOG.md
- Git commit
✔ Git commit
- Git tag
✔ Git tag
- Git push
Rolling back remote tag push 4.0.0
WARNING An error was encountered when trying to rollback the tag on the remote: error: unable to delete '4.0.0': remote ref does not exist
error: failed to push some refs to 'https://gitlab.developers.cam.ac.uk/uis/devops/infra/terraform/gcp-scheduled-script.git'
✖ Git push
ERROR remote: GitLab: You are not allowed to push code to protected branches on this project.
To https://gitlab.developers.cam.ac.uk/uis/devops/infra/terraform/gcp-scheduled-script.git
 ! [remote rejected] master -> master (pre-receive hook declined)
 ! [remote rejected] 4.0.0 -> 4.0.0 (pre-receive hook declined)
error: failed to push some refs to 'https://gitlab.developers.cam.ac.uk/uis/devops/infra/terraform/gcp-scheduled-script.git'
Rolling back changes...
Deleting local tag 4.0.0
Resetting local changes made

In case this wasn't fixed. It looks like sometimes the branch protection rule lacks the appropriate bot's permission. I'm not 100% sure what actually is supposed to set the rule but when it isn't set, release-it complains as you've noticed.

Yes, I had to add the bot user to the list of "who can push to protected branch" or something like this last time.

closed