Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update thoth config with base image recommended by thoth #345

Open
pacospace opened this issue Jul 16, 2021 · 10 comments
Open

Update thoth config with base image recommended by thoth #345

pacospace opened this issue Jul 16, 2021 · 10 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/stack-guidance Categorizes an issue or PR as relevant to SIG Stack Guidance.

Comments

@pacospace
Copy link
Contributor

pacospace commented Jul 16, 2021

Is your feature request related to a problem? Please describe.
As DS,
I want to know which is the base image I should use for my steps in my AI Pipeline. I would like the extension to automatically update thoth config in my repo with base image recommended by Thoth.

Describe the solution you'd like
use new feature of Thoth and update thoth config from advise results automatically once no runtime environment is requested in adviser inputs.

Describe alternatives you've considered

Additional context

@pacospace
Copy link
Contributor Author

Related-To: #229

@goern
Copy link
Member

goern commented Jul 22, 2021

/priority important-soon

@sesheta sesheta added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Jul 22, 2021
@sesheta
Copy link
Member

sesheta commented Aug 25, 2021

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

/close

@sesheta
Copy link
Member

sesheta commented Aug 25, 2021

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 sesheta added the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Aug 25, 2021
@sesheta sesheta closed this as completed Aug 25, 2021
@sesheta
Copy link
Member

sesheta commented Aug 25, 2021

@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.

@pacospace pacospace reopened this Aug 25, 2021
@pacospace pacospace added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels Aug 25, 2021
@pacospace
Copy link
Contributor Author

Depends-On: thoth-station/adviser#1533

@sesheta
Copy link
Member

sesheta commented Oct 1, 2021

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

/close

@sesheta sesheta closed this as completed Oct 1, 2021
@sesheta
Copy link
Member

sesheta commented Oct 1, 2021

@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.

@pacospace pacospace moved this from New to To Do in jupyterlab-requirements Nov 24, 2021
@goern
Copy link
Member

goern commented Jan 14, 2022

/priority important-longterm

@sesheta sesheta added the priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. label Jan 14, 2022
@goern
Copy link
Member

goern commented Apr 26, 2022

/sig stack-guidance

@sesheta sesheta added the sig/stack-guidance Categorizes an issue or PR as relevant to SIG Stack Guidance. label Apr 26, 2022
@goern goern removed the priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. label Jul 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/stack-guidance Categorizes an issue or PR as relevant to SIG Stack Guidance.
Projects
No open projects
Status: To Do
Development

No branches or pull requests

3 participants