OBJET | OBJET : A Computer Vision Graphical Sandbox | Machine Learning library

It's an attempt to exploit (an apparently non-existent) code injection vulnerability. The use of eval is a dead giveaway.

You would have to parse the body yourself to cut off anything you don't want.

What you want is not really possible - message body is a free-form text, the user is allowed to type anywhere. I personally do that all the time - I just type "see below" and insert my comments in the original email. There is no way to separate the two.

The dtype is Object

This suggest you have strs representing numbers rather than numbers, try chaning keys in your dict to strs. Consider following example:

My answer from Discourse:

The answer you linked to is the correct way to get this information, from the payment_method on the payment_intent. I'm not sure how/why your payment_intent value would not be populated, as my testing indicates this to be initialized upon creating the session, even if I never redirect to it.

Are you certain you're creating a mode=payment session? I see that in the code you shared, but things will change a bit if you're actually doing setup or subscription mode.

You can try with something similar as

Perhaps you could check whether the input argument is quoted or not and use that information. There might be a ready-made function for that already, but you could also define it yourself, for example doing something like this:

You need to prepare the query and then add the values to it

As you seem to have problems with the acccent, put it in backticks, or remove them completely.

see manual

Just for clarification purposes:

• Helm is a package manager with which you can install an application onto the cluster in a bundled matter: it basically provides you with all the necessary YAMLs, such as ConfigMaps, Services, Deployments, and whatever else is needed to get the desired application up and running in a proper way.

• An Operator is essentially a controller. In Kubernetes, there are lots of different controllers that define the "logic" whenever you do something (e.g. the replication-controller adds more replicates of a Pod if you decide to increment the replicas field). There simply are too many controllers to list them all and have running individually, that's why they are compiled into a single binary known as the kube-controller-manager. Custom-built controllers are called operators for easier distinction. These operators simply watch over the state of certain "things" and are going to perform an action if needed. Most of the time these "things" are going to be CustomResources (CRs) which are essentially new Kubernetes objects that were introduced to the cluster by applying CustomResourceDefinitions (CRDs).

With that being said, it is not uncommon to use helm to deploy operators, however, try to avoid the term "helm operator" as it is actually referring to a very specific operator and may lead to confusion in the future: https://github.com/fluxcd/helm-operator

So my question is, can we somehow use those helm operators inside our operator?

Although you may build your own operator with the operator-sdk which then lets you deploy or trigger certain events from other operators (e.g. by editing their CRDs) there is no reason to do so.

The only method I can think of so far is calling the helm setup console commands from within a deployment app.

Most likely what you are looking for is a proper CI/CD workflow. Simply commit the helm chart and values.yaml files that you are using during helm install inside a Git repository and have a CI/CD tool (such as GitLab) deploy them to your cluster every time you make a new commit.

Update: As the other edited his question and left a comment i decided to update this post:

The main purpose of the operator is to deploy X databases. Along with that we would like to have a single operator/bundle that deploys the whole system right away.

Do you think it makes sense to bundle operators together in another operator, as one would do with Helm?

No it does not make sense at all. That's exactly what helm is there for. With helm you can bundle stuff, you can even bundle multiple helm charts together which may be what you are actually looking for. You can have one helm chart that passes the needed values down to the actual operator helm charts and therefore use something like the service-name in multiple locations.

In the case of operators inside operators, is it still necessary to configure every sub-operator individually when configuring the operator?

As mentioned above, it does not make any sense to do it like that, it is just an over-engineered approach. However, if you truly want to go with the operator approach there are basically two approaches you could take:

• Write an operator that configures the other operators by changing their CRs, ConfigMaps etc. ; with this this approach you will have a somewhat lightweight operator, however you will have to ensure it is compatible at all times with all the different operators you want it to interfere with (when they change to a new apiVersion with breaking changes, introduce new CRs or anything of that kind, you will have to adapt again).
• Extract the entire logic from the existing operators into your operator (i.e. rebuild something that already already exists); with this approach you will have a big monolithic application that will be huge pain to maintain as you will continuously have to update your code whenever there is an update in the upstream operator

Hopefully it is clear by now that building your own operator for "operating" other operators comes with lot of painful dependencies and should not be the way to go.

Is it possible to deploy different configurations of images? Such as databases configured with different ports?

Good operators and helm charts let you do that out of the box, either via a respective CR / ConfigMap or a values.yaml file, however, that now depends on what solutions you are going to use. So in general the answer is: yes, it is possible if supported.