Open RFC2516 opened 1 year ago
Hi , I am looking at your ticket and reviewing it, Please let me know are you facing the issue still or not ?
Yes,
Less of an issue and more of a request for a new feature 😊
I did import the latest pyats[full] package and confirmed the feature is not there.
As we currently not supporting, we will add to backlog for support as per priority of customer need to resolve the issue you are facing in future. If you need further assistance, please let me know and I'll do my best to provide additional guidance.
Feature Request
I would like to not be restricted to using a testbed file in my PyATS usage. The reason for this is because my environment is ephemeral. The connection details change from environment to environment. I personally would prefer not to create an intermediary script, and I suspect others would too, that writes the testbed script after ingesting local environment details. In my opinion a yaml testbed file is ideal for human to programmatic interaction, however a yaml testbed file is not ideal for environmental discovery and programmatic interaction. Such as workflow again in my opinion should remain in the python script. I also acknowledge the Netbox Plugin but it is simply not practical for local development environment.
Current Examples:
vs.
Story
A Network Engineer is working on a proposed change to the infrastructure. They create a repository on their local, initialize git, use ansible for their configuration management, they also create a virtualization environment / orchestration tool definition yaml file, and now they need to write unit tests to prove their change is acceptable as well as providing the same test files that will move into production to allow for continuous testing of the new feature.
These inventory files, testbeds and etc. must survive being deployed into different environments.
Proposed experience of exposed unicon connection API