-
Notifications
You must be signed in to change notification settings - Fork 1
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
implements metal connection, info and integration tests #118
Conversation
should be ready for review |
Co-authored-by: Tomáš Karásek <[email protected]>
Co-authored-by: Tomáš Karásek <[email protected]>
@AlexBacho we will need to rework this a bit still. With the API update and with new equinix_metal pip package, you can see that InterconnectionCreateInput class is not genreated anymore. Instead it's defined as oneOf[0], and there is You will need to update equinix_metal to the latest release to see the new input classes. Please also fix equinix_metal to the newest equinix_metal release in requirements.yml. |
@AlexBacho I looked a bit more on the API[0]. It seems that there's a way to create IC in project[1] or in an org[2]. The module should handle both. The API input to project can be any of the three [3], and input to org can be only DedicatedPort. We have 4 combinations here which is not good. We need to think how to handle those in the api_router[4], because in the CREATOR routes, we have a combination of APImethod-Input, I think we'll need 4 entries there metal_connection_project_dedicated .. in form ('`metal_connection_organization_vlanfabric', action.CREATE): spec_types.Specs(
equinix_metal.InterconnectionsApi(mpc).metal_connection_organization_vlanfabric,
{'organization_id': 'organization_id'}, # see the args of the function in [5]
equinix_metal.DedicatedPortCreateInput,
), .. I think you understand what the configuration should be for the other routes. You will need to distinguish those for the create event in the module. I do sth similar but much simpler in the metal_project, line 245 [6]. As for the GETTER and UPDATER, there's only one of each [7,8]. As for listers there will be 2 [9,10] (you will need them in You don't need to implement the fetch by name in I hope this is clear, let's talk tomorrow. [0] https://deploy.equinix.com/developers/api/metal#tag/Interconnections |
…ons, for example the interconnection models
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@AlexBacho Please fix my latests suggestions, regenerate docs and push.
You did improvements to vlan and project_ssh_key, it's a good intiative, but next time they should go to a separate PR.
Co-authored-by: Tomáš Karásek <[email protected]>
Co-authored-by: Tomáš Karásek <[email protected]>
Co-authored-by: Tomáš Karásek <[email protected]>
Co-authored-by: Tomáš Karásek <[email protected]>
work in progress
Fixes #15
Fixes #54