Folders that are visible from the SDK don't appear to be visible via the CLI

dsoprea

We have a "Full Dropbox" app installed on a team account. We're setting DROPBOX_MANAGE_APP_KEY and DROPBOX_MANAGE_APP_SECRET. I've also tried with DROPBOX_PERSONAL_APP_KEY and DROPBOX_PERSONAL_APP_SECRET, and DROPBOX_TEAM_APP_KEY and DROPBOX_TEAM_APP_SECRET. For some reason, dbxcli is using my personal home as the root folder, and can't see the team-level folders. It works fine when using the SDK from our webhooks, though, using the exact same credentials. 

 

This is essentially the loop in some webhook code that we have that responds to events in our team account:

 

 

# Get non-team scoped resource
dbx = dropbox.dropbox_client.Dropbox(
        app_key=_DROPBOX_KEY,
        app_secret=_DROPBOX_SECRET,
        oauth2_refresh_token=_DROPBOX_REFRESH_TOKEN)

cursor_id = None
has_more = True
while has_more is True:

    if cursor_id is None:
        # This is either the first time we've ever enumerated the
        # folder, or we've cleared our cursor

        # Enumerate the root of our scoped path. This is a required
        # parameter and the root must be represented as an empty string.
        #
        # This call is nonrecursive by default, which is fine by us
        result = \
            dbx.files_list_folder(
                path='/ManagedIntake',
                recursive=True)

    else:

        #
        # IMPORTANT
        #
        # Multi-file operations will usually induce separate webhook
        # notifications, but the earlier requests will often have
        # already read the full cursor before the later requests.
        # Therefore, some of the requests will show nothing to do.

        result = dbx.files_list_folder_continue(cursor_id)


    # Update cursor
    cursor_id = result.cursor

    for entry in result.entries:
        yield entry, cursor_id


    # Repeat only if there's m ore to do
    has_more = result.has_more

 

 

 

However, when we try to do this from the CLI, it won't let us access that root folder:

 

$ ./dbxcli ls -l
Revision Size Last modified Path
-        -    -             /dustin@<hidden>’s files 
-        -    -             /PRODUCT IMAGES                       

$ ./dbxcli ls -l /ManagedIntake
Error: path/not_found/

 

 

I also tried passing `--as-member <member ID>`, but got the same result.

 

For reference, this is my UI view:

 

I must be missing an obvious and/or fundamental truth. Any thoughts?

 

This seems like a root-path issue. Typically, when using the API, we can go and get whichever root-path is relevant to our context using the API and set it via the `Dropbox-API-Path-Root` header for those calls. It's still not clear why our SDK integration doesn't have the particular issue that we're trying to deal with, but the CLI doesn't even seem to have the ability to expose path-IDs nor to set that header. How are we supposed to manage this via the CLI?

dsoprea

Okay. Yes. That's what I was missing. I saw enough entries that has non-None team-member IDs that I missed that the one I was looking for had a None one.

 

Yes. That's fine. I'm not dealing with pagination given that this is a PoC that didn't require it.

 

Since this is a team-level folder, I've just enumerated the members and grabbed the first one:

# Get team-scoped resource
dbxt = dropbox.dropbox_client.DropboxTeam(
        app_key=_DROPBOX_KEY,
        app_secret=_DROPBOX_SECRET,
        oauth2_refresh_token=_DROPBOX_REFRESH_TOKEN)

# Get members

result = dbxt.team_members_list()

# Grab the first member returned

first_member_id = None
for member in result.members:
    first_member_id = member.profile.team_member_id
    break

assert \
    first_member_id is not None, \
    "No members found."

# Get the namespace whose root we want to use

r = dbxt.team_namespaces_list()
namespace_id = None
for namespace in r.namespaces:
    if namespace.name != 'ManagedIntake':
        continue

    namespace_id = namespace.namespace_id

assert \
    namespace_id is not None, \
    "Could not find images namespace."

# Get object scoped to the member and root-path above

dbxtm = dbxt.as_user(first_member_id)

path = dropbox.common.PathRoot.namespace_id(namespace_id)
dbxtmp = dbxtm.with_path_root(path)

result = dbxtmp.files_list_folder("")
for entry in result.entries:
    print(entry.name)

 

So, that works, and works as desired.

 

How would the account-level access work? Since all of our apps would have to be team-scoped, are you just saying that removing the team-scopes will magically allow the app to have account -specific access? I had originally created a separate app for this and hadn't given it any team-scopes, but I was unable to even see this folder, presumably because it lives in the team space. Is that accurate?