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

Replace usage of deprecated fields in schema.Resource #230

Closed
1 task done
bendbennett opened this issue Apr 12, 2022 · 1 comment · Fixed by #231
Closed
1 task done

Replace usage of deprecated fields in schema.Resource #230

bendbennett opened this issue Apr 12, 2022 · 1 comment · Fixed by #231

Comments

@bendbennett
Copy link
Contributor

bendbennett commented Apr 12, 2022

Terraform CLI and Provider Versions

Terraform v1.1.7
random provider v3.1.2

Use Cases or Problem Statement

The random provider is using deprecated fields within schema.Resource.
For example resource_id uses the Create field which has been deprecated in favour of CreateContext or CreateWithoutTimeout.

Proposal

Replace usage of deprecated fields in schema.Resource (e.g., replace Create with CreateContext or CreateWithoutTimeout).

How much impact is this issue causing?

Low

Additional Information

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@bendbennett bendbennett changed the title Usage of deprecated fields in schema.Resource Replace usage of deprecated fields in schema.Resource Apr 12, 2022
bendbennett added a commit that referenced this issue Apr 12, 2022
bendbennett added a commit that referenced this issue Apr 12, 2022
bendbennett added a commit that referenced this issue Apr 12, 2022
bendbennett added a commit that referenced this issue Apr 12, 2022
bendbennett added a commit that referenced this issue Apr 12, 2022
…eadContext and DeleteContext in resource_shuffle (#230)
bendbennett added a commit that referenced this issue Apr 12, 2022
…text, ReadContext, DeleteContext and StateContext in resource_uuid (#230)
bendbennett added a commit that referenced this issue Apr 12, 2022
Copy link

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 24, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant