aiops

For SC Operator it may be a good idea to generate CRD manifests from inside a docker container.
This should provide reproducible generation step and avoid "produces different output on my machine" issues.

Linter should also fail if generation of manifests produce diff with the commited version.

When trying to log a list of dictionaries like this:

to_send =  [
            {
                "residual": None,
                "timestamp": 1553004853455
            },
            {
                "residual": None,
                "timestamp": 1553004853662
            },
            {
                "residual": None,
                "timestamp": 1553004853868
            }

Is your feature request related to a problem? Please describe.
Users may want to get logs from S3 instead of elasticsearch. We should be able to support that.

Describe the solution you'd like
You can use the boto3 library to download files.
This package is already included in dependencies.

Is your feature request related to a problem? Please describe.
When we get predictions

Is your feature request related to a problem? Please describe.
The existing example workflows are all quite simple. They don't well represent a real-world workflow.

Describe the solution you'd like
There should be a new workflow example in the examples/ directory which carries out the following steps:

• create namespace
• create deployment
• delete deployment
• delete namespace

Is your feature request related to a problem? Please describe the problem.
Helm repo updates are currently manual and human-intensive.

Describe the feature/solution you'd like
Whenever code is pushed to Iter8's helm folder (helm), the helm repo update workflow needs to be triggered automatically.

**Will this feature/solution bring new benefits for Iter8 developers? What are