FEATURE REQ: Add checks for Oracle SQLDeveloper connections.xml about seatbelt HOT 6 CLOSED

We're definitely open to it if we can confirm the locations they're dropped - is there any documentation online as to the connection.xml locations?

Since I don't have a test environment, if you're able to build a module to test that'd likely be ideal, but I'll leave this issue up until a module is merged.

from seatbelt.

Hey there :)

In Win7 they are definitely in:

C:\Users<username>\AppData\Roaming\SQL Developer\system\o.jdeveloper.db.connection\connections.xml

Seems to vary quite significantly depending on what version of SQLDeveloper that is running / what servers you connect to so hard to pinpoint a path.
So I think some form of 'recursive listing of dirs for connections.xml within C:\Users<username>\AppData\Roaming\SQL Developer*' would pull them out.

Working on finding out where they are on W10 and getting a test install going.

from seatbelt.

@BaffledJimmy were you able to get a test install going by chance?

@leechristensen we could build a simple module to just test for the presence of these files, ya? Something along the lines of the DpapiMasterKeys command.

from seatbelt.

@BaffledJimmy I finally got a module built for this, and just did a PR for it to master (#55) . Once @leechristensen approves it'll land and I'll close this issue.

from seatbelt.

approves it'll land and I'll close this issue.

psst @HarmJ0y :) you can use a keyword such as "closes #<ISSUE_ID>" or "fixes #<ISSUE_ID>" in your PR or commit to automatically close the corresponding issue!
https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword

from seatbelt.

Landed now as the OracleSQLDeveloper command

from seatbelt.