PROJECT_REQUIRES_IMPORT about docgist HOT 4 OPEN

Thanks for shedding light on this issue.

I just heard back from Firebase and they said they are willing to restore access to the database until May 15th. I guess they are changing infrastructure and that's their hard deadline to extend access for non-migrated accounts. But that will at least give people a chance to recover documents (which were hopefully only work in progress). After that date, we will connect the service to a new account and maintain the credentials more responsibly.

I also think this is a good idea to clearly communicate how this storage backend works and what the terms are. This is not meant to be a production or secure instance. We just need to be transparent about that. You can always take docgist and run it on your own infrastructure if you need more security or uptime guarantees.

from docgist.

The service is available again in its former state until May 15th. At that point, we have to either change to a new database instance or decide not to run that part of the service.

from docgist.

I'm aware of this problem and I'm working to resolve it. The challenge is that the maintainer of database instance (and former maintainer of docgist) is no longer with us. While the Asciidoctor project hosts the application, the information about the account never got recorded properly. I'm in contact with Firebase Support to regain control of the instance so it can be migrated.

Here's where we are right now

we can't transfer ownership over the project without first demonstrating that you are the owner of the project or otherwise have root access to it. The means that we have for that are either (a) email verification for the owner account or (b) proof of ownership of one or more of the secrets of the database instance. It sounds like the email verification is no longer possible; let us know if you have admin access to the database via a database secret, and we can discuss how to prove ownership that way.

One last alternative is that we could re-enable the project temporarily, allowing you to access the data in there, however that would be a temporary solution. Unfortunately, it would not change the timeline that the project will be permanently disabled and deleted without proper import and ownership in May.

I'd be fine with the temporary solution as it would at least allow us to have a smooth transition to a new database instance. Then, we will be sure to guard access to the database credentials properly this time.

from docgist.

Aw snap. Thanks for the details. I wanted to bring this issue to the light in case it has been overlooked.

I hope you will be able to recover access to the database 🙌

from docgist.