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

Velocloud Module - Allowing for multiple vEdge instances to be created #77

Merged
merged 24 commits into from
Nov 19, 2024

Conversation

zachreborn
Copy link
Owner

@zachreborn zachreborn commented Nov 5, 2024

Description

Expanding the scope of this module to be able to handle multiple deployments.

Issue or Ticket

N/A

Type of change

  • Bugfix
  • New feature
  • Version update

Breaking Changes

  • Yes
  • No

Breaking Changes Description

This change will break existing velocloud and transit_gateway_connect_peer module usage.

  • You will need to follow the new variable structure for the velocloud_activation_keys which was changed from velocloud_activation_key.
  • You will need to the new map input structure of peers. For more information, see the module readme.

TODOs

  • Validate your code matches the style of the project.
  • Update the docs.
  • Validate all tests run successfull, including pre-commit checks.
  • Include release notes and description. This should include both a summary of the changes and any necessary context.

@zachreborn zachreborn merged commit 40ba07a into main Nov 19, 2024
7 of 11 checks passed
@zachreborn zachreborn deleted the velocloud_ha_pair branch November 19, 2024 23:36
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.

1 participant