Extend Thamos with a new flag to get the base image recommended

[pacospace]

Is your feature request related to a problem? Please describe.
See: AICoE/recommend-base-image-tutorial#1

Describe the solution you'd like
Extend Thamos with a new flag to get the base image recommended and provide it to the user.

Describe alternatives you've considered

Additional context

[goern]

/kind feature
/priority backlog

[pacospace]

this is required for AICoE/recommend-base-image-tutorial#1 (comment)

[pacospace]

hey @fridex do we need to add more here? I would like to add this feature to finish the last tutorial, wdyt?

[fridex]

I don't see any blockers to have this implemented.

[pacospace]

I don't see any blockers to have this implemented.

But at the moment the image is only provided in stack_info only from a boot pipeline unit, should we just iterate over stack_info results and look for ps-* URL links? If no images are identified, just warn the user.

[fridex]

It might be good to provide a generic mechanism for this in advised_manifest_changes so we can generalize the feature. Something like (rough design just to show the functionality):

advised_manifest_changes:
 - file: .thoth.yaml  # File that should be patched (can be also a buildconfig or so).
   patch:
     add: ...

[pacospace]

It might be good to provide a generic mechanism for this in advised_manifest_changes so we can generalize the feature. Something like (rough design just to show the functionality):

advised_manifest_changes:
 - file: .thoth.yaml  # File that should be patched (can be also a buildconfig or so).
   patch:
     add: ...

sounds great, this would be part of a wrap for predictable stacks now right?

[fridex]

sounds great, this would be part of a wrap for predictable stacks now right?

Yes, only wrap pipeline units can add advised_manifest_changes as of now.

[sesheta]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[sesheta]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

[sesheta]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

[sesheta]

@sesheta: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[sesheta]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

[sesheta]

@sesheta: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.