Currently the extra manifests are registered at the end of the agent installer client "register" command after the ClusterDeployment and InfraEnv have been registered. Because the extra manifests and ClusterDeployment manifest may now appear after the InfraEnv is created, the current flow does not work to support this scenario.

To register extra manifests, having the ClusterDeployment exist is the only requirement.  The client should be refactored so that it doesn't register the extra manifests after the InfraEnv is created. A possible implementation would be to run the following in its own thread:

Proposed flow:

• The client polls for extra manifests in the file system
• Once extra manifests are detected, the client queries the assisted-service REST-API to check if a ClusterDeployment has been registered
  • If yes, the extra manifests are registered to the ClusterDeployment. Care must be taken so that no duplicates are added through the REST-API.
  • If no,  the client sleeps and retries above