feat(command): add support to delete dependants of command resource (#…

…189)

* feat(command): add support to delete dependents of command resource

This PR does the following changes:
- Add support to delete dependent resources when command resource is
  deleted.
- Add support to launch the jobs periodically when command is configured
  for run always

Signed-off-by: mittachaitu <sai.chaithanya@mayadata.io>

feat(crd): use unstructured type inplace of typed crd instance (#187)

This commit makes exhaustive changes to handle CRD instances.
CRD instances make use of unstructured types instead of typed
instances. Both CRD versions i.e. v1beta1 & v1 are supported.

Unstructured instances have proved to be generic & testable
versus the typed counterparts especially for CRD schemas that
can differ from each other. In other words, CRD schemas have a
majority schemaless section that is well handled via
unstructured type.

This commit also includes a number of integration test cases
to avoid bug injections if any.

This closes #186
partially. A better approach will be to use latest version of
d-operators with clients that make use of unstructured instances
directly instead of yaml strings that get converted to go
structures.

This commit is also a breaking change, since some of the
structures have been modified. Clients that are already making use
of this structure need to be modified accordingly.

Signed-off-by: AmitKumarDas <amit.das@mayadata.io>

feat(discovery): add method to list resources based on kind (#185)

This PR adds the method to discover list of resources based on
provided kind. This functionality will help consumers to get
resource details based on K8s Kind.

Signed-off-by: mittachaitu <sai.chaithanya@mayadata.io>

feat(testing): initial integration test implementation (#184)

This commit uses container image to run integration tests. The
tests are automated and run on a K3s installation. Integration
tests are triggered as a make target.

e.g. make integration-test-suite

This approach provides the code coverage report in suite's run
logs.

This change fixes a labelling bug where resources that are not
supposed to be labelled are labelled.

GitHub actions has been modifed to accommodate integration testing.

Signed-off-by: AmitKumarDas <amit.das@mayadata.io>

fix(recipe): include ignoreDiscovery as a valid Recipe schema (#183)

This fixes the InvalidSchema issue faced while applying Recipe
custom resource in a Kubernetes cluster.

Signed-off-by: AmitKumarDas <amit.das@mayadata.io>

fix(recipe): update labeling operation with fixes (#182)

This handles the case when ApplyLabels field is not set.
Code results in error when ApplyLabels is empty.

All listed resources are included to be labeled if
IncludeByNames field is empty, since this is an optional
field.

Signed-off-by: AmitKumarDas <amit.das@mayadata.io>

feat(recipe): add labeling as an operation (#181)

This commit adds labeling as an operation. In other words, this
lets one to labels against one or more resources. This also
has tunable to unset labels against the resources that was applied
previously.

Signed-off-by: AmitKumarDas <amit.das@mayadata.io>

feat(crd): create & apply CRD can ignore discovery if set (#180)

Recipe based create or apply action introduces IgnoreDiscovery
boolean flag. This is set to false by default. When this is
set to true it avoids discovering CRD if this CRD got created.

This solves the problem of waiting for each CRD to get
discovered when a Recipe consisting of one or more CRDs get
created.

Signed-off-by: AmitKumarDas <amit.das@mayadata.io>

fix(recipe): fix recipe constructor to use config field (#179)

Signed-off-by: AmitKumarDas <amit.das@mayadata.io>

feat(crd): add v1 apis to apply CRDs (#178)

Signed-off-by: AmitKumarDas <amit.das@mayadata.io>