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

Clarify docs for migration of ipam coupling to dnssync #443

Merged
merged 3 commits into from
Oct 18, 2024

Conversation

Stathogon
Copy link
Contributor

Hello,
i just migrated my netbox to use DNSSync and was a bit confused what to do with the custom fields. Added a Clarification to the docs so it is easier to see.

In my Opinion it wasnt clear what to do with the custom fields of the old IPAM coupling. I added a paragraph that clarifies that it doesnt have to be done manually.
Copy link
Owner

@peteeckel peteeckel left a comment

Choose a reason for hiding this comment

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

Hi @Stathogon, thanks for this! It's always difficult to write documentation for things you don't need documented for yourself, so this is valuable input.

Could you please just remove the extraneous whitespace between "to the" and "new IPAM DNSSync"?

@Stathogon
Copy link
Contributor Author

i edited the file in the Commit? im not to familiar with git/github, i hope it achieved what i wanted. Atleast for me it looks fine now

Copy link
Owner

@peteeckel peteeckel left a comment

Choose a reason for hiding this comment

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

Yep, thanks!

@peteeckel
Copy link
Owner

peteeckel commented Oct 18, 2024

Generally, if you want to make changes to a PR it's sufficient to change files in your local repository, commit and push to GitHub again.

@peteeckel peteeckel merged commit 5a5c7e0 into peteeckel:main Oct 18, 2024
4 checks passed
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.

2 participants