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

fix: set owner name and email to "default"#209

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
mtojek merged 4 commits intomainfrommatifali/set-default-owner
Apr 23, 2024

Conversation

matifali
Copy link
Member

Closes coder/modules#162

When the terraform plan is run, thedata.coder_workspace.me.owner_email anddata.coder_workspace.me.owner_name fields are blank, which causes the template build to fail.

This should resolve the issue by setting those entries to a non-empty string.

michaelbrewer and TheZoker reacted with heart emoji
Closes coder/modules#162When the terraform plan is run, the `data.coder_workspace.me.owner_email` and `data.coder_workspace.me.owner_name` fields are blank, which causes the template build to fail. This should resolve the issue by setting those entries to a non-empty string.
Copy link
Member

@johnstcnjohnstcn left a comment
edited
Loading

Choose a reason for hiding this comment

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

We should add a unit test to validate this behaviour, and we should probably also validate that this only happens during the plan phase; if these values are unset at the apply stage then this is a pretty big bug somewhere in the coder <-> provider interface.

mtojek and matifali reacted with thumbs up emoji
@matifali
Copy link
MemberAuthor

We should add a unit test to validate this behaviour, and we should probably also validate that this only happens during the plan phase; if these values are unset at the apply stage, then this is a pretty big bug somewhere in the coder <-> provider interface.

I would be happy if someone could take this from here and add the tests. I opened this, considering its a smaller change. I am yet to feel confident about my Go skills.

mtojek reacted with thumbs up emoji

@mtojekmtojek self-assigned thisApr 17, 2024
@mtojekmtojek requested a review fromjohnstcnApril 23, 2024 14:34
@mtojekmtojek merged commit8c5e8ff intomainApr 23, 2024
@mtojekmtojek deleted the matifali/set-default-owner branchApril 23, 2024 14:40
@github-actionsgithub-actionsbot locked and limited conversation to collaboratorsApr 23, 2024
Sign up for freeto subscribe to this conversation on GitHub. Already have an account?Sign in.
Reviewers

@mtojekmtojekmtojek left review comments

@johnstcnjohnstcnjohnstcn approved these changes

Assignees

@matifalimatifali

@mtojekmtojek

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Git config 1.0.3 Call to function "coalesce" failed: no non-null, non-empty-string arguments.
3 participants
@matifali@johnstcn@mtojek

[8]ページ先頭

©2009-2025 Movatter.jp