2.32.2.20241008: Mitigate issues with deployment-process migration in… #862
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.
… 2.32.2.20241003
Issue #, if available:
The 2.32.2.20241003 update involved a switch to a new source repo for Fluent Bit commits, to increase the stability and efficiency of future deployments/feature-releases.
This change should have been paired with tagging of all commits in that new source with the v1.9.10 tag; however, it seems said tagging failed, leading to #861 (a recurrence of #491)
To mitigate the issue, we are switching the relevant command to instead directly pull from the 1.9.10 branch in that repository.
Description of changes:
Switch from pulling tags from the target repo to pulling a target branch.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.