generated from ministryofjustice/template-repository
-
Notifications
You must be signed in to change notification settings - Fork 289
New issue
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
Removed pinned provider version & increased max_retries for Secure Baselines #6598
Merged
richgreen-moj
merged 5 commits into
main
from
fix/remove-pinned-provider-in-secure-baselines
Mar 26, 2024
Merged
Removed pinned provider version & increased max_retries for Secure Baselines #6598
richgreen-moj
merged 5 commits into
main
from
fix/remove-pinned-provider-in-secure-baselines
Mar 26, 2024
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
richgreen-moj
had a problem deploying
to
production
March 25, 2024 11:38
— with
GitHub Actions
Failure
|
richgreen-moj
had a problem deploying
to
production
March 25, 2024 13:33
— with
GitHub Actions
Failure
richgreen-moj
had a problem deploying
to
production
March 25, 2024 13:33
— with
GitHub Actions
Failure
|
1 similar comment
|
richgreen-moj
had a problem deploying
to
production
March 25, 2024 14:47
— with
GitHub Actions
Failure
|
richgreen-moj
temporarily deployed
to
production
March 25, 2024 14:51
— with
GitHub Actions
Inactive
|
richgreen-moj
changed the title
rmv pinned provider version
Removed pinned provider version & increased max_retries for Secure Baselines
Mar 26, 2024
mikereiddigital
approved these changes
Mar 26, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lg2m
richgreen-moj
temporarily deployed
to
production
March 26, 2024 09:19
— with
GitHub Actions
Inactive
richgreen-moj
temporarily deployed
to
production
March 26, 2024 09:19
— with
GitHub Actions
Inactive
richgreen-moj
temporarily deployed
to
production
March 26, 2024 09:35
— with
GitHub Actions
Inactive
richgreen-moj
deleted the
fix/remove-pinned-provider-in-secure-baselines
branch
March 26, 2024 11:47
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.
A reference to the issue / Description of it
#6486
How does this PR fix the problem?
I've reverted the code that was pinning the version of the AWS TF provider back to
v5.38.0
The jobs are now picking up the latest version
v5.42.0
which has had an update that stops client side rate limiting which stops you getting the original error we encountered e.g.failed to get rate limit token, retry quota exceeded, 3 available, 5 requested
But we were still encountering this error e.g.
ListTagsForResource, exceeded maximum number of attempts, 25, https response error StatusCode: 400, RequestID: c17f1153-756e-4968-bd57-e38a51792366, api error ThrottlingException: Rate exceeded
There is an optional max_retries setting that can be applied to the provider so you can raise it from the default of
25
.In this PR I have set it to
100
which has been tested successfully on two subsequent runs of the scheduled baseline job.How has this been tested?
It worked ... https://github.com/ministryofjustice/modernisation-platform/actions/runs/8422101284
twice... https://github.com/ministryofjustice/modernisation-platform/actions/runs/8422873826
Checklist (check
x
in[ ]
of list items)Additional comments (if any)
This might just be a setting we keep our eye on over time as with all the scheduled baseline code which is growing as the platform grows.