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

readXXX functions should fully populate resource objects #7

Closed
7 tasks done
dancrumb opened this issue May 29, 2018 · 7 comments
Closed
7 tasks done

readXXX functions should fully populate resource objects #7

dancrumb opened this issue May 29, 2018 · 7 comments

Comments

@dancrumb
Copy link
Contributor

dancrumb commented May 29, 2018

Right now, implementations of readXXX only partially populate the ResourceData objects.

It's tedious work, to be sure, but I think they should really be fully populating them. See, for example: https://github.com/terraform-providers/terraform-provider-aws/blob/master/aws/resource_aws_api_gateway_integration_response.go#L152

  • Clients (Applications)
  • Client Grants
  • Connections
  • Custom Domains
  • Resource Servers (APIs)
  • Rules
  • Rules Configs
@alexkappa
Copy link
Owner

Yes, absolutely. We should do this to be in line with other providers and be consistent.

@dancrumb
Copy link
Contributor Author

I'm working on the Client resource today

@alexkappa
Copy link
Owner

alexkappa commented May 29, 2018 via email

@dancrumb
Copy link
Contributor Author

First pass at Client resource in #8

@alexkappa alexkappa changed the title readXXX functions should fully populate the ResourceData objects readXXX functions should fully populate resource objects Jun 1, 2018
@dancrumb
Copy link
Contributor Author

At long last, the PR is complete :)

@alexkappa
Copy link
Owner

Thanks for the help on this @dancrumb !

@dancrumb
Copy link
Contributor Author

Thanks for your patience! This is the first time I've really written any Go, so it was a bit of a slog. but I'm excited to have this functionality!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants