You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 11, 2024. It is now read-only.
Often users will have existing Tyk deployments either in different environments to those using the Operator or in existing Tyk deployments where the operator is to be onboarded. To move to the operator a user must manually create the CRDs which can be an onerous task.
We should be able to import an existing API definition and where possible template it onto a new CRD and pass that back. Preferably just as a CLI command for automation.
The dashboard may then import the package that does this work and export CRDs from our Cloud and On premise API Managers.
Current Behavior
No real solution to this currently.
Possible Solution
One option is to use Go templating to pass values from an inputted API definition JSON and create a CRD
Expected Behavior
Often users will have existing Tyk deployments either in different environments to those using the Operator or in existing Tyk deployments where the operator is to be onboarded. To move to the operator a user must manually create the CRDs which can be an onerous task.
We should be able to import an existing API definition and where possible template it onto a new CRD and pass that back. Preferably just as a CLI command for automation.
The dashboard may then import the package that does this work and export CRDs from our Cloud and On premise API Managers.
Current Behavior
No real solution to this currently.
Possible Solution
One option is to use Go templating to pass values from an inputted API definition JSON and create a CRD