Bulk update/create Resources from Excel

[gbern-tg]

Bulk update/create Resources from Excel

Functionality: a means to allow admins to bulk update/create resources from excel.

Example:

1. ./tg export - by default, exports the admin's tenant into an xlsx file
2. The admin can go in and adjust most (see limitations below) cells for bulk configuration changes, and save the file.
3. ./tg import -f <xlsx-file> - will import the saved configuration changes and attempt to either (a) update the existing resource or (b) create a new resource

Explanation of changes:

TwingateApiClient.mjs:

• Expanded resource fields - although groups and serviceAccounts is now deprecated for the access connection, there doesn't seem to be consistency across the API so I left as is (FRs that need to be requested below).
• Updated createResource() for expanded functionality with the mutation
• Created updateResource() to allow bulk update functionality with the mutation

smallUtilFuncs.mjs:

• readerFromStreamReader seems to be deprecated, temporarily updated module to the last working version (not familiar enough with a path forward - @chenbishop?)
• updated genFileNameFromNetworkName() to accommodate new output folder so import/export files aren't dropped in main directory

importCmd.mjs:

• expanded functionality to support new updateResource()
• expanded functionality to support updated createResource()
• Added an outputDir so import files aren't dropped in main directory

exportCmd.mjs:

• Added an outputDir so export files aren't dropped in main directory

Instructions/Limitations & FRs needed:

Instructions/Limitations:

• Creating a resource:
  • A resource will be created if an existing Id is not found AND must have (a) name, (b) remoteNetworkLabel, and (c) addressValue specified. - serviceAccounts will not get updated as there is currently no argument available for resourceCreate mutation. - isActive will not get updated as there is currently no argument available for resourceCreate.
• Updating a resource:
  • A resource will instead be updated if an existing Id is found AND (a) name, (b) remoteNetworkLabel, and (c) addressValue are specified. - serviceAccounts will not get updated as there is currently no argument available for resourceUpdate.

FRs needed:

• resourceUpdate Mutation
  • needs serviceAccounts ([]) - or the new access{serviceAccounts, groupIds}
• resourceCreate Mutation
  • needs isActive (boolean)
  • needs serviceAccounts ([]) - or goes off the new access{serviceAccounts, groupIds}

[chenbishop]

@gbern-tg

Hi Grady, I made a commit to fix an issue where the createResource call in different places was not working because the order of the function argument was changed. Please let me know if you are happy with the changes?

I also tried to add the functionality of importing (creating and updating) security policy directly but this is require quite a bit of effort (though we can still change security policy by editing resource during the import), is this needed for your use-case ?

I ran the following tests:

1. tg resource create, this is working now after the new commit
2. tg export seems to be working ok
3. tg import seems to be working ok a. tested resource update and create b. tested resource with updated security policy column change
4. tg import on security policy does not work at the moment as mentioned previously
   1. we cannot use import to create or update the security policy directly
   2. can change policy of a resource through changing resource

Are there anything else you believe I should be testing in particular and could you let me know what have you tested already please?