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

chore: support importing resources by fully qualified names #84

Conversation

ethanndickson
Copy link
Member

@ethanndickson ethanndickson commented Sep 3, 2024

Previously, user, group and template resources could only be imported via their UUIDs. The coder/coder frontend doesn't expose these UUIDs to the user, so we should provide an alternative, more user-friendly way to import resources.

User resources: ID or username, since usernames must be unique, even across multiple orgs.
Template resources: ID or <organization-name>/<template-name>
Group resources: ID or <organization-name/<group-name>

Copy link
Member Author

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @ethanndickson and the rest of your teammates on Graphite Graphite

@ethanndickson ethanndickson force-pushed the 09-03-chore_support_importing_resources_by_fully_qualified_names branch from bc0395f to ced04dc Compare September 3, 2024 05:03
@ethanndickson ethanndickson marked this pull request as ready for review September 3, 2024 05:04
@ethanndickson ethanndickson merged commit 7645de8 into main Sep 3, 2024
14 checks passed
@ethanndickson ethanndickson deleted the 09-03-chore_support_importing_resources_by_fully_qualified_names branch September 3, 2024 05:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants