Workaround dist.apache.org download restrictions #752
Merged
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.
After a "passing" RC, the wizard has RMs download the CRDs and helm charts from a 'staging' area on dist.apache.org and then upload them to the final location. We have scripts to do this, but these were broken recently when dist.apache.org changed its robots.txt to disallow unknown "crawlers".
This commit gets our scripting working again by tweaking a
wget
invocation to not strictly obey the robots.txt for dist.apache.org, which likely isn't intended for restricting foundation-internal usecases such as ours.