New Deployment generation feature

[thomas-bc]

Originating Project/Creator
Affected Component
Affected Architectures(s)	fprime-util new
Related Issue(s)	nasa/fprime#1926
Has Unit Tests (y/n)
Builds Without Errors (y/n)	y
Unit Tests Pass (y/n)
Documentation Included (y/n)	y

---

Change Description

• Adds in a new deployment cookiecutter template and the associated logic for new --deployment
• Refactoring to enable utilities that are not tied to an build/deployment/project more easily:
  • Moved utility_entry() to cli.py because it was odd in build_helper.py
  • The logic of loading the build etc... from build_helper.py is now its own function, which utility_entry() calls only if it needs to
  • Moved all special command handler functions out of cli.py and into a new commands.py file for better readability
  • The flag controlling which new target to generate is now an argparse mutually_exclusive_group so we can defer that logic to argparse instead of handling it

Rationale

Addresses nasa/fprime#1926. Will be used for short tutorials and workshops. Has been requested for a long time. The created deployment contains the basic CNDH stack so that users can get started easily.

Request for comments

The cookiecutter stuff is in fbuild/interaction.py which is a little odd hierarchy/naming. I was thinking of putting the new_*** functions in a new module under util/ but that would make yet more refactoring. Let me know if you think that's good or if you see issues with that and I'll put it in for the future new --project feature.

Future Work

TODO: loadParameter() has been commented out in the generated configureTopology() because the function is not autocoded yet. A fix will likely be made where the function gets autocoded even if not parameters are used. Should be un-commented then.

We could add the following cookiecutter options:

• use phases or handcoded topology?
• useTlm channelizer vs packtizer?
• which Ground driver? TCP, UART...

[LeStarch]

Some minor change requests, otherwise this refactor looks really nice!

[LeStarch]

Two other comments:

1. Spelling failed, those new templates bring a lot of spelling that we fixed in F´ core
2. Installation, make sure to run pip install without -e to make sure the templates installed correctly.

[thomas-bc]

1. spelling fixed
2. I was able to install locally without -e with no issue

I addressed your comments, ready for re-review

[LeStarch]

This looks good to me. I very much relate to your last 4 commits.