Add frigg start command

[seanspeaks]

Update the CLI to include the new frigg start command.
Update tests, basic for now.
Migrate the backend-js and commit-changes helper functions over.

TODO:

• Likely need to make sure we've updated so that we're looking for either index or backend.js
• Likely need to be js or ts agnostic
• Likely need to assert that the output of the backend or index.js files/modules are properly formatted/confirm that they're what we want.
• Not sure how this works with ts.

Remove old CLI files for restructure and some removal

Added helper functions and migrated from prior setup (basically, lots of renaming) for frigg-cli directory structure.

The changes include:

• Adding a new start command to the CLI
• Updating the main index.js file to include the new command
• Creating a new start-command directory with an index.js file for the start command implementation
• Restructuring the existing install command files into an install-command directory
• Updating import paths and file names to reflect the new structure
• Migrating helper functions and renaming them for consistency
• Updating tests to work with the new structure
• Removing the old environmentVariables.test.js file and replacing it with a new one in the install-command directory

[seanspeaks]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• Changes to the UI library #353
• Add the new Frigg Serverless Plugin #352
• Format mock-integration, basically. #351
• Add Programmatic Serverless #350
• Add frigg start command #349 👈 (View in Graphite)
• Add MIT License #348
• Add QueuerUtil with BatchSend capability #347
• Update integration-router to use the new .send method and default lifecycle events. #346
• Update the integration-factory to take advantage of/utilize the new methods for the integration-base. #345
• Update Integration Base class to v2 #344
• Update the exports for Core with new modules #343
• Add core model for Websocket Connections #342
• Add package-lock at the very end #341
• next

This stack of pull requests is managed by Graphite. Learn more about stacking.

[seanspeaks]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• Add the new Frigg Serverless Plugin #352
• Format mock-integration, basically. #351
• Add Programmatic Serverless #350
• Add frigg start command #349 👈
• Add MIT License #348
• Add QueuerUtil with BatchSend capability #347
• Update integration-router to use the new .send method and default lifecycle events. #346
• Update the integration-factory to take advantage of/utilize the new methods for the integration-base. #345
• Update Integration Base class to v2 #344
• Update the exports for Core with new modules #343
• Add core model for Websocket Connections #342
• Add package-lock at the very end #341
• next

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @seanspeaks and the rest of your teammates on Graphite

[seanspeaks]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• Add the new Frigg Serverless Plugin #352
• Format mock-integration, basically. #351
• Add Programmatic Serverless #350
• Add frigg start command #349 👈
• Add MIT License #348
• Add QueuerUtil with BatchSend capability #347
• Update integration-router to use the new .send method and default lifecycle events. #346
• Update the integration-factory to take advantage of/utilize the new methods for the integration-base. #345
• Update Integration Base class to v2 #344
• Update the exports for Core with new modules #343
• Add core model for Websocket Connections #342
• Add package-lock at the very end #341
• next

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @seanspeaks and the rest of your teammates on Graphite

[sonarcloud]

Quality Gate failed

Failed conditions
5 Security Hotspots
C Reliability Rating on New Code (required ≥ A)

See analysis details on SonarCloud

Catch issues before they fail your Quality Gate with our IDE extension SonarLint