Skip to content

9604 Add Termination to CircuitTermination #17821

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

Merged
merged 41 commits into from
Oct 31, 2024

Conversation

arthanson
Copy link
Collaborator

@arthanson arthanson commented Oct 21, 2024

Fixes: #9604

As per review comments:

  • Changed from using scope to termination
  • changed _sitegroup to _site_group
  • changed related names to not use underscore

@jeremystretch jeremystretch added this to the v4.2 milestone Oct 22, 2024
@arthanson arthanson changed the title DRAFT: 9604 Add Scope to CircuitTermination 9604 Add Scope to CircuitTermination Oct 22, 2024
@arthanson arthanson marked this pull request as ready for review October 22, 2024 20:58
@jeremystretch
Copy link
Member

I was under the impression that ProviderNetwork would be one of the scope choices, rather than remaining as a standalone, alternative field. Is there a reason not to make this one of the options for the scope GFK? (The current site and provider_network ForeignKey fields are already mutually exclusive.)

@arthanson arthanson changed the title 9604 Add Scope to CircuitTermination 9604 Add Termination to CircuitTermination Oct 30, 2024
@jeremystretch jeremystretch merged commit a8eb455 into feature Oct 31, 2024
6 checks passed
@jeremystretch jeremystretch deleted the 9604-circuit-termination-location-2 branch October 31, 2024 13:55
@gjvc
Copy link

gjvc commented Nov 13, 2024

Great to see this complete, thank you all very much!

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 14, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants