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

Add router resource #325

Merged
merged 3 commits into from
Jul 12, 2018
Merged

Add router resource #325

merged 3 commits into from
Jul 12, 2018

Conversation

danawillow
Copy link
Contributor

@danawillow danawillow commented Jul 3, 2018

Fixes #319

I wouldn't mind some feedback on the TODO I have in api.yaml about peer and interface.


[all]

Add router resource

[terraform]

Autogenerate router resource. Also adds update support and a few new fields.

[puppet]

[puppet-compute]

[puppet-sql]

[puppet-storage]

[chef]

[chef-compute]

[chef-sql]

[chef-storage]

[ansible]

@modular-magician
Copy link
Collaborator

modular-magician commented Jul 3, 2018

I am a robot that works on MagicModules PRs!

I built this PR into one or more PRs on other repositories, and when those are closed, this PR will also be merged and closed.
depends: hashicorp/terraform-provider-google#1723
depends: modular-magician/ansible#54
depends: GoogleCloudPlatform/puppet-google-compute#64
depends: GoogleCloudPlatform/chef-google-compute#27

@modular-magician
Copy link
Collaborator

I am (still) a robot that works on MagicModules PRs!

I just wanted to let you know that your changes (as of commit 89be6c2) have been included in your existing downstream PRs.

@@ -0,0 +1,216 @@
package google
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In Puppet/Chef/Ansible, we have the products/compute/files folder to hold files exclusive to compute.

I feel like Terraform should move towards that model as well for consistency, unless this test template will be used for other things too.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, we've talked a little bit about this- on one hand, yes. On the other hand, all the other go code that we have for terraform is inside the templates folder (a lot of it, though not actually a template, is shared), and it feels weird to stick this somewhere totally far away in the code base just because of that. This will be a good thing to revisit when we go through and scrutinize the names of things and stuff.

A reference to the network to which this router belongs.
required: true
input: true
# TODO(danawillow): Figure out the story for interfaces/bgpPeers. Right
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's a great model and I'd love to have it in these other providers. Another of the places that MagicModules can be a better cleaner declarative version of the GCP APIs.

@modular-magician
Copy link
Collaborator

I am (still) a robot that works on MagicModules PRs!

I just wanted to let you know that your changes (as of commit 802b0aa) have been included in your existing downstream PRs.

danawillow and others added 2 commits July 12, 2018 20:12
Tracked submodules are build/puppet/compute build/puppet/sql build/puppet/storage build/puppet/container build/puppet/dns build/puppet/pubsub build/puppet/resourcemanager build/chef/compute build/chef/sql build/chef/storage build/chef/container build/chef/dns build/terraform build/ansible.
@modular-magician modular-magician merged commit 0b3b91a into master Jul 12, 2018
@danawillow danawillow deleted the router branch December 7, 2018 17:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants