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

consider moving the platform-specific datatypes from the core schemas to their corresponding component schemas #61

Open
zport opened this issue Jan 14, 2019 · 0 comments

Comments

@zport
Copy link
Contributor

zport commented Jan 14, 2019

@djhaynes commented on Fri Aug 16 2013

We have a few datatypes that are platform-specific and are only used in the
corresponding component schemas. We should consider moving them out of the
core schemas and into the appropriate component schemas. Platform-specific
datatypes include:

evr_string (linux)
fileset_revision (hp-ux)
ios_version (cisco ios)


@djhaynes commented on Fri Aug 16 2013

We will defer this issue to a later release after version 5.10.

Resolving this issue will require a significant refactoring of the schema. The
most significant challenge here is supporting the use of platform specific
datatypes in variables. One possible solution would be to simply restrict
variables to only use primitive datatypes like int, string, boolean, etc. Doing
so would be a significant restriction in variable support.

On the other hand, it is not clear that these platform specific datatypes are
ever used in variables.


@solind commented on Tue Aug 30 2016

Punting to 5.12.

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

No branches or pull requests

1 participant