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

netbox 3.6 support #167

Merged
merged 14 commits into from
Mar 27, 2024
Merged

netbox 3.6 support #167

merged 14 commits into from
Mar 27, 2024

Conversation

ryanmerolle
Copy link
Collaborator

@ryanmerolle ryanmerolle commented Oct 14, 2023

Pull Request

Related Issue

#159

New Behavior

Development:

  • devcontainer bumped to NetBox 3.6
  • migrate from vscode user given ubtuntu uid conflicts

NetBox Changes to investigate

  • The device_role field on the Device model has been renamed to role. The device_role field has been temporarily retained on the REST API serializer for devices for backward compatibility, but is read-only.
  • The choices array field has been removed from the CustomField model. Any defined choices are automatically migrated to CustomFieldChoiceSets, accessible via the new choice_set field on the CustomField model.
  • Introduce choice sets for custom fields netbox#12988 -Custom Field Choice Sets
  • Remove the custom ChoiceField and MultipleChoiceField subclasses netbox#11766 - Remove obsolete custom ChoiceField and MultipleChoiceField classes
  • The device_role field on the Device model has been renamed to role. The device_role field has been temporarily retained on the REST API serializer for devices for backward compatibility, but is read-only.

Contrast to Current Behavior

...

Discussion: Benefits and Drawbacks

...

Changes to the Documentation

...

Proposed Release Note Entry

...

Double Check

  • I have explained my PR according to the information in the comments
    or in a linked issue.
  • My PR targets the dev branch.

@ryanmerolle
Copy link
Collaborator Author

ryanmerolle commented Oct 14, 2023

@Cormoran96 @abhi1693 @jsenecal tagging for visibility.

I started looking at change for 3.6. Development in VS Code devcontainer now works, but all views except for ACL Interface Assignments are broken.

I'm not currently leveraging NetBox at my new job, but that will likely eventually change. Just explaining why this work is not already done.

@sonarcloud
Copy link

sonarcloud bot commented Oct 14, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@garnser
Copy link

garnser commented Jan 5, 2024

Tested, works for 3.7 as well

Copy link
Member

@abhi1693 abhi1693 left a comment

Choose a reason for hiding this comment

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

If my suggestion is not required, let's release these changes

.devcontainer/Dockerfile-plugin_dev Show resolved Hide resolved
Copy link

sonarcloud bot commented Jan 5, 2024

Quality Gate Failed Quality Gate failed

Failed conditions

2 Security Hotspots

See analysis details on SonarCloud

@jeffgdotorg
Copy link
Contributor

jeffgdotorg commented Mar 26, 2024

@abhi1693 @ryanmerolle between this PR and @kbelokon's draft PR #175, I think we have all the pieces to get this plugin working through NetBox 3.7. How do we break the logjam?

Let me know if you need me to remove any obstacles. The two hotspots identified by Sonar look okay to me; if you concur, and if the checks all pass after marking them safe, I'm a +1 to merging once the 3.7 changes are in.

PS I tested the fix branch for #175 in a 3.7.4 system and it did not blow up in my face.

@ryanmerolle ryanmerolle merged commit f0b4616 into dev Mar 27, 2024
9 checks passed
@ryanmerolle ryanmerolle deleted the netbox_3.6 branch March 27, 2024 04:09
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.

4 participants