Ltd 4311 cflinuxfs4 #212
Merged
Ltd 4311 cflinuxfs4 #212
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
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #212 +/- ##
=======================================
Coverage 79.82% 79.82%
=======================================
Files 53 53
Lines 3137 3137
Branches 436 436
=======================================
Hits 2504 2504
Misses 535 535
Partials 98 98 ☔ View full report in Codecov by Sentry. |
saruniitr
approved these changes
Oct 30, 2023
This is to upgrade to this particular stack before gov paas forcibly upgrades for us in November
kevincarrogan
force-pushed
the
LTD-4311-cflinuxfs4
branch
from
7dd2af7 to
6b584df
Compare
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.
This explicitly sets the version for the cf stack in preparation for the cflinuxfs4 upgrade.
This is currently the implicit version but once we upgrade the stack version these change becomes "sticky" and means that even if we try to rollback we can still be stuck with this new version, if this is set explicitly then if we need to rollback it will rollback to this specific version.