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
This is a port of an existing issue for a templating CLI. Since that original CLI was developed, a lot has changed about the integrations project, and it's now outdated. Additionally, the needs of developers are much more nuanced, and the templating code is much trickier to port. As such, this issue introduces the idea of a smaller CLI.
What solution would you like?
There are a few tasks that can be automated to assist with integration development, without requiring a full templating tool. These include:
Automatically verify the schema of an integration against some data, to detect redundant or incorrectly configured fields.
Determine the fields used by an existing visualization in order to help port it to SS4O.
Tools for data generation.
Tools for code generation of ingestion configs such as:
Jaeger
FluentBit
Data Prepper
OTEL Collector
Logstash
Updated templating tools.
This code can go in the catalog repository, since the catalog is organizing a lot of information and documentation regarding integrations, and in the future we plan on maintaining integrations within the catalog.
What alternatives have you considered?
We can try to update the old CLI, but it's so outdated that it's more effort than it's worth, and trying to fix the templating will distract from implementing simpler functionality that can deliver more immediate value.
Is your feature request related to a problem?
This is a port of an existing issue for a templating CLI. Since that original CLI was developed, a lot has changed about the integrations project, and it's now outdated. Additionally, the needs of developers are much more nuanced, and the templating code is much trickier to port. As such, this issue introduces the idea of a smaller CLI.
What solution would you like?
There are a few tasks that can be automated to assist with integration development, without requiring a full templating tool. These include:
This code can go in the catalog repository, since the catalog is organizing a lot of information and documentation regarding integrations, and in the future we plan on maintaining integrations within the catalog.
What alternatives have you considered?
We can try to update the old CLI, but it's so outdated that it's more effort than it's worth, and trying to fix the templating will distract from implementing simpler functionality that can deliver more immediate value.
Do you have any additional context?
opensearch-project/observability#1451
The text was updated successfully, but these errors were encountered: