Skip to content
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.

Consider generation terraform.SetupFn based on Terraform Provider Configuration #171

Open
turkenh opened this issue Dec 6, 2021 · 3 comments
Labels
enhancement New feature or request wontfix This will not be worked on

Comments

@turkenh
Copy link
Member

turkenh commented Dec 6, 2021

What problem are you facing?

Today, we leave implementing provider-specific SetupFn to the developer. This requires manually adding all configuration parameters which is usually postponed to later steps.

How could Terrajet help solve your problem?

We should consider generating terraform.SetupFn based on Terraform Provider Configuration if possible.

@turkenh turkenh added the enhancement New feature or request label Dec 6, 2021
@muvaf
Copy link
Member

muvaf commented Dec 7, 2021

What would be the source information to that could help us know what goes to SetupFn?

@turkenh
Copy link
Member Author

turkenh commented Dec 7, 2021

What would be the source information to that could help us know what goes to SetupFn?

I believe we could get most of this information (maybe not all) from the provider schema: https://github.com/integrations/terraform-provider-github/blob/3444b63ec2a8ed2b7665fe48f8747b88e6d5dcd8/github/provider.go#L15

AFAIR, similar information available in terraform providers schema -json output.

@stale
Copy link

stale bot commented Aug 13, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix This will not be worked on label Aug 13, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants