cosmicjs / cosmic-cli Goto Github PK

need to add option for json inputs to all commands

Thank you for the tool. Although I just tried it easily, I could connect the bucket well and I got the information of the bucket, but when I use getObject, I will report that data that is not my own is acquired . Thank you.

CLI

npm i cosmic-cli -g
cosmic login (save creds)
cosmic create-user
cosmic add-bucket -slug "bucket-slug" -title "New Test Bucket"
cosmic use-bucket -slug bucket-slug -read_key -write_key (connect to bucket, save)
cosmic add-user -first_name -last_name -email
cosmic install-app app-slug
cosmic add-object-type
cosmic get-object-types
cosmic delete-object-type
cosmic add-object
cosmic get-objects
cosmic get-object
cosmic edit-object
cosmic delete-object
cosmic add-media
cosmic get-media
cosmic delete-media

-d as JSON
-file as JSON file path

Example:

npm i cosmic-cli -g
cosmic

Options
create-user
login

Options
Add-bucket
Bucket

Options
Object-type, object, media, extensions, webhooks

Login command works and returns authenticated. But use-bucket returns Not authorized.

Do I have to use the read key or is this a problem with Windows? Token & email is stored in C:\Users\Alexander\.config\configstore\cosmic-cli.json

Is there a way to get a debug print to get more details why it returns 'Not authorized'?

I'm running Windows 10 Pro (64bit).

Here is a screenshot from my console output from cmd.exe with-in VS code:

Tested the cli also in a virtual machine with Ubuntu 16.0.4.3 (64bit) with the same log message - so this is not an issue that's only related to Windows.

was not in original command list, but I figure that was just a mistake. Added the command.

install-app // 1. Are you sure 2. PUT /buckets/:id
start-app // 1. cd in 2. npm start connected to Bucket
// deploy-app

couple subquestions:

• Should we just take the filename that the user has locally
• If we allow them to specify their own, should we attach the extension to the filename if they do not. For png's for example, if they say 'myimage' for the filename, the upload does not recognize it is a png. So we should take the ending from the filename itself probably and convert 'myimage' to 'myimage.png'. make sure to check they did not already include '.png' at end

Example:

  `exec('git clone ' + repo_url + ' ./' + invokedCmd, function(error, stdout, stderr) {`

uses ./ syntax. Might need to bring in path building helper functions, test on a windows.

Just as we discussed, adding a flag like this:

--metafields '[{type:"text", key: "headline", value: "This is AWESOME"}]'

This will need to be on the following commands:

• Add Object
• Edit Object
• Add Object Type
• Edit Object Type