-
Notifications
You must be signed in to change notification settings - Fork 30
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
Use nest custom fields (subnets) #86
Conversation
@lord-kyron , @pavel-z1 any updates on this ? |
Hi @d-costa Please, add information about optional config parameter After this the PR will be approved. Maybe you can add nested custom fields support to the address and vlans too? |
@d-costa can you fix description to move forward with PR? |
@d-costa can you please update description? |
hey @pavel-z1, sorry for the delay. I've updated |
docs/index.md
Outdated
@@ -109,6 +109,9 @@ The options for the plugin are as follows: | |||
supplied via the `PHPIPAM_USER_NAME` variable. | |||
- `insecure` - Set to true to not validate the HTTPS certificate chain. | |||
Optional parameter, can be used only with HTTPS connections | |||
- `nest_custom_fields` - Set to true if your PHPIPAM application has the nested | |||
custom fields feature enabled. ptional parameter, currently only affects |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Small typo
Please correct it to Optional parameter
@d-costa Thank you for your work! |
What
Use nested custom fields SDK feature for subnet resources.
nest_custom_fields
. Defaults to false (opt-in).resource_phpipam_first_free_subnet
andresource_phpipam_subnet
resources, but the same methodology can be applied for VLAN and Address resourcesWhy
Ref
Tests
Its behavior is described in the table below:
false
false
true
true
true
false
false
true
[1]
[2]
Unit tests
make test
Output
Acceptance tests (Nest custom fields = no)
Details