FR doesn't start when cloud_provider is specified but generic invocation exists #231
Description
Expected Result
When specifying a cloud_provider in your stackl instance, it was expected that functional requirements that only had a 'generic' invocation would still get triggered.
Actual Result
Functional Requirements don't start at all if they don't have the cloud_provider tag specified, even though a 'generic' invocation is configured.
Steps To Reproduce
create stackl instance with 'cloud_provider=azure'
Create FR with only a 'generic' invocation
The instance will not start up at all.