- Notifications
You must be signed in to change notification settings - Fork22
docs: clarifycoder_metadata
usage#267
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
This stack of pull requests is managed by Graphite.Learn more about stacking. Join@ethanndickson and the rest of your teammates on |
19dd470
to38546ea
Compareff7aabf
to97e4fb5
Compare97e4fb5
toca52f1f
CompareImportant We should backport this to Also, I renamed the |
matifali left a comment• edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
@ethanndickson@stirby can you backport this to release branch too? And then we can push a new tag.
286841d
intomainUh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
The
coder_metadata
resource is only used to apply metadata to specific template resources. To apply metadata at the workspace level, and have it be shown on the main workspace pane, ametadata
block needs to be created on thecoder_agent
resource. Alternatively, anycoder_metadata
attached to the resource containing the agent will be shown on the dashboard by default (see our dogfood template), but this isn't super obvious, so we'll add a comment.It's pretty easy to assume that the
coder_metadata
resource would let you apply workspace metadata, if you associated it with the agent, so we'll also add a comment mentioning this isn't the case.