Merge main into data-stream #493
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
chore(terraform): Update log retention to match GDS guidance
…ith environment configuration
feat(terraform): Add a workbook dashboard
…add-adf-to-dashboard
…dashboard FHB-1145: Add ADF to dashboard
Merge main into release-monitoring-and-alerting
…l/fh-services into merge-main-into-release-monitoring-and-alerting
…toring-and-alerting Merge main into release monitoring and alerting
Merge main into monitoring and alerting release
Merge main into monitoring and alerting release
Merge `main` into `release-monitoring-and-alerting`
…t name" This reverts commit af1e556.
FHB-1239 app gateway alerts
…-plan-alerts FHB-1240 app service plan alerts
… (average not supported)
ci(Stryker): FHB-875 - Stryker Mutator Weekly Report
…ch-ownership-and-basic-auth FHB-1295 google search ownership and basic auth
…rovider-pinning FHB-1351 Pin terraform version to 4.19.0 and fix deprecation warnings
refactor(Playwright): Basic Auth for Single Directory
[FHB-1411] Update connect email template ids as they are now in the manage gov notify service
Introduce PR checklist
* ADR for deds change
Bugfix/publish profile masking
…vements Merge `release-infrastructure-improvements` into `main`
Merge `main` into `release-monitoring-and-alerting`
This PR removes some speculative reasons from ADR027. These speculative reasons were added since the reasons why the selected option was chosen in ADR027 are unclear and not recorded in project documentation. Since the speculation would not accurately reflect the aspects considered when ADR027 was decided, Aaron and I decided it should be removed.
Merge `release-monitoring-and-alerting` into `main`
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR is to keep the data-stream branch up to date with main.
Checklist
[ ] Jira ticket ID included in the title (unless not applicable)[ ] Commit messages are short, informative and accurate. When in doubt, use [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/)[ ] Documentation related to the change has been added/updated as appropriate[ ] Changes have been given a once-over for spelling and grammar errors[ ] Tests have been added to cover any changes