32 results found

1. Add support for AWS SSO when authMechanism is MONGODB-AWS

   Currently MONGODB-AWS authentication mechanism doesn't support AWS SSO. User has to manually run aws sso get-role-credentials to retrieve the temporary credentials first.

   All AWS SDK support SSO out of the box, therefore mongosh should add support for it too.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Commands  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. Change mongosh to process and use arguments only up to a "--" sentinel

   Getting command line arguments into mongosh is virtually impossible.  The --eval option insists on printing the last eval expr evaluated to the console despite the --quiet switch.  Allowing a script to self parse and manage any args following the "–" sentinel using the "process.argv" array would permit the developer a wide array of choices in handling script input from a command line.

   " > mongosh mongo-options script file – arg arg... "

   Component: mongosh

   Versions: 1.4.x and up

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   4 comments  ·  Scripting  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. Support git command

   MongoSh is a developer tool, obviously. So as a developer, git is always a part of it. Supporting git command inside mongosh will help us save a lot of time.

   Here's some of my implementation:
   
const git = (command) => {
try {
return execSync(`git ${command}`).toString();
} catch (e) {};
return null;
};
const listBranches = () => {
const branches = git(`branch -a`).split(/\r\n|\n|\r/).filter(notEmpty);
return branches.map(branchObj);
};
const pull = (remote = 'origin') => {
return git(`pull ${remote} --rebase`);
};
const log = (cnt) => {
const _cnt = Number(cnt) || 32;
return git(`log --graph --all --oneline --decorate=short --max-count=${_cnt}`);
}


   MongoSh is a developer tool, obviously. So as a developer, git is always a part of it. Supporting git command inside mongosh will help us save a lot of time.

   Here's some of my implementation:
   
const git = (command) => {
try {
return execSync(`git ${command}`).toString();
} catch (e) {};
return null;
};
const listBranches = () => {
const branches = git(`branch -a`).split(/\r\n|\n|\r/).filter(notEmpty);
return branches.map(branchObj);
};
const pull = (remote = 'origin') => {
return git(`pull ${remote} --rebase`);
};
const log = (cnt) => {
const _cnt = Number(cnt) || 32;
return git(`log --graph --all --oneline --decorate=short --max-count=${_cnt}`);
}… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Commands  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. Suggest new feature for loading scripts: loadScript and loadFolder

   For loading external script into MongoSh current session, currently we have the load() function, which is enough for the task. But I found myself using my own functions instead. So I would like to describe those as suggestion to improve MongoSh:

   loadScript()

   This function is basically has the same function with load(). But has 1 major difference: all relative paths in the script has the same base directory with the script itself, not the current MongoSh working directory.
   For example:
   - Script "D:\MyProject\src\script.js" have these references: "test.js", "../test2.js"
   - Current working dir process.cwd(): "C:\MongoSh"
   - Path resolved using load("D:\MyProject\src\script.js"): "C:\MongoSh\test.js", "C:\test2.js"
   - Path resolved using loadScript("D:\MyProject\src\script.js"): "D:\MyProject\src\test.js", "D:\MyProject\test2.js"

   My implementation:

   const loadScript = function (name) {
     const currentDir = path.resolve();
     const absPath = path.resolve(name);
     try {
       process.chdir(path.dirname(absPath));
       load(path.basename(absPath));
     } catch (e) {
       print(e);
     }
     process.chdir(currentDir);
   }
   

   loadFolder()

   This function load all scripts in folder and its nested folders (including symbolic links) using loadScript() behavior.

   Why I use this in the first place? Because of .mongoshrc.js. I have a lot of self implement functions, so I put them all in mongoshrc folder in the same location with .mongoshrc.js. And then load them all inside .mongoshrc.js. But since load() function do not interpreted relative path based on script location, so I have to change my working directory like this:

   {
     const currentDir = path.resolve();
     process.chdir(`${process.env.HOME ?? process.env.USERPROFILE}/mongoshrc`);
     load(`myScripts.js`);
     process.chdir(currentDir);
   }
   

   It is better if .mongosh.js loaded with loadScript(), then the script is just:

   loadScript(`mongoshrc/myScripts.js`);
   

   or

   loadFolder(`mongoshrc`);
   

   Hope I make myself clear. Thanks for reading.

   For loading external script into MongoSh current session, currently we have the load() function, which is enough for the task. But I found myself using my own functions instead. So I would like to describe those as suggestion to improve MongoSh:

   loadScript()

   This function is basically has the same function with load(). But has 1 major difference: all relative paths in the script has the same base directory with the script itself, not the current MongoSh working directory.
   For example:
   - Script "D:\MyProject\src\script.js" have these references: "test.js", "../test2.js"
   - Current working dir process.cwd(): "C:\MongoSh"
   - Path resolved… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Scripting  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. Extended JSON v2

   Allow the use of Extended JSON v2 for e.g. inserting or finding documents.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Commands  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. Retain multi-line input in history.

   Ideally, when using an inline text editor, the inline text editor would show the history command with its multi-lines retained.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Usability  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. Ability to control OCSP TLS certificate verification on mongo shell

   Please allow to control OCSP TLS certificate verification on mongosh shell like it was possible on the legacy shell using "./mongo ... --setShellParameter ocspEnabled=false ..."

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Security  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. auto pair right parentheses when input left
   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Usability  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

9. Add a command to change date format when logrotate is used

   After testing db.adminCommand( { logRotate : 1 } ), the following file was generated:
   /var/log/mongodb/mongod.log.2021-07-05T15-09-17. It would be good to add command to change date format. E.g. yyyymmdd-hhmmss and also it could be specified as variable in mongod.conf

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Commands  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

10. Change naming conventions to more inclusive terms. For example "slaveDelay" to "workerDelay" or "rs.isMaster" to "rs.isMain"

    There is an initiative in the tech community to replace non-inclusive terms with more inclusive ones and I'd like to get the community's take on it. I think the biggest offenders are terminology referring to "slaves" and "masters", but I'm sure there are others that might fall into that category. Although I'm sure nobody meant any harm by using these terms, I think we can and should do better.

    I'm currently working my way through the m103 replication course and I see in replication configuring there's a term "slaveDelay". Also a "rs.isMaster()" method. I'm suggesting replacing "slave" with "worker" and "master" with "main". I know these changes have a gigantic impact logistically speaking, but I think it's time to prioritize the human impact.

    An initiative like this ties into a larger movement across the tech industry to create a better, more professional workplace for everyone. See this article for a similar initiative taken on by GitHub: https://www.zdnet.com/article/github-to-replace-master-with-main-starting-next-month/#:~:text=By%20default%2C%20GitHub%20uses%20the,of%20a%20source%20code%20repository.&text=1%2C%202020%2C%20any%20new%20repositories,will%20be%20left%20as%20is.

    There is an initiative in the tech community to replace non-inclusive terms with more inclusive ones and I'd like to get the community's take on it. I think the biggest offenders are terminology referring to "slaves" and "masters", but I'm sure there are others that might fall into that category. Although I'm sure nobody meant any harm by using these terms, I think we can and should do better.

    I'm currently working my way through the m103 replication course and I see in replication configuring there's a term "slaveDelay". Also a "rs.isMaster()" method. I'm suggesting replacing "slave" with "worker" and… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    started  ·  2 comments  ·  Commands  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

11. Paginate shell output

    When running a query or a command that returns a long output, the content scrolls off the screen and cannot be seen without using the terminal scrollbar.

    It would be nice if the content would only scroll to screen boundaries and pause like more or less.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Usability  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

12. create custom role with list of collection

    currently, when creating a role, we need to list one collection per db for custom role

    db.getSisterDB('admin').createRole({role : 'readWriteCollectionXY',
    privileges : [ {resource : {db : "databaseA", collection : "***"}, actions : ["find", "insert", "update"]},
    {resource : {db : "databaseA", collection : "yyy"}, actions : ["find", "insert", "update"]} ],
    roles : []
    })

    having an option to list all the collections in one db with the same permission would be a nice thing to have.

    db.getSisterDB('admin').createRole({role : 'readWriteCollectionXY',
    privileges : [ {resource : {db : "database_A", collections : ["***", "yyy"] }, actions : ["find", "insert", "update"]} ],
    roles : []
    })

    currently, when creating a role, we need to list one collection per db for custom role

    db.getSisterDB('admin').createRole({role : 'readWriteCollectionXY',
    privileges : [ {resource : {db : "databaseA", collection : "***"}, actions : ["find", "insert", "update"]},
    {resource : {db : "databaseA", collection : "yyy"}, actions : ["find", "insert", "update"]} ],
    roles : []
    })

    having an option to list all the collections in one db with the same permission would be a nice thing to have.

    db.getSisterDB('admin').createRole({role : 'readWriteCollectionXY',
    privileges : [ {resource : {db : "database_A", collections : ["***", "yyy"] }, actions : ["find", "insert", "update"]} ],
    roles… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Commands  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close