CF CLI binaries unavailable

[catalinmares]

Please fill out the issue checklist below and provide ALL the requested information.

• I reviewed open and closed github issues that may be related to my problem.
• I tried updating to the latest version of the CF CLI to see if it fixed my problem.
• I attempted to run the command with CF_TRACE=1 to help debug the issue.
• I am reporting a bug that others will be able to reproduce.

Describe the bug and the command you saw an issue with
Provide details on what you were trying to do (and why).
It seems that currently the cf-cli binaries cannot be retrieved from the official CloudFoundry repository. Our deployment pipelines are failing because of this.

What happened
curl -sL https://packages.cloudfoundry.org/stable?release=linux64-binary&version=v8&source=github returns a 404

Expected behavior
The command should return an archive containing the cf-cli binaries which I could extract and use.

Exact Steps To Reproduce
Steps to reproduce the behavior; include the exact CLI commands and verbose output:

1. Run curl -sL https://packages.cloudfoundry.org/stable?release=linux64-binary&version=v8&source=github | tar -zx
2. See error

Provide more context

• platform and shell details: running the command in Jenkinsfile
• version of the CLI you are running: cf8-cli

[nhConitas]

Experiencing the same issue.

[MB175]

I'm facing the same issue, the server isn't serving anything but 404.

[CONITAS-WeDo]

Same problems over here. Can't reach any of the resources

[lfdebrux]

Same issue, if I go to https://packages.cloudfoundry.org/debian I get

404 Not Found: Requested route ('packages.cloudfoundry.org') does not exist.

[cbsmerveguel]

Same issue here as well.

[rob-de-jong-alliander]

Same here

[MB175]

Bad news for all the AzureDevops Task Users, it looks like there is no way to exchange the source server with for example GitHub.

See here

[MB175]

Servers are working again, make sure to check the checksums of the binary since there is no official response what the cause of the outage was, servers might have been under attack or something else

[phingage]

still 404

[andreasvoigt]

Same here.

[cbsmerveguel]

Same issue furthers......

[sagentac]

Also getting a 404

[philipphaeusle]

Same here

[florian-becker]

broken again