conversation listlengths 2 2 | source stringlengths 35 111 | score int64 5 5 |
|---|---|---|
[
{
"from": "human",
"value": "What is the primary purpose of the Choreo Marketplace?"
},
{
"from": "gpt",
"value": "The Choreo Marketplace primarily promotes and facilitates the reuse and sharing of services. It enables users to share all services deployed within Choreo and allows others to easil... | docs\choreo-concepts\choreo-marketplace.md/Choreo Marketplace | 5 |
[
{
"from": "human",
"value": "What types of content can users find and refer to within the Choreo Marketplace for available services?"
},
{
"from": "gpt",
"value": "Within the Choreo Marketplace, users can find and refer to service definitions, documentation, and instructions on how to use the av... | docs\choreo-concepts\choreo-marketplace.md/Choreo Marketplace | 5 |
[
{
"from": "human",
"value": "Why is effective discoverability desirable in the Choreo Marketplace?"
},
{
"from": "gpt",
"value": "Effective discoverability is desirable in the Choreo Marketplace because it includes all services deployed in an organization, which can be a large number of services... | docs\choreo-concepts\choreo-marketplace.md/Discover services | 5 |
[
{
"from": "human",
"value": "What are the two primary methods available for users to explore services in the Choreo Marketplace?"
},
{
"from": "gpt",
"value": "The two primary methods available for users to explore services in the Choreo Marketplace are using the search bar or applying various f... | docs\choreo-concepts\choreo-marketplace.md/Discover services | 5 |
[
{
"from": "human",
"value": "Where is the search bar located in the Choreo Marketplace interface?"
},
{
"from": "gpt",
"value": "The search bar in the Choreo Marketplace interface is located at the top, providing universal searching capabilities."
}
] | docs\choreo-concepts\choreo-marketplace.md/Search | 5 |
[
{
"from": "human",
"value": "What are the specific search attributes that the top search bar in the Choreo Marketplace allows users to search for text within?"
},
{
"from": "gpt",
"value": "The top search bar in the Choreo Marketplace allows users to search for text within the following specific... | docs\choreo-concepts\choreo-marketplace.md/Search | 5 |
[
{
"from": "human",
"value": "What does the 'All' search attribute encompass when searching for services in the Choreo Marketplace?"
},
{
"from": "gpt",
"value": "When searching for services in the Choreo Marketplace, the 'All' search attribute encompasses the service name, service labels, and se... | docs\choreo-concepts\choreo-marketplace.md/Search | 5 |
[
{
"from": "human",
"value": "How is the filtering capability provided in the Choreo Marketplace?"
},
{
"from": "gpt",
"value": "The filtering capability in the Choreo Marketplace is provided through a left-hand side filter panel."
}
] | docs\choreo-concepts\choreo-marketplace.md/Filter | 5 |
[
{
"from": "human",
"value": "What are the two available options for the 'Type' filter attribute in the Choreo Marketplace, and what do they represent?"
},
{
"from": "gpt",
"value": "The two available options for the 'Type' filter attribute in the Choreo Marketplace are 'Internal' and 'Third-part... | docs\choreo-concepts\choreo-marketplace.md/Filter | 5 |
[
{
"from": "human",
"value": "What are the three choices for the 'Network Visibility' filter attribute in the Choreo Marketplace, and what level of exposure does each choice represent?"
},
{
"from": "gpt",
"value": "The three choices for the 'Network Visibility' filter attribute in the Choreo Mar... | docs\choreo-concepts\choreo-marketplace.md/Filter | 5 |
[
{
"from": "human",
"value": "How can a user access the detailed view of a service in the Choreo Marketplace?"
},
{
"from": "gpt",
"value": "A user can access the detailed view of a service in the Choreo Marketplace by clicking on the service card."
}
] | docs\choreo-concepts\choreo-marketplace.md/Explore a service | 5 |
[
{
"from": "human",
"value": "What information is featured in the header of a detailed service page in the Choreo Marketplace?"
},
{
"from": "gpt",
"value": "The header of a detailed service page in the Choreo Marketplace features the service name, summary, version, labels, and service icon."
}... | docs\choreo-concepts\choreo-marketplace.md/Explore a service | 5 |
[
{
"from": "human",
"value": "How does Choreo organize the content of a service's detailed view, and what are the four main tabs?"
},
{
"from": "gpt",
"value": "Choreo organizes the content of a service's detailed view into four tabs. The four main tabs are 'Overview,' 'API definition,' 'How to u... | docs\choreo-concepts\choreo-marketplace.md/Explore a service | 5 |
[
{
"from": "human",
"value": "What kind of information is displayed in the 'Overview' tab of a service's detailed view in the Choreo Marketplace, and when is this section disabled?"
},
{
"from": "gpt",
"value": "The 'Overview' tab of a service's detailed view in the Choreo Marketplace displays th... | docs\choreo-concepts\choreo-marketplace.md/Explore a service | 5 |
[
{
"from": "human",
"value": "How can a service developer provide or update the overview content for a service in the Choreo Marketplace?"
},
{
"from": "gpt",
"value": "A service developer can provide or update the overview content for a service in the Choreo Marketplace via the 'Manage → Marketp... | docs\choreo-concepts\choreo-marketplace.md/Explore a service | 5 |
[
{
"from": "human",
"value": "What information is included in the 'API definition' tab of a service's detailed view in the Choreo Marketplace, and where is this definition extracted from?"
},
{
"from": "gpt",
"value": "The 'API definition' tab of a service's detailed view in the Choreo Marketplac... | docs\choreo-concepts\choreo-marketplace.md/Explore a service | 5 |
[
{
"from": "human",
"value": "What happens if an API definition is not provided for a service in the Choreo Marketplace?"
},
{
"from": "gpt",
"value": "If an API definition is not provided for a service in the Choreo Marketplace, the 'API definition' tab will be empty."
}
] | docs\choreo-concepts\choreo-marketplace.md/Explore a service | 5 |
[
{
"from": "human",
"value": "What kind of instructions are included in the 'How to use' tab of a service's detailed view in the Choreo Marketplace?"
},
{
"from": "gpt",
"value": "The 'How to use' tab of a service's detailed view in the Choreo Marketplace includes instructions on how to use the s... | docs\choreo-concepts\choreo-marketplace.md/Explore a service | 5 |
[
{
"from": "human",
"value": "What information is included in the 'Related documents' tab of a service's detailed view in the Choreo Marketplace, and how is this content provided?"
},
{
"from": "gpt",
"value": "The 'Related documents' tab of a service's detailed view in the Choreo Marketplace inc... | docs\choreo-concepts\choreo-marketplace.md/Explore a service | 5 |
[
{
"from": "human",
"value": "What is the general method for adding services to the Choreo Marketplace?"
},
{
"from": "gpt",
"value": "Services can be added to the Choreo Marketplace as Choreo services."
}
] | docs\choreo-concepts\choreo-marketplace.md/Add a service to the Choreo Marketplace | 5 |
[
{
"from": "human",
"value": "How is a service exposed through the Choreo platform termed, and how is it identifiable?"
},
{
"from": "gpt",
"value": "A service exposed through the Choreo platform is termed a Choreo service, and each such service is identifiable by an endpoint within a Choreo serv... | docs\choreo-concepts\choreo-marketplace.md/Add a Choreo service | 5 |
[
{
"from": "human",
"value": "When do services automatically get added to the Choreo Marketplace?"
},
{
"from": "gpt",
"value": "Services automatically get added to the Choreo Marketplace upon deployment to the initial environment."
}
] | docs\choreo-concepts\choreo-marketplace.md/Add a Choreo service | 5 |
[
{
"from": "human",
"value": "What essential details does Choreo automatically collect during deployment to generate service entries in the Marketplace?"
},
{
"from": "gpt",
"value": "During deployment, Choreo effortlessly collects essential details such as the component name, endpoint name, desc... | docs\choreo-concepts\choreo-marketplace.md/Add a Choreo service | 5 |
[
{
"from": "human",
"value": "What is the naming convention for a service in the Choreo Marketplace, and what happens to other details?"
},
{
"from": "gpt",
"value": "The service name in the Choreo Marketplace follows the convention of `component name - endpoint name`, while all other details col... | docs\choreo-concepts\choreo-marketplace.md/Add a Choreo service | 5 |
[
{
"from": "human",
"value": "How are service versions displayed in the Choreo Marketplace?"
},
{
"from": "gpt",
"value": "In the Choreo Marketplace, service versions are displayed in their major version format."
}
] | docs\choreo-concepts\choreo-marketplace.md/Service versioning in the Choreo Marketplace | 5 |
[
{
"from": "human",
"value": "What does each service entry in the Choreo Marketplace represent regarding its version?"
},
{
"from": "gpt",
"value": "Each service in the Choreo Marketplace represents the latest version of the service within its major version, following semantic versioning principl... | docs\choreo-concepts\choreo-marketplace.md/Service versioning in the Choreo Marketplace | 5 |
[
{
"from": "human",
"value": "What happens to a service entry in the Choreo Marketplace when a new minor version of an already deployed service is released?"
},
{
"from": "gpt",
"value": "When a new minor version of a service already deployed in Choreo is released, the corresponding service in th... | docs\choreo-concepts\choreo-marketplace.md/Service versioning in the Choreo Marketplace | 5 |
[
{
"from": "human",
"value": "What is the benefit of using a service from the Choreo Marketplace as a dependency regarding traffic routing?"
},
{
"from": "gpt",
"value": "When a service from the Choreo Marketplace is used as a dependency, the dependent service's traffic automatically routes to th... | docs\choreo-concepts\choreo-marketplace.md/Semantic-version-based intelligent routing in the Choreo Marketplace | 5 |
[
{
"from": "human",
"value": "Provide an example to illustrate how semantic-version-based intelligent routing works when a dependent service connects to a Choreo Marketplace service."
},
{
"from": "gpt",
"value": "For example, if a Choreo component named `Foo` connects to a Choreo service named `... | docs\choreo-concepts\choreo-marketplace.md/Semantic-version-based intelligent routing in the Choreo Marketplace | 5 |
[
{
"from": "human",
"value": "What aspects of a service in the Choreo Marketplace are automatically updated during redeployment to any environment?"
},
{
"from": "gpt",
"value": "During redeployment to any environment, Choreo automatically updates service definitions, visibility, and descriptions... | docs\choreo-concepts\choreo-marketplace.md/Edit services in the Choreo Marketplace | 5 |
[
{
"from": "human",
"value": "What is the primary purpose of Choreo's CI/CD experience?"
},
{
"from": "gpt",
"value": "Choreo provides a streamlined continuous integration and continuous deployment (CI/CD) experience designed to efficiently deploy applications and services across multiple environ... | docs\choreo-concepts\ci-cd.md/CI/CD | 5 |
[
{
"from": "human",
"value": "How does Choreo organize environments for projects, and what are the characteristics of these environments?"
},
{
"from": "gpt",
"value": "Choreo creates environments for each project, where all components within the project share these environments. An environment i... | docs\choreo-concepts\ci-cd.md/CI/CD | 5 |
[
{
"from": "human",
"value": "What are the default environments provided by the Choreo cloud data plane, and how can environments be customized in a private data plane organization?"
},
{
"from": "gpt",
"value": "The Choreo cloud data plane provides two default environments: development and produ... | docs\choreo-concepts\ci-cd.md/CI/CD | 5 |
[
{
"from": "human",
"value": "Explain Choreo's 'build once, deploy many' strategy for managing components across multiple environments."
},
{
"from": "gpt",
"value": "Choreo adopts a 'build once, deploy many' strategy, meaning an application is built only once (either per commit if automatic buil... | docs\choreo-concepts\ci-cd.md/CI/CD | 5 |
[
{
"from": "human",
"value": "How does Choreo handle configurations and secrets in relation to source code and environments?"
},
{
"from": "gpt",
"value": "Choreo injects configurations and secrets, which are maintained at the environment level, into components at runtime. This approach ensures a... | docs\choreo-concepts\ci-cd.md/CI/CD | 5 |
[
{
"from": "human",
"value": "What types of configurations and secrets can be injected into components at runtime in Choreo?"
},
{
"from": "gpt",
"value": "Configurations and secrets that can be injected include resource credentials for databases, caches, or other backing services, as well as cre... | docs\choreo-concepts\ci-cd.md/CI/CD | 5 |
[
{
"from": "human",
"value": "How are configurations and secrets secured in Choreo, and where can they be stored in a private data plane organization?"
},
{
"from": "gpt",
"value": "All configurations and secrets are encrypted at rest and in transit and are stored in a secure vault. In a private ... | docs\choreo-concepts\ci-cd.md/CI/CD | 5 |
[
{
"from": "human",
"value": "Describe the general steps involved in Choreo's auto-generated build pipelines."
},
{
"from": "gpt",
"value": "Generally, Choreo's auto-generated build pipelines, which may slightly differ by component type, perform the following steps: they build a container image f... | docs\choreo-concepts\ci-cd.md/Build | 5 |
[
{
"from": "human",
"value": "Can unit tests be integrated into Choreo's build pipeline, and where can more details be found?"
},
{
"from": "gpt",
"value": "Yes, some buildpacks in Choreo support integrating unit tests into the build pipeline. More details can be found in the documentation sectio... | docs\choreo-concepts\ci-cd.md/Build | 5 |
[
{
"from": "human",
"value": "What does 'repeatable builds' mean in Choreo, and what is the policy regarding multiple builds from the same code version?"
},
{
"from": "gpt",
"value": "Repeatable builds in Choreo mean that the system can replicate builds from an identical code version (Git commit)... | docs\choreo-concepts\ci-cd.md/Build | 5 |
[
{
"from": "human",
"value": "How can a user manually trigger a build in Choreo, and what additional option is available for Admin and Choreo DevOps users?"
},
{
"from": "gpt",
"value": "To manually trigger a build, a user can go to the 'Build' page and click 'Build Latest'. If necessary, they al... | docs\choreo-concepts\ci-cd.md/Build | 5 |
[
{
"from": "human",
"value": "How can a user configure Choreo to automatically trigger a build?"
},
{
"from": "gpt",
"value": "To automatically trigger a build with each commit, a user can enable the 'Auto Build on Commit' setting."
}
] | docs\choreo-concepts\ci-cd.md/Build | 5 |
[
{
"from": "human",
"value": "Where can users view build logs and access detailed information for specific builds in Choreo?"
},
{
"from": "gpt",
"value": "Users can view build logs for specific builds on the 'Build' page. To view details of a specific build, they need to click 'View Details' cor... | docs\choreo-concepts\ci-cd.md/Build | 5 |
[
{
"from": "human",
"value": "What are the two main approaches for deploying an image in Choreo once it has been built?"
},
{
"from": "gpt",
"value": "Once an image is built in Choreo, it can be deployed via the 'Deploy' page using one of two approaches: either manually by going to the 'Set Up' c... | docs\choreo-concepts\ci-cd.md/Deployment | 5 |
[
{
"from": "human",
"value": "What is a prerequisite for enabling 'Auto Deploy on Build' in Choreo, and why is it necessary?"
},
{
"from": "gpt",
"value": "To enable 'Auto Deploy on Build', 'Auto Build on Commit' must be enabled. This is because automatic deployment is not necessary or useful in ... | docs\choreo-concepts\ci-cd.md/Deployment | 5 |
[
{
"from": "human",
"value": "What special consideration applies to the first build of a Ballerina component regarding deployment and configurations?"
},
{
"from": "gpt",
"value": "For a Ballerina component, the first build must be triggered manually to ensure that Choreo applies the required con... | docs\choreo-concepts\ci-cd.md/Deployment | 5 |
[
{
"from": "human",
"value": "How does Choreo handle configurable values for Ballerina components during deployment, and what is the implication if configurables are changed?"
},
{
"from": "gpt",
"value": "Choreo automatically checks the configurable values defined in a Ballerina component's sour... | docs\choreo-concepts\ci-cd.md/Deployment | 5 |
[
{
"from": "human",
"value": "What are the responsibilities of a user when managing configurations for Dockerfile-based components in Choreo?"
},
{
"from": "gpt",
"value": "For Dockerfile-based components, users must manually manage and update the configurations and secrets in environments ahead ... | docs\choreo-concepts\ci-cd.md/Deployment | 5 |
[
{
"from": "human",
"value": "What is the 'setup area' in Choreo's deploy phase, and what is its role in the initial deployment?"
},
{
"from": "gpt",
"value": "In the deploy phase, Choreo uses a 'setup area' to merge the Docker image with its environment-independent configurations. This composite... | docs\choreo-concepts\ci-cd.md/Deployment | 5 |
[
{
"from": "human",
"value": "What does it mean for deployments to be 'immutable' in Choreo, and what happens if configurations are changed after deployment?"
},
{
"from": "gpt",
"value": "Once Choreo deploys a component with configurations, those configurations become immutable. Any subsequent c... | docs\choreo-concepts\ci-cd.md/Deployment | 5 |
[
{
"from": "human",
"value": "How does Choreo facilitate the promotion of a component to higher environments?"
},
{
"from": "gpt",
"value": "Choreo builds a container once per GitHub commit and then allows it to be promoted to subsequent higher environments. Users can manually promote a component... | docs\choreo-concepts\ci-cd.md/Deployment | 5 |
[
{
"from": "human",
"value": "What are the two types of configurations Choreo allows users to define?"
},
{
"from": "gpt",
"value": "Choreo allows users to define both environment-independent configurations and environment-specific configurations."
}
] | docs\choreo-concepts\ci-cd.md/Configurations | 5 |
[
{
"from": "human",
"value": "How do environment-independent configurations apply, and what is the process for changing them?"
},
{
"from": "gpt",
"value": "Environment-independent configurations apply to all environments. To change them, users must go to the 'Deploy' page of the component, make ... | docs\choreo-concepts\ci-cd.md/Configurations | 5 |
[
{
"from": "human",
"value": "How do environment-specific configurations apply, and what is the process for changing them?"
},
{
"from": "gpt",
"value": "Environment-specific configurations apply to a particular environment. To change them, users need to go to the 'Deploy' page of the component, ... | docs\choreo-concepts\ci-cd.md/Configurations | 5 |
[
{
"from": "human",
"value": "For which component types is the information on the 'Execute' page applicable?"
},
{
"from": "gpt",
"value": "The information on the 'Execute' page is only applicable to scheduled and manual task components."
}
] | docs\choreo-concepts\ci-cd.md/Task execution | 5 |
[
{
"from": "human",
"value": "What kind of information can users track and monitor on the 'Execute' page for scheduled and manual tasks?"
},
{
"from": "gpt",
"value": "On the 'Execute' page, users can track and monitor current and historic execution details, along with a quick snapshot of recent ... | docs\choreo-concepts\ci-cd.md/Task execution | 5 |
[
{
"from": "human",
"value": "What are the benefits of the information provided on the 'Execute' page?"
},
{
"from": "gpt",
"value": "The information on the 'Execute' page enhances transparency, troubleshooting capabilities, and overall execution management, allowing users to easily monitor and a... | docs\choreo-concepts\ci-cd.md/Task execution | 5 |
[
{
"from": "human",
"value": "How does Choreo ensure zero downtime during deployments and promotions?"
},
{
"from": "gpt",
"value": "Choreo performs rolling updates to ensure zero downtime between deployments and promotions."
}
] | docs\choreo-concepts\ci-cd.md/Zero-downtime deployments | 5 |
[
{
"from": "human",
"value": "What role do health checks play in Choreo's deployment process?"
},
{
"from": "gpt",
"value": "A new build undergoes a health check before traffic is switched to it from the current build. If the necessary health checks are configured for a component, they can preven... | docs\choreo-concepts\ci-cd.md/Zero-downtime deployments | 5 |
[
{
"from": "human",
"value": "What is the fundamental definition of a component within a project in Choreo?"
},
{
"from": "gpt",
"value": "A component within a project in Choreo represents a single unit of work in a cloud native application."
}
] | docs\choreo-concepts\component.md/# Definition and Characteristics of a Component | 5 |
[
{
"from": "human",
"value": "What are common examples of what a component typically represents in Choreo?"
},
{
"from": "gpt",
"value": "A component in Choreo is usually a single microservice, API, or job/task."
}
] | docs\choreo-concepts\component.md/# Definition and Characteristics of a Component | 5 |
[
{
"from": "human",
"value": "How is a component in Choreo linked to its source code or build instructions?"
},
{
"from": "gpt",
"value": "Each component in Choreo is attached to a given directory path in a Git repository. This directory path either contains the program source code or a Dockerfil... | docs\choreo-concepts\component.md/# Definition and Characteristics of a Component | 5 |
[
{
"from": "human",
"value": "What is considered Choreo's fundamental unit of deployment?"
},
{
"from": "gpt",
"value": "A component is Choreo’s unit of deployment."
}
] | docs\choreo-concepts\component.md/# Component Deployment and Scaling | 5 |
[
{
"from": "human",
"value": "How does a Choreo component map to the underlying infrastructure at deployment time?"
},
{
"from": "gpt",
"value": "Each component in Choreo maps to a single pod in the Kubernetes cluster (data plane) at deployment time."
}
] | docs\choreo-concepts\component.md/# Component Deployment and Scaling | 5 |
[
{
"from": "human",
"value": "What capabilities does Choreo offer regarding the deployment, management, and scaling of individual components?"
},
{
"from": "gpt",
"value": "In Choreo, you can deploy, manage, and scale each component independently."
}
] | docs\choreo-concepts\component.md/# Component Deployment and Scaling | 5 |
[
{
"from": "human",
"value": "Does Choreo support different types of components, and if so, what is the purpose of this variety?"
},
{
"from": "gpt",
"value": "Yes, Choreo supports different component types for various use cases."
}
] | docs\choreo-concepts\component.md/# Component Types and Features | 5 |
[
{
"from": "human",
"value": "What are some examples of the various component types supported by Choreo?"
},
{
"from": "gpt",
"value": "Component types supported by Choreo include services, API proxies, integrations, web applications, and others."
}
] | docs\choreo-concepts\component.md/# Component Types and Features | 5 |
[
{
"from": "human",
"value": "Do different component types in Choreo possess unique features?"
},
{
"from": "gpt",
"value": "Yes, each component type in Choreo hosts unique features based on its characteristics."
}
] | docs\choreo-concepts\component.md/# Component Types and Features | 5 |
[
{
"from": "human",
"value": "Can you provide an example of a specific feature tied to a particular component type in Choreo?"
},
{
"from": "gpt",
"value": "For example, a scheduled integration component can accept a cron expression as a configuration to schedule an integration job/task."
}
] | docs\choreo-concepts\component.md/# Component Types and Features | 5 |
[
{
"from": "human",
"value": "What are the two main forms in which services can exist, and what role do 'Connections' play in integrating them within Choreo?"
},
{
"from": "gpt",
"value": "Services can exist in two main forms: standalone and integrated. Connecting services is an integral part of ... | docs\choreo-concepts\connections.md/Connections | 5 |
[
{
"from": "human",
"value": "How does Choreo facilitate the integration of services using Connections, specifically regarding the information provided and its usage?"
},
{
"from": "gpt",
"value": "Upon creating a connection to a service on Choreo, Choreo provides a Connection ID along with a set... | docs\choreo-concepts\connections.md/Connections | 5 |
[
{
"from": "human",
"value": "Explain the runtime mechanism of Choreo Connections and the primary benefit of this approach for developers."
},
{
"from": "gpt",
"value": "At runtime, Choreo dynamically injects values into the environment variables based on the configured mapping. This approach ens... | docs\choreo-concepts\connections.md/Connections | 5 |
[
{
"from": "human",
"value": "What are the two different visibility levels available for adding Connections in Choreo?"
},
{
"from": "gpt",
"value": "You can add Connections in two different visibility levels: Project and Component."
}
] | docs\choreo-concepts\connections.md/Visibility Levels | 5 |
[
{
"from": "human",
"value": "What is the primary purpose and scope of Project Connections in Choreo?"
},
{
"from": "gpt",
"value": "Project Connections are created to connect to services within a particular project. Their primary scope is that they can be used by any component within that specif... | docs\choreo-concepts\connections.md/Project Connections | 5 |
[
{
"from": "human",
"value": "Provide an example scenario where using a Project Connection would be beneficial."
},
{
"from": "gpt",
"value": "An example scenario where a Project Connection would be beneficial is if you want to share a third-party service, such as Twilio, across an entire project... | docs\choreo-concepts\connections.md/Project Connections | 5 |
[
{
"from": "human",
"value": "How do components refer to Project Connections, and what is the implication for OAuth security schemes when using Project Connections to consume Choreo services?"
},
{
"from": "gpt",
"value": "Components can refer to Project Connections using the connection ID. When ... | docs\choreo-concepts\connections.md/Project Connections | 5 |
[
{
"from": "human",
"value": "What is the definition and usage scope of Component Connections in Choreo?"
},
{
"from": "gpt",
"value": "Component Connections are defined at the component level and are used exclusively by only that specific component."
}
] | docs\choreo-concepts\connections.md/Component Connections | 5 |
[
{
"from": "human",
"value": "Give an example of a situation where a Component Connection would be the appropriate choice."
},
{
"from": "gpt",
"value": "An example of a situation where a Component Connection would be appropriate is if you want to connect a legacy service specifically to a given ... | docs\choreo-concepts\connections.md/Component Connections | 5 |
[
{
"from": "human",
"value": "How do components refer to Component Connections, and what is the behavior regarding OAuth security schemes if a component consumes multiple Choreo services via Component Connections?"
},
{
"from": "gpt",
"value": "Components can refer to the Component Connection usi... | docs\choreo-concepts\connections.md/Component Connections | 5 |
[
{
"from": "human",
"value": "What are the two key components of Choreo's architecture, and what are their primary responsibilities?"
},
{
"from": "gpt",
"value": "Choreo's architecture comprises two key components: the control plane and the data plane. The control plane handles essential tasks s... | docs\choreo-concepts\data-planes.md/Data Planes | 5 |
[
{
"from": "human",
"value": "What type of service is the Choreo control plane, and what does it manage?"
},
{
"from": "gpt",
"value": "The Choreo control plane is a SaaS (Software as a Service) that manages all cloud data planes and private data planes."
}
] | docs\choreo-concepts\data-planes.md/Data Planes | 5 |
[
{
"from": "human",
"value": "Which user personas are catered to by the Choreo control plane?"
},
{
"from": "gpt",
"value": "The Choreo control plane caters to diverse user personas, including CIOs, architects, developers, DevOps, site reliability engineers, and platform engineers."
}
] | docs\choreo-concepts\data-planes.md/Data Planes | 5 |
[
{
"from": "human",
"value": "What types of user applications can be deployed in the Choreo data plane, and what approach is supported for programming languages?"
},
{
"from": "gpt",
"value": "User applications deployed in the Choreo data plane can range from services and web applications to APIs... | docs\choreo-concepts\data-planes.md/Data Planes | 5 |
[
{
"from": "human",
"value": "How does the Choreo data plane ensure the containment of user data and traffic?"
},
{
"from": "gpt",
"value": "All traffic related to the runtime of user applications is restricted to the Choreo data plane, ensuring strict containment of user data within its boundari... | docs\choreo-concepts\data-planes.md/Data Planes | 5 |
[
{
"from": "human",
"value": "What are the two distinct types of data planes featured in Choreo's architecture, and how do they differ in their infrastructure models?"
},
{
"from": "gpt",
"value": "Choreo's architecture features two distinct data plane types: cloud data planes and private data pl... | docs\choreo-concepts\data-planes.md/Data Planes | 5 |
[
{
"from": "human",
"value": "On which platforms can Choreo private data planes be deployed?"
},
{
"from": "gpt",
"value": "Choreo private data planes can be deployed with almost all major cloud providers, such as Azure, AWS, and GCP, and are also compatible with on-premises infrastructure."
}
... | docs\choreo-concepts\data-planes.md/Private data planes - Infrastructure | 5 |
[
{
"from": "human",
"value": "What are the essential infrastructure requirements for a Choreo private data plane?"
},
{
"from": "gpt",
"value": "The essential requirements for a private data plane include upstream-compatible Kubernetes clusters, a container registry, a key vault (secret store), a... | docs\choreo-concepts\data-planes.md/Private data planes - Infrastructure | 5 |
[
{
"from": "human",
"value": "How is the Choreo Private Data Plane (PDP) system set up on Kubernetes infrastructure?"
},
{
"from": "gpt",
"value": "Setting up the Choreo PDP system involves using a Helm installation on the Kubernetes infrastructure."
}
] | docs\choreo-concepts\data-planes.md/Private data planes - System components | 5 |
[
{
"from": "human",
"value": "Which software components are installed during the Helm execution for setting up a Choreo Private Data Plane?"
},
{
"from": "gpt",
"value": "The following software components are installed during the Helm execution: Cilium CNI and service mesh, Choreo API Gateways an... | docs\choreo-concepts\data-planes.md/Private data planes - System components | 5 |
[
{
"from": "human",
"value": "How do the software components within a Choreo Private Data Plane receive updates, including security patches and bug fixes?"
},
{
"from": "gpt",
"value": "All software components within a Choreo Private Data Plane receive automatic updates, including security patche... | docs\choreo-concepts\data-planes.md/Private data planes - System components | 5 |
[
{
"from": "human",
"value": "What is the general direction of communication between the private data plane and the Choreo control plane, and what network configuration is typically not required from the PDP's perspective?"
},
{
"from": "gpt",
"value": "All communication between the private data ... | docs\choreo-concepts\data-planes.md/Private data planes - Connectivity with the control plane | 5 |
[
{
"from": "human",
"value": "What action is necessary if an organization's network restricts all outbound traffic for a private data plane's communication with the control plane?"
},
{
"from": "gpt",
"value": "If an organization's network restricts all outbound traffic, it is necessary to permit... | docs\choreo-concepts\data-planes.md/Private data planes - Connectivity with the control plane | 5 |
[
{
"from": "human",
"value": "Describe the communication pathways, directions, and protocols for the Choreo PDP agent's connectivity."
},
{
"from": "gpt",
"value": "The Choreo PDP agent communicates outbound to the Choreo control plane (mizzen server) using WSS protocol, and outbound (cluster int... | docs\choreo-concepts\data-planes.md/Private data planes - Connectivity with the control plane | 5 |
[
{
"from": "human",
"value": "What are the outbound communication endpoints and protocols for the APIM/local adaptor in a private data plane?"
},
{
"from": "gpt",
"value": "The APIM/local adaptor communicates outbound to the Global adaptor using HTTPS and outbound to Azure Service Bus (CP) using ... | docs\choreo-concepts\data-planes.md/Private data planes - Connectivity with the control plane | 5 |
[
{
"from": "human",
"value": "How does the APIM/Enforcer component in a private data plane connect to the control plane?"
},
{
"from": "gpt",
"value": "The APIM/Enforcer component connects outbound to the Event hub (CP) using AMQP."
}
] | docs\choreo-concepts\data-planes.md/Private data planes - Connectivity with the control plane | 5 |
[
{
"from": "human",
"value": "What is the communication pathway for the Choreo secret resolver in a private data plane?"
},
{
"from": "gpt",
"value": "The Choreo secret resolver communicates outbound (VPC internal) to the Cloud secret store using HTTPS."
}
] | docs\choreo-concepts\data-planes.md/Private data planes - Connectivity with the control plane | 5 |
[
{
"from": "human",
"value": "Detail the inbound and outbound communication for the Container registry component within a private data plane."
},
{
"from": "gpt",
"value": "The Container registry component has inbound communication from the Container registry (public) via HTTPS, and outbound comm... | docs\choreo-concepts\data-planes.md/Private data planes - Connectivity with the control plane | 5 |
[
{
"from": "human",
"value": "Which external services does the Certificate manager in a private data plane communicate with, and using what protocol?"
},
{
"from": "gpt",
"value": "The Certificate manager communicates outbound to Azure DNS service and LetsEncrypt, both using HTTPS."
}
] | docs\choreo-concepts\data-planes.md/Private data planes - Connectivity with the control plane | 5 |
[
{
"from": "human",
"value": "What are the outbound communication pathways for the Flux source controller and Flux Helm controller in a private data plane?"
},
{
"from": "gpt",
"value": "The Flux source controller communicates outbound to GitHub using HTTPS, and the Flux Helm controller communica... | docs\choreo-concepts\data-planes.md/Private data planes - Connectivity with the control plane | 5 |
[
{
"from": "human",
"value": "How is all communication between the control plane and the private data plane secured?"
},
{
"from": "gpt",
"value": "All communication between the control plane and the private data plane is secured using TLS."
}
] | docs\choreo-concepts\data-planes.md/Private data planes - Connectivity with the control plane | 5 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.