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

deeplink / open from url workspace parameter is not being set #1489

Open
vrabbi opened this issue Dec 18, 2024 · 4 comments
Open

deeplink / open from url workspace parameter is not being set #1489

vrabbi opened this issue Dec 18, 2024 · 4 comments
Labels

Comments

@vrabbi
Copy link

vrabbi commented Dec 18, 2024

What happened?
the workspace parameter is not filling in the workspace name.
also additional parameters are not available like prebuild repo or devcontainer path.

What did you expect to happen instead?
to have the workspace parameter work and the other options all to be supported as well.

How can we reproduce the bug? (as minimally and precisely as possible)

My devcontainer.json:

{
    "name": "...",
    ...
}

Local Environment:

  • DevPod Version: [use devpod version] 0.6.5
  • Operating System: windows
  • ARCH of the OS: AMD64

DevPod Provider:

  • Cloud Provider: kubernetes
  • Kubernetes Provider: [use kubectl version]
  • Local/remote provider: docker | ssh
  • Custom provider: provide imported provider.yaml config file

Anything else we need to know?

@bkneis
Copy link
Contributor

bkneis commented Dec 19, 2024

Thanks for reporting your issue @vrabbi! Can you give me a bit more context, what is not working? Can you give me your .devcontainer.json and the logs of the failing command? I have working devcontainers with both prebuild repo and paths so it may be a misconfiguration of the .devcontainer.json

@vrabbi
Copy link
Author

vrabbi commented Dec 19, 2024

Sorry if there is a misunderstanding.
The issue is about those parameters not being available when using deeplinks/open from url for creating a devpod workspace. It has nothing to do with the devcontainer itself.

@bkneis
Copy link
Contributor

bkneis commented Dec 19, 2024

Oh I see now thanks. This is related to #1474. I am unsure if we can support all the devcontainer parameters in a link (like prebuild repo) but I agree the workspace path would be great

@vrabbi
Copy link
Author

vrabbi commented Dec 19, 2024

The current docs show that the parameter workspace should work for the name of the workspace but it doesnt

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

No branches or pull requests

2 participants