Test coverage for entrypoint variable of mlcube deployment

[sarthakpati]

@hasan7n: is there a way we can check this in the tests? We should perhaps discuss this in a separate issue, since this could perhaps be important.

Originally posted by @sarthakpati in #730 (comment)

[github-actions]

Stale issue message

[sarthakpati]

Hey @hasan7n could you please take a look at this?

[github-actions]

Stale issue message

[sarthakpati]

Hey @hasan7n can you take a crack at this?

[sarthakpati]

@VukW this should be fixed already with the new API branch, right?

[VukW]

@sarthakpati No, this part was never touched in new API branch. To tell truth I don't get quite well even after reading parent PR what exactly is the issue about? What do we need to check?

[sarthakpati]

Ah okay. It is basically that these lines are not getting covered by tests:

And since this is (IMO) an integral part of the deploy mechanism, I would assume a test would need to updated/added to cover it. I was trying to ask clarification from @hasan7n but he hasn't responded this thread, yet.

[VukW]

Are you talking about just a coverage of this line in deploy.py, or also about real check if container built with such an entrypoint would run properly?

[sarthakpati]

The coverage.