Use `GenerateResourceConfig` RPC to generate config instead of using the `tfadd` if the server support it
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- go, terraform
- Domain
- cli, devops, infrastructure
Research direction
Start by locating the Terraform mode that currently invokes tfadd and inspect how terraform-client-go exposes provider capabilities. Check the Terraform version before selecting the path, use GenerateResourceConfig when the provider supports it, and retain tfadd as the fallback for older versions or unsupported providers. Done means both paths are covered and the referenced Terraform RPC behavior is respected.
Written by the indexing model from the issue text.
Description
Since terraform v1.14.0, there will be a new RPC protocol GenerateResourceConfig that allows the provider to generate a precise config instead of using tfadd. We shall check whether the target provider supports that, if so, we use this new method, otherwise fallback to using tfadd.
This requires the support of the new interfaces in terraform-client-go.
This also requires to add a check on the terraform version (with tf mode), if less than v1.14.0, still using tfadd. Gradually, we shall deprecate tfadd if all the azure providers have supported the new RPC protocol.
Reference: https://github.com/hashicorp/terraform/pull/37515
- Dominant language
- Go
- Stars
- 1.9k
- Forks
- 220
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 5
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Azure/aztfexport
-
question
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Azure/aztfexport#676 · 1 comment ·
-
question
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Azure/aztfexport#663 · 3 comments ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
Azure/aztfexport#649 · 1 reaction ·
-
upstream-provider
Difficulty 3/5 1-2 days Newbie friendliness 35/100
Azure/aztfexport#637 · 1 comment · 1 reaction ·
-
service
Difficulty 4/5 3-5 days Newbie friendliness 28/100
Azure/aztfexport#624 · 1 comment ·
All issues in Azure/aztfexport
Similar issues
-
darwin zsh
Difficulty 1/5 Under an hour Newbie friendliness 90/100
carapace-sh/carapace-bin#3846 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 70/100
golang-app/ecommerce#179 ·
Maintainers usually reply within 1 day
-
Simulator process crashes (nil pointer panic) when the dataset returns an errorPossibly taken @EugeneVon claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
llm-d/llm-d-inference-sim#772 ·
Maintainers usually reply within 1 day
-
refactor: decode numchildren with a lenient int type instead of a hand-written xProp.UnmarshalXMLOpen
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
crazy-goat/xdbg#125 ·
Maintainers usually reply within 1 day
-
150 points ci complexity:medium drips-wave help wanted medium
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
sorotrail/SoroBeacon#449 ·
Maintainers usually reply within 1 day