feat: [TKC-2966] Store TestWorkflowExecutionRequest config in TestWorkflowExecution

[povilasv]

Pull request description

Store request config inside TestWorkflowExecution

Checklist (choose whats happened)

• breaking change! (describe)
• tested locally
• tested on cluster
• added new dependencies
• updated the docs
• added a test

Breaking changes

Changes

Fixes

[rangoo94]

I'm not 100% sure, but could be that iterating over workflow.Spec.Config could be more correct - as a sensitive property set to default value may also be kind of sensitive (similar to uncertainty when working with PII rules - single information may not be sensitive, but in conjunction with others - it can become sensitive)

But, I guess, we can ignore that for now 👍

[povilasv]

Regarding given users can mark their properties as sensitive, I think we can keep it as is?

I.e. if it's kind of sensitive in relation to others, you can still set it to sensitive, right? 🤔

[rangoo94]

I.e. if it's kind of sensitive in relation to others, you can still set it to sensitive, right?

Yes, but I'm more saying about the default value - i.e. if you specify:

spec:
  config:
    apiUrl: { type: string, default: "my-value", sensitve: true }

And you request execution with config:

{}

The code above will save the configuration properly, despite it actually is using sensitive my-value value.

As mentioned though, I think that we can ignore it for now :)

[rangoo94]

I.e. if it's kind of sensitive in relation to others, you can still set it to sensitive, right?

Yes, but I'm more saying about the default value - i.e. if you specify:

spec:
  config:
    apiUrl: { type: string, default: "my-value", sensitve: true }

And you request execution with config:

{}

The code above will save the configuration properly, despite it actually is using sensitive my-value value.

As mentioned though, I think that we can ignore it for now :)