We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
rack_type
The following attributes of a rack_type each use maps keyed by attribute instance name:
This is an inelegant solution to two problems:
With both of these problems behind us it looks like these attributes can be either sets or lists.
Sets are possible/safe because each attribute has a name field which is required by Apstra to be unique.
name
Lists are possible because (we now believe) that Apstra preserves the order in which the object were submitted.
With that in mind, lists appear to be the best approach.
The text was updated successfully, but these errors were encountered:
chrismarget-j
No branches or pull requests
The following attributes of a
rack_type
each use maps keyed by attribute instance name:This is an inelegant solution to two problems:
With both of these problems behind us it looks like these attributes can be either sets or lists.
Sets are possible/safe because each attribute has a
name
field which is required by Apstra to be unique.Lists are possible because (we now believe) that Apstra preserves the order in which the object were submitted.
With that in mind, lists appear to be the best approach.
The text was updated successfully, but these errors were encountered: