Add New Exports and Imports

[phalestrivir]

This PR contains changes to allow for the addition of new imports and exports in Frodo Lib (see this PR. The changes are all separated in separate commits, and they include:

• The addition of the new role command which allows for listing, exporting, and importing internal roles.
• The addition of the new server command which allows for listing, exporting, and importing servers and their corresponding properties and default properties.
• The addition of export and import sub-commands for the realm command to add export and import functionality for realms.
• The addition of global exports, imports, and describing of authentication settings.
• Support for exporting, importing, listing, and describing new agent types, including global agents.
• Bug fix for sync mapping imports.
• A few other misc. changes
• Updates to mocks and tests as needed in order for them to pass.

[vscheuber]

@phalestrivir can you check if the file starting with capital F is the final one or the one with lower-case f?

Since both files are in git but only one can exist on a filesystem, it creates a weird conflict. I just don't know which one to delete and which one to keep.

[vscheuber]

@phalestrivir can you check if the file starting with capital F is the final one or the one with lower-case f?

Since both files are in git but only one can exist on a filesystem, it creates a weird conflict. I just don't know which one to delete and which one to keep.

[vscheuber]

@phalestrivir since we released v3.0.0 of the lib, you could, if you want, update the package.json to reference v3 and include it in the PR. That way the tests should run and succeed if everything is well and make the merge easier.

Regarding the issue with these two files:

• federation.authenticationModules.json
• Federation.authenticationModules.json

I've had that happen when I renamed files but the only change was the case of a character in the filename and then I just did a git add, it leads to this conflict. There is a git mv command that instructs git to treat it as a rename so you don't end up with both. I wish IDEs would detect this properly but they don't.

[phalestrivir]

@vscheuber I just updated the package.json to the latest lib version 3.0.1-0. I deleted the Federation.authenticationModules.json file. It wasn't a renaming issue, but rather there was an authentication module named Federation in the frodo dev tenant that was being exported in addition to the default federation module, so they were two separate, distinct modules. I went ahead and deleted it from the dev tenant since it doesn't appear to be used anywhere so that way in future exports we don't run into the same problem.

[phalestrivir]

@vscheuber It seems the checks are failing because it can't find the newest changes to the library code. Both package.json and package-lock.json are updated to the latest version of the lib, so I'm not sure what else is causing it to fail.