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.

Sign up for GitHub

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

Jump to bottom

soopervisor --skip-docker should use the configured repository when running with AWS Batch #130

Open
DennisJLi opened this issue Dec 5, 2024 · 3 comments · May be fixed by #131
Open

soopervisor --skip-docker should use the configured repository when running with AWS Batch #130

DennisJLi opened this issue Dec 5, 2024 · 3 comments · May be fixed by #131

Comments

@DennisJLi
Copy link

Right now, when using --skip-docker, the Batch exporter tries to determine the name of the container for the Job definition based on the package the soopervisor.yml file is in, but ideally it'd reuse the configured repository within that file in the Job definition if it's already provided.
@DennisJLi
Copy link
Author

Hey curious if this is something you guys think would be able to be done and released quickly or if it takes a while between releases?

@edublancas
Copy link
Contributor

Hi,

the team is pretty constrained right now, but feel free to open a PR and we can review it.

@DennisJLi
Copy link
Author

Ok I'll try to throw something together.

@DennisJLi DennisJLi linked a pull request Dec 6, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
2 participants
@edublancas @DennisJLi