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

fix: unexpected new value: .scopes: was cty.SetValEmpty(cty.String), but now null in teammate import method #16

Merged
merged 1 commit into from
Sep 27, 2023

Conversation

kenzo0107
Copy link
Owner

In teammate Import method,

After specifying .scopes = [] and applying, the following error occurs.

unexpected new value: .scopes: was cty.SetEmpty(cty.String), but now null.

This is because scopes is defined as types.Set type, so if it is not specified, it is specified as the default value.

To avoid the above, define .scopes with []types.String type, Specify the default with []types.String{}.

…but now null in teammate import

In teammate Import method,

After specifying .scopes = [] and applying, the following error occurs.

````
unexpected new value: .scopes: was cty.SetEmpty(cty.String), but now null.
````

This is because scopes is defined as `types.Set` type, so if it is not specified, it is specified as the default value.

To avoid the above, define .scopes with `[]types.String` type,
Specify the default with `[]types.String{}`.
@kenzo0107
Copy link
Owner Author

I confirmed that make testacc passes in the development environment.

@kenzo0107 kenzo0107 merged commit 65fd79e into main Sep 27, 2023
3 of 4 checks passed
@kenzo0107 kenzo0107 deleted the fix_teammate_scopes_default_value branch September 27, 2023 16:50
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.

1 participant