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

Feature request: allow default-repo to be set in skaffold.yaml #5856

Closed
ekuefler opened this issue May 17, 2021 · 6 comments
Closed

Feature request: allow default-repo to be set in skaffold.yaml #5856

ekuefler opened this issue May 17, 2021 · 6 comments

Comments

@ekuefler
Copy link

Expected behavior

I should be able to ask developers to check out my repository and then start working using skaffold dev with no further configuration.

Actual behavior

I have to tell each developer to set default-repo according to the instrucitons at https://skaffold.dev/docs/environment/image-registries/. We set default-repo the same for each developer, so there's no advantage to making everyone do this.

Information

  • Skaffold version: v1.23.0
  • Operating system: Linux
  • Installed via: skaffold.dev
@tejal29
Copy link
Member

tejal29 commented May 17, 2021

@ekuefler
you could define the repository as part of your image name in skaffold.yaml. It will solve half of your problems but not all.
It won't solve the issue for when you want to apply a new default repo per profile i.e. prod, staging,
We have another issues related to specifying default repo per profile basis. #2317

Adding this for our planned work in H2. #5857

@tejal29 tejal29 added the planning/Q4-21 Q4 2021 planning label May 17, 2021
@ekuefler
Copy link
Author

Thanks - I think #2317 probably covers what I want. Our manifests and skaffold.yaml currently specify the repository as it appears in production. Developers don't have write access to that repo, so we want to use a separate dev repo for local development.

@tejal29 tejal29 added the area/V2 label Oct 4, 2021
@tejal29 tejal29 added the kind/todo implementation task/epic for the skaffold team label Oct 13, 2021
@tejal29 tejal29 modified the milestones: unplanned, v1.38.0 Oct 13, 2021
@irvifa
Copy link

irvifa commented Nov 8, 2021

Is this still blocked?

@nkubala nkubala removed the area/V2 label Nov 15, 2021
@nkubala nkubala modified the milestones: v1.38.0, 2.0.0-alpha Nov 15, 2021
@nkubala nkubala removed the kind/todo implementation task/epic for the skaffold team label Nov 15, 2021
@gsquared94 gsquared94 added the triage/discuss Items for discussion label Nov 19, 2021
@gsquared94
Copy link
Collaborator

I added this to our triage discussion list

@tejal29 tejal29 removed the triage/discuss Items for discussion label Jan 10, 2022
@tejal29
Copy link
Member

tejal29 commented Jan 10, 2022

removing the triage/discuss. As part of v2 config re-design, an engineer will look into it

@tejal29 tejal29 removed this from the 2.0.0-alpha-rc1 milestone Mar 2, 2022
@damlys damlys mentioned this issue Aug 31, 2022
3 tasks
@aaron-prindle
Copy link
Contributor

Marking as dupe of #2317, we'll use that issue to track the discussion/progress on this item. Closing (dupe)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants