Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

chore(docs): update documentation for coder_workspace_tags#15620

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

Merged
johnstcn merged 2 commits intomainfromcj/15087-docs
Nov 25, 2024

Conversation

johnstcn
Copy link
Member

Adds documentation relating to#15087 and#15427

See also:#15578

Copy link
Member

@matifalimatifali left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Left a few commnents but looks good to me.


- You will need to have an [external provisioner](https://coder.com/docs/admin/provisioners#external-provisioners) with the correct tagset running in order to import this template.
- When specifying values for the `coder_workspace_tags` data source, you are restricted to using a subset of Terraform's capabilities.
- You must specify default values for all data sources and variables referenced by the `coder_workspace_tags` data source.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Are we exposing an explicit error if this is not the case to inform the user on what they can do to fix it. Think about it in context of#15447 .

Copy link
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

See below comment, but TL;DR yes.

Comment on lines +98 to 104
You mayonly specify the following as inputs for `coder_workspace_tags`:

| | Example |
| :----------------- | :-------------------------------------------- |
| Static values | `"developers"` |
| Template variables | `var.az` |
| Coder parameters | `data.coder_parameter.runtime_selector.value` |
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

But the value of thecoder_parameter can itself come from any otherlocal,resource, ordata. Right?

Copy link
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

No, the default must be specified in thecoder_parameter data source. I'll make this more explicit.

matifali reacted with thumbs up emoji
Comment on lines +67 to +68
All template variables and `coder_parameter` data sources **must** provide a
default value. Failure to do so will result in an error.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Can we be sure that the error is explicit and inform the user on how to fix it?

Copy link
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

There are some UI improvements to be made, but here are the main messages:

I'd rather not over-index on documenting package-level errors in documentation, but I can document these if you think it's necessary?

matifali reacted with eyes emoji
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Not needed in docs but with UI enhancements but if we can parse them and show to the user that would do the work.
cc:@chrifro consider this in context of#15447.

chrifro reacted with thumbs up emoji
Copy link
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

It should end up in the API response returned by the backend, so all the FE needs to do is display it to the user 👍

matifali reacted with thumbs up emoji
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

I think we should create an issue in coder/internal to track adding terraform errors to API response.

Copy link
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

I agree, but this might already be in the scope of#15447

Your call though!

matifali reacted with thumbs up emoji
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Yes ✅

@johnstcnjohnstcn merged commite550365 intomainNov 25, 2024
29 checks passed
@johnstcnjohnstcn deleted the cj/15087-docs branchNovember 25, 2024 21:01
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@matifalimatifalimatifali approved these changes

@EdwardAngertEdwardAngertAwaiting requested review from EdwardAngert

Assignees

@johnstcnjohnstcn

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

2 participants
@johnstcn@matifali

[8]ページ先頭

©2009-2025 Movatter.jp