3 ms·

> Our teams are working on the restoration path for returning our impacted git repositories to a public state. Cant they just make them public? Am i missing s

by mendym 2y ago

> Our teams are working on the restoration path for returning our impacted git repositories to a public state. Cant they just make them public? Am i missing something?

sqeaky 2y ago
If they posted it on an error or outage page then they probably didn't mean to set it that way, and that implies that there was a non-obvious mistake. They might be doing something silly with their permissions. And that is presuming that this is some sort of technical issue.
- JensRantil 2y ago
  ...or they mistakenly droppen them. :)
dadoonet 2y ago
Not that easy as there are some consequences when you move from public repo to private repo.
- martypitt 2y ago
  I seem to remember someone posting about this once -- you lose all your stars / followers when going public -> private, and they're not restored when you go back.
  - horsawlarway 2y ago
    You can see this now on the link in the post. The repo is currently sitting at Watch: 194 Forks: 0 Stars: 183
  - colechristensen 2y ago
    I would bet, as a result of this and other things like fork management, that they'll be working with GitHub support to try to reverse the go-private and all its consequences.
Retr0id 2y ago
It's perhaps an issue on GitHub's end
- dewey 2y ago
  Pretty sure they would call that out in the status update if it was out of their control.
  - Retr0id 2y ago
    Why? The issue affects their users regardless of whose fault it is.
lutoma 2y ago
I'm guessing someone accidentally pushed something they shouldn't have
parsimo2010 2y ago
"As part of an internal change task" is the justification listed. Maybe this is a genuine accident. 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.
- winddude 2y ago
  unlikely, over the summer they announced that they were going to be more opensource, <https://www.elastic.co/blog/elasticsearch-is-open-source-again https://www.elastic.co/blog/elasticsearch-is-open-source-aga...>
  - xeraa 2y ago
    It's a configuration error (sorry!). Also with thousands of forks this would be a pretty pointless operation. Once something is out (and that includes a license), you cannot just take it back — it will be there forever. [I work for Elastic]
debarshri 2y ago
it could be that they might have discovered some credential leak or secrets leakage in the repo and they are fixing it right now.
- vb-8448 2y ago
  I don't think so, if you accidentally leak an api key you invalidate that specific key.
  - xeraa 2y ago
    Yeah. This was a configuration error. Keys you just rotate. Making repos private accidentally creates a whole new mess with forks, stars,... Not recommended [I work for Elastic]
ajb 2y ago
If it's this: https://news.ycombinator.com/item?id=41060102 https://news.ycombinator.com/item?id=41060102 Then they will need to delete(or rename), remake the repos and push again. Any security problem would also require doing some due diligence to make sure you really squashed it.

by mendym 2y ago

> Our teams are working on the restoration path for returning our impacted git repositories to a public state. Cant they just make them public? Am i missing something?

sqeaky 2y ago

If they posted it on an error or outage page then they probably didn't mean to set it that way, and that implies that there was a non-obvious mistake. They might be doing something silly with their permissions. And that is presuming that this is some sort of technical issue.

JensRantil 2y ago
...or they mistakenly droppen them. :)

dadoonet 2y ago

Not that easy as there are some consequences when you move from public repo to private repo.

martypitt 2y ago
I seem to remember someone posting about this once -- you lose all your stars / followers when going public -> private, and they're not restored when you go back.
- horsawlarway 2y ago
  You can see this now on the link in the post. The repo is currently sitting at Watch: 194 Forks: 0 Stars: 183
- colechristensen 2y ago
  I would bet, as a result of this and other things like fork management, that they'll be working with GitHub support to try to reverse the go-private and all its consequences.

Retr0id 2y ago

It's perhaps an issue on GitHub's end

dewey 2y ago
Pretty sure they would call that out in the status update if it was out of their control.
- Retr0id 2y ago
  Why? The issue affects their users regardless of whose fault it is.

lutoma 2y ago

I'm guessing someone accidentally pushed something they shouldn't have

parsimo2010 2y ago

"As part of an internal change task" is the justification listed. Maybe this is a genuine accident. 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.

winddude 2y ago
unlikely, over the summer they announced that they were going to be more opensource, <https://www.elastic.co/blog/elasticsearch-is-open-source-again https://www.elastic.co/blog/elasticsearch-is-open-source-aga...>
- xeraa 2y ago
  It's a configuration error (sorry!). Also with thousands of forks this would be a pretty pointless operation. Once something is out (and that includes a license), you cannot just take it back — it will be there forever. [I work for Elastic]

debarshri 2y ago

it could be that they might have discovered some credential leak or secrets leakage in the repo and they are fixing it right now.

vb-8448 2y ago
I don't think so, if you accidentally leak an api key you invalidate that specific key.
- xeraa 2y ago
  Yeah. This was a configuration error. Keys you just rotate. Making repos private accidentally creates a whole new mess with forks, stars,... Not recommended [I work for Elastic]

ajb 2y ago

If it's this: https://news.ycombinator.com/item?id=41060102 https://news.ycombinator.com/item?id=41060102 Then they will need to delete(or rename), remake the repos and push again. Any security problem would also require doing some due diligence to make sure you really squashed it.