Comments (5)
Hi @rjhornsby 👋 Thank you for raising this issue as the tutorial content is not open source at this time.
It's a great idea that these tutorials should be more prescriptive about the preference of framework provider development over SDK provider development. We had planned on updating each the SDK tutorials to have a callout pointing to the framework tutorials with similar text to what you found, but I'm personally unsure the status of those tutorial updates. I will followup internally to ensure these updates occur to reduce confusion.
Out of curiosity, I'm wondering if:
I went looking for docs on writing a custom TF provider, and found https://developer.hashicorp.com/terraform/tutorials/provider
Was this through a search engine or similar? We would definitely love to point developers at the framework tutorials where possible and insight into how they might still be pointed at the older tutorials is greatly appreciated.
Thanks again!
from terraform-docs-common.
Ah ha, it turns out those updates did happen to the individual tutorial pages (e.g. the callout box near the top of https://developer.hashicorp.com/terraform/tutorials/providers/provider-use) but not the collection page. I'll see what can happen here -- the collection page content might be a little more limited in what can be put there, so it might wind up being normal text instead of a callout.
from terraform-docs-common.
Was this through a search engine or similar?
IIRC it was a Google search result, but now I can't seem to figure out what terms I used or how I ended up on that specific page. I can see where I was trying to figure out the difference between the framework and the SDK, but not how I landed on the page that led me to trying to sort that out. Sorry that's not helpful.
it might wind up being normal text instead of a callout.
That seems fine. Google is really good about search results for deprecated APIs, SDKs, etc showing up near the top unless you're super specific. I end up hitting this constantly with AWS documentation. So any additional remarks on the page - callout or otherwise - that say "hey, btw, we suggest the Framework" would be helpful.
from terraform-docs-common.
The additional information is very appreciated, thanks so much @rjhornsby 👍
from terraform-docs-common.
All set! https://developer.hashicorp.com/terraform/tutorials/providers
In these tutorials, learn how Terraform interacts with APIs and write a provider based on the prior plugin SDK. To create a new Terraform provider, please follow the Custom Framework Providers tutorials instead.
Thank you again.
from terraform-docs-common.
Related Issues (20)
- update run states for final states comprehensively HOT 1
- Terraform Cloud - Org Settings / Security / Authentication not documented? HOT 1
- Add support for documentation generation in the tutorial HOT 2
- Add support for migration in the code generation documentation HOT 1
- website/docs/cloud-docs/api-docs/team-tokens.mdx does not document GET call
- Update data security categories for Terraform Cloud
- drift detection documentation typo HOT 1
- vault_mount.intermediate.path HOT 1
- mycloud.alternate HOT 1
- aws.west HOT 1
- resource "aws_instance" "foo" { provider = aws.west # ... } HOT 1
- aws_security_group.hashiapp.id HOT 1
- resource "vault_pki_secret_backend_cert" "app" { backend = vault_mount.intermediate.path name = vault_pki_secret_backend_role.test.name common_name = "app.my.domain" } check "certificate_valid" { assert { condition = !vault_pki_secret_backend_cert.app.renew_pending error_message = "Vault cert is ready to renew." } } HOT 1
- aws_security_group.hashiapp.id HOT 1
- data "hcp_packer_image" "hashiapp_image" { bucket_name = "hashiapp" channel = "latest" cloud_provider = "aws" region = "us-west-2" } resource "aws_instance" "hashiapp" { ami = data.hcp_packer_image.hashiapp_image.cloud_image_id instance_type = var.instance_type associate_public_ip_address = true subnet_id = aws_subnet.hashiapp.id vpc_security_group_ids = [aws_security_group.hashiapp.id] key_name = aws_key_pair.generated_key.key_name tags = { Name = "hashiapp" } } check "ami_version_check" { data "aws_instance" "hashiapp_current" { instance_tags = { Name = "hashiapp" } } assert { condition = aws_instance.hashiapp.ami == data.hcp_packer_image.hashiapp_image.cloud_image_id error_message = "Must use the latest available AMI, ${data.hcp_packer_image.hashiapp_image.cloud_image_id}." } } HOT 1
- aws_subnet.hashiapp.id HOT 1
- aws_instance.hashiapp.ami HOT 1
- vault_mount.intermediate.path HOT 1
- vault_pki_secret_backend_role.test.name HOT 1
- Behavior Changes in Filter for Provider Documentation HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from terraform-docs-common.