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

CXF-83184: Adding NIMF Metal-2-AWS Example #34

Closed
wants to merge 29 commits into from
Closed

Conversation

srushti-patl
Copy link
Collaborator

Includes:
Metal-2-AWS Example

Copy link

@iawells iawells left a comment

Choose a reason for hiding this comment

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

varaibles.tf -> variables.tf

purchase_order_number = "1-323292"
project_id = "<Project_ID>"
aside_ap_authentication_key = "<Metal_Auth_Token>"
aside_ap_type = "METAL_NETWORK"
Copy link

Choose a reason for hiding this comment

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

If this is a metal network example, why is this an input that can be modified?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

We have added this example based on the Fabric Connection contract. We've included it as an input variable for testing purposes. Once the feature is ready for production(supported from Metal side as well), we will update it accordingly

Copy link
Collaborator

Choose a reason for hiding this comment

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

We should update this. The module has the variable as well but it will always be the same Access Point type for Metal Connection module, right?

srushti-patl and others added 15 commits February 22, 2024 16:25
…rtual interface connections (#39)

* fix:Replacing aws_vpn_gateway with aws_dx_gateway resource

* chore: Removing extra space

* chore: fixing indentation

* chore: Adding trailing line
* feat: Integrating GCP Provider with Fabric examples

* chore:Adding variable type and fixing indentation

* fix: Changing variables name from gcp to google

* misc:removing files for old GCP example
* feat: Adding z_side block for virtual device & FCR 2 VD example

* feat: Adding FCR 2 VD redundant example

* nit: Adding indentation space and changing variables names

* misc: Updating variables for FCR 2 NE Redundant connection & adding content readme.md file

* nit: Removing extra line from REDME.md file.

* misc: Adding output id for secondary connection and changing variable name for DOT1Q vlan_tag

* chore: Fixing format

* chore: Updating README.md file

* fix: Adding secondary VD variables in modules main.tf file
Signed-off-by: GitHub <[email protected]>
Co-authored-by: srushti-patl <[email protected]>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
* fix: Updating aws_dx_gateway resource & changing ibm2 example variable name for additional_info

* fix: Updating aws_dx_gateway resource & changing ibm2 example variable name for additional_info
* Update docs for v0.4.0 release

* Include bug fix doc updates
Signed-off-by: GitHub <[email protected]>
Co-authored-by: srushti-patl <[email protected]>
* feat: Adding GHA workflow for Terra tests

* feat: Adding new terratests for port-2port connection and updating variables

* misc: removing cloud router changes from the PR

* misc: fixing UAT terra-tests workflow

* misc: Adding versions file to uat/tests examples

* fix: Updating UAT tests workflow and moving terra tests under one file

* fix: Appending Secret values directly to the file in UAT workflow

* fix: fixing setup variables files job in UAT workflow

* fix: deleting old terra tests files

* nit: fixing indentation

* misc:Updating workflow file

* misc:reverting the latest change in UAT workflow

* misc:Updating UAT workflow file and variable files

* fix: Updating variables files for examples

* fix: Adding project_id block in connection modules & examples

* fix: Adding project_id varaible in IBM2 example
Copy link
Collaborator

@thogarty thogarty left a comment

Choose a reason for hiding this comment

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

Changes requested.

# Metal to AWS Connection Example

This example shows how to leverage the [Metal Connection Module](../../modules/metalconnection/README.md)
to create a Fabric Connection from a Metal to AWS.
Copy link
Collaborator

Choose a reason for hiding this comment

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

Should be "to create a Fabric Connection from Equinix Metal to AWS"

purchase_order_number = "1-323292"
project_id = "<Project_ID>"
aside_ap_authentication_key = "<Metal_Auth_Token>"
aside_ap_type = "METAL_NETWORK"
Copy link
Collaborator

Choose a reason for hiding this comment

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

We should update this. The module has the variable as well but it will always be the same Access Point type for Metal Connection module, right?

required_providers {
equinix = {
source = "equinix/equinix"
version = ">= 1.20.0"
Copy link
Collaborator

Choose a reason for hiding this comment

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

We shouldn't add new content with old versions of the Terraform provider. This will need to be updated to be the latest version of the release after https://github.com/equinix/terraform-provider-equinix/pull/626/files#diff-703d45b76399eb49451408ebb9688abdad1236c9cfb95664c5044fe2488e19fb is merged into the provider.

Please refer to the metal-* examples in this module's registry for more details on how to leverage the submodule.

<!-- Begin Module Docs (Do not edit contents) -->
## Equinix Fabric Developer Documentation
Copy link
Collaborator

Choose a reason for hiding this comment

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

You don't need any content between these boundaries. It will be overwritten anyway.

}
a_side {
access_point {
type = var.aside_ap_type
Copy link
Collaborator

Choose a reason for hiding this comment

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

If this is truly a module for Metal then the Access Point will always be the same, right?

type = string
default = ""
}
variable "additional_info" {
Copy link
Collaborator

Choose a reason for hiding this comment

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

It should be marked sensitive here as well. We never know what will go in the additional info so we should prevent it from being exposed.

required_providers {
equinix = {
source = "equinix/equinix"
version = ">= 1.20.0"
Copy link
Collaborator

Choose a reason for hiding this comment

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

This needs to be updated with the latest version of the TF provider after the merge of this PR: https://github.com/equinix/terraform-provider-equinix/pull/626/files#diff-703d45b76399eb49451408ebb9688abdad1236c9cfb95664c5044fe2488e19fb

@@ -0,0 +1,13 @@
# Metal to AWS Connection Example
Copy link
Collaborator

Choose a reason for hiding this comment

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

The name of this directory doesn't follow our example naming patterns. Should be all lowercase, kebab case (which it is) and the module should be the prefix. Rename directory to metal-nimf-2-aws-connection/

@srushti-patl srushti-patl marked this pull request as draft April 2, 2024 21:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants