Deployment Controller - Ensure all IOC deployment use cases are properly covered

[pnispero]

Deployment Controller - Ensure all IOC deployment use cases are properly covered

Deployment works as is for IOCs, but isn't robust, seem to be running into bugs when testing out deployment.

• Update deployment so it covers all use cases:

1. Deploy tag to select existing IOCs
   (IOCs specified, facility not required)
2. Deploy tag to all existing IOCs
   (IOCs specified, facility not required)
   2.1. Deploy tag to all existing IOCs but user specified which facilities they want to update.
   This would end up being case 2, but the cli would need logic
   to figure out which IOCs in the facilities to deploy
3. Deploy tag to new IOCs
   (IOCs specified, facility required)
4. Deploy tag to component
   (no IOCs, facility required) - works for both new and existing components
5. Deploy tag to new component AND new IOCs
   (IOCs specified, facility required)

Note - that if new component or new IOCs is being deployed, we can trust the user, and deploy them. No need to confirm with user.

• Although we can confirm with source tree they are sitting in, if the IOCs they want to deploy actually exist in their source tree before allowing them to deploy those.

• Also another error check. When deploying existing iocs, have the cli check first if those iocs exist in db, if any don't then confirm with user if they want to proceed, and give them command for new iocs with facility.

• Update the deploy cli to get rid of the --new

• Then update the pytest file to cover those use cases

• Also update onboarding confluence page to include those 5 use cases as examples on how to use the deployment command line.

• Also make another issue for this, but for pydm get rid of the --new as well in the cli and in the deployment controller