Skip to content

How should platforming, revisioning, and versioning be combined? #991

@MilosQL

Description

@MilosQL

OS directories may also contain additional subdirectories for specific platforms when command behavior differs between them. For example:

  • iosxe/asr1k/show_platform.py
  • iosxe/cat3k/c3850/show_platform.py

The documentation also explains the differences between schema revisioning and output versioning, and how each of these mechanisms individually affects the parser directory structure.

Since all three cases (platform-specific variations, schema revisions, and versioning) can potentially apply at different points in time, complex combinations seem possible. For example, revisioning may occur after multiple version changes, followed by platform-specific deviations, followed again by additional revision changes affecting only certain platforms.

Is combining these mechanisms supported, and if so, what are the rules or recommended structure for doing so?

Does folder-based testing (i.e., the tests/folder_parsing_job.py script) support this kind of mixed nesting across platform, revision, and version layers?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions