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
Natural key multi column csv export #4367
Comments
Hey team! Please add your planning poker estimate with Zenhub @bryanculver @glennmatthews @gsnider2195 @HanlinMiao @jathanism @timizuoebideri1 |
Should this be blocked by #4346? |
…`BaseModel`. (#4439) * Implemented `.natural_slug` property on all models that inherit from `BaseModel`. - Added `emoji` as a dependency - Added `python-slugify` as a dependency - Replaced `composite_key` with natural_slug` in public interfaces. - Left composite_key to serializers until after #4367 is complete. --------- Co-authored-by: Glenn Matthews <glenn.matthews@networktocode.com>
Due to M2M->CSV->M2M ugliness we are going to document not supporting M2Ms (except for tags) in CSV round trip and exclude testing for them for 2.0.0. Future follow on may find a way to re-introduce them, or provide multi-part forms to handle this (see how we've documented addressing CSV import of IPAddress-to-Interface assignments via #4103) |
As Ozzy the Operator, I want to be able to export Nautobot data that contains relationships to other data in a format that is clear and easy for me to understand.
I will know this is complete when CSV export supports multi column natural keys by allowing the various fields in a natural key to be separate fields in the export.
tenant__name
, so they are round-trippable.DEVICE_NAME_NATURAL_KEY
This is the inverse of #3794
The text was updated successfully, but these errors were encountered: