ElasticSearch and many other repos are gone
github.com
github.com
It's possible that any delay is them trying to figure out how to get Terraform back to a good state rather than making the repos public being this inherently hard thing.
I don't know if it is Terraform, but if that was the case, it would actually be trivial to rollback the IaC terraform itself, or even from a previous statefile.
All things considered it doesn't seem to be a destructive mistake, and not 18:00 on a Friday :)
But you're quite right that if they're comfortable enough, they should go into S3 and get a statefile they were happy with!
And the details how it happened are a bit different but it was a configuration error (making things too secure )
[I work for Elastic]
+1 here
The pendulum went from "no tools, we manage everything manually" to "even smoke pauses need to be tracked and versioned".
"Some public repositories are temporarily unavailable"
"GitHub will detach public forks of the public repository and put them into a new network."
"Stars and watchers for this repository will be permanently erased"
And GitHub might have implemented something that let's them restore it after it wasn't possible before, as it's been 2 yrs since.
Lots of possibilities that might change the outcome if elastic is lucky
"In our case, however, they refuse to do that, citing undesirable side effects and the cost of resources. We even offered GitHub financial compensation for any resources required. But, sadly, they declined. They have other priorities than resurrecting the community of one of the oldest and most popular community projects on their platform."
Certainly possible they implemented a way to do this over the last 2 years.
> Current forks will remain public and will be detached from this repository.
If I'm not mistaken when they are back public again everyone will need to update their origin ?
This sentence seems to be about GitHub internally treating forked repos as branches of the original repo to save space (as well as displaying "fork of X" in the UI), and there's no way to manually set that relationship other than the fork button. GitHub would have to manually reset that if they wanted to. (This setup is what allows those fake commit URLs where you use the URL of the original repo plus the commit hash of a commit in a fork.)
This is even more painful for small-to-midsize projects whose star counts help distinguish them.
And if you leak credentials, you'd just have to rotate them. Taking the repo offline would probably be too late anyway and causes a major mess, so not something I could recommend for popular repos
[I work for Elastic]
Since we don't maintain private forks for the Elasticsearch repository (maybe for someone's short lived feature development), the problem of private or deleted forks shouldn't be an issue here.
"Stars and watchers for this repository will be permanently erased, which will affect repository rankings."
https://docs.github.com/en/repositories/managing-your-reposi...
[I work for Elastic]
I'm the maintainer of a reasonably popular project (~9K stars) and it's certainly a nightmare scenario given that I consider the stars to give it credibility in a crowded space.
I guess ES has enough brand recognition. But it'd be killer for a lesser known project. While stars don't matter per se, they do give a project some credibility over a project with 0 stars or 50 stars.
If someone looked at both Elasticsearch and Opensearch and was new to the area, they'd think Opensearch was the original and ES the fork.
It also seems to factor into github search, OpenSearch is on the first page and ElasticSearch is nowhere to be found.
https://github.com/search?q=search&type=repositories
When I see that a project as been forked I use these stats to help select which fork to go with.
Cant they just make them public? Am i missing something?
And that is presuming that this is some sort of technical issue.
Watch: 194 Forks: 0 Stars: 183
Someone paranoid might think that the for-profit management at Elastic is trying to pull some of their previously free software behind a paid-for product. Perhaps they accidentally marked all repos private when they only intended to make a few of them private. They have had beef with AWS in the past where they changed their licensing due to things AWS was doing. So I'll fully believe that it was a genuine accident if all the formerly public repos become public again.
[I work for Elastic]
[I work for Elastic]