Validate the incoming NFFG request with the NFFG schema.
In addition, since we may need some optional tags in the request (e.g., domain ID), add the proper code that raises an error when the orchestrator is connected to multiple domains, and the NFFG does not specify which domain refers to.
However, do not raise this exception if the orchestrator is connected to a single domain, which will be useful to allow an initial deployment (e.g., for testing), which typically happens with a single domain and we don't want to bother the tester with useless errors.
Validate the incoming NFFG request with the NFFG schema. In addition, since we may need some optional tags in the request (e.g., domain ID), add the proper code that raises an error when the orchestrator is connected to multiple domains, and the NFFG does not specify which domain refers to. However, do not raise this exception if the orchestrator is connected to a single domain, which will be useful to allow an initial deployment (e.g., for testing), which typically happens with a single domain and we don't want to bother the tester with useless errors.