dashboard access to conf files
closed
John Kennedy
closed
John Kennedy
Yisroel Yakovson we are not at this time looking to expose full APOC, and I've discussed that further here : https://neo4j-aura.canny.io/feature-requests/p/need-apoc-full-on-aura
We have however improved the import experience in Aura with the arrival of data-importer.neo4j.io in the console for AuraDB Free and Professional Databases.
I'm going to close this card now as we've specifically answered the question about allowing full access to edit apoc.conf, which we won't do for security reasons.
John
Kurt Freytag
Yisroel Yakovson could you give us some more details about what you'd like to accomplish?
As you can perhaps appreciate, providing Neo4j as a Service with security and resiliency requires a _huge_ amount of automation and uniformity. This means that we have to apply certain policies in our service that you wouldn't be faced with were you running Neo4j yourself.
If you can tell us about you specific needs (source of data, kind / format of data, target of export), we can help determine the best way to address them.
Yisroel Yakovson
Kurt Freytag: Hi! I understand the issue. On the other hand, there are basic capabilities which have been built into neo4j with an expectation that we have access to the conf files.
This was specifically motivated by a desire for programmatic export and import. That seems to me to be a basic expectation for a database. If I understood your documentation, I need to set apoc.conf to enable that. I ended up implementing a node.js routine that takes care of it, but I think that direct exporting and importing would have been simpler, and I think that it would scale better.
If you don't want to give us access to our configuration (via console or api), then I think that you should find an alternative cypher syntax for aura-specific commands that enable missing capabilities such as export.
Oren Goldberg
This is connected/related to