rasa-pro 3.8.18__py3-none-any.whl → 3.9.15__py3-none-any.whl

README.md

@@ -10,11 +10,11 @@
 
 <hr />
 
-<img align="right" height="255" src="https://www.rasa.com/assets/img/sara/sara-open-source-2.0.png" alt="An image of Sara, the Rasa mascot bird, holding a flag that reads Open Source with one wing, and a wrench in the other" title="Rasa Open Source">
+<img align="right" height="255" src="https://www.rasa.com/assets/img/sara/sara-open-source-2.0.png" alt="An image of Sara, the Rasa mascot bird, holding a flag that reads Open Source with one wing, and a wrench in the other" title="Rasa Pro">
 
 Rasa Pro is an open core product that extends Rasa Open Source. With over 50 million downloads, Rasa Open Source is the most popular open source framework for building chat and voice-based AI assistants.
 
-Rasa Pro extends Rasa Open Source with CALM, a generative AI-native approach to developing assistants, combined with enterprise-ready analytics, security, and observability capabilities. A paid license is required to run Rasa Pro, but all Rasa Pro code is visible to end users and can be customized as needed.
+Rasa Pro introduces CALM, a generative AI-native approach to developing assistants, combined with enterprise-ready analytics, security, and observability capabilities. A paid license is required to run Rasa Pro, but all Rasa Pro code is visible to end users and can be customized as needed.
 
 Rasa Pro is the pro-code component of our enterprise solution, Rasa Platform, for implementing resilient and trustworthy AI assistants at scale. Rasa Studio complements Rasa Pro with a low-code user interface, enabling anyone on your team to create and improve your assistant.
 
@@ -212,8 +212,8 @@ The Docker image is available on your local machine as `rasa-private-dev`.
 
 ### Code Style
 
-To ensure a standardized code style we use the formatter [black](https://github.com/ambv/black).
-To ensure our type annotations are correct we use the type checker [pytype](https://github.com/google/pytype).
+To ensure a standardized code style we use the [ruff](https://docs.astral.sh/ruff/formatter/) formatter.
+To ensure our type annotations are correct we use the type checker [mypy](https://mypy.readthedocs.io/en/stable/).
 If your code is not formatted properly or doesn't type check, GitHub will fail to build.
 
 #### Formatting
@@ -222,7 +222,7 @@ If you want to automatically format your code on every commit, you can use [pre-
 Just install it via `pip install pre-commit` and execute `pre-commit install` in the root folder.
 This will add a hook to the repository, which reformats files on every commit.
 
-If you want to set it up manually, install black via `poetry install`.
+If you want to set it up manually, install `ruff` via `poetry install`.
 To reformat files execute
 ```
 make formatter
@@ -236,39 +236,6 @@ To check the types execute
 make types
 ```
 
-### Backporting
-
-In order to port changes to `main` and across release branches, we use the `backport` workflow located at
-the `.github/workflows/backport.yml` path.
-This workflow is triggered by the `backport-to-<release-branch>` label applied to a PR, for example `backport-to-3.8.x`.
-Current available target branches are `main` and maintained release branches.
-
-When a PR gets labelled `backport-to-<release-branch>`, a PR is opened by the `backport-github-action` as soon as the
-source PR gets closed (by merging). If you want to close the PR without merging changes, make sure to remove the `backport-to-<release-branch>` label.
-
-The PR author which the action assigns to the backporting PR has to resolve any conflicts before approving and merging.
-Release PRs should also be labelled with `backport-to-main` to backport the `CHANGELOG.md` updates to `main`.
-Backporting version updates should be accepted to the `main` branch from the latest release branch only.
-
-Here are some guidelines to follow when backporting changes and resolving conflicts:
-
-a) for conflicts in `version.py`: accept only the version from the latest release branch. Do not merge version changes
-from earlier release branches into `main` because this could cause issues when trying to make the next minor release.
-
-b) for conflicts in `pyproject.toml`: if related to the `rasa-pro` version, accept only the latest release branch; 
-if related to other dependencies, accept `main` or whichever is the higher upgrade (main usually has the updated 
-dependencies because we only do housekeeping on `main`, apart from vulnerability updates). Be mindful of dependencies that
-are removed from `main` but still exist in former release branches (for example `langchain`).
-
-c) for conflicts in `poetry.lock`: accept changes which were already present on the target branch, then run
-`poetry lock --no-update` so that the lock file contains your changes from `pyproject.toml` too.
-
-d) for conflicts in `CHANGELOG.md`: Manually place the changelog in their allocated section (e.g. 3.8.10 will go under the 
-3.8 section with the other releases, rather than go at the top of the file)
-
-If the backporting workflow fails, you are encouraged to cherry-pick the commits manually and create a PR to
-the target branch. Alternatively, you can install the backporting CLI tool as described [here](https://github.com/sorenlouv/backport?tab=readme-ov-file#install).
-
 ## Releases
 Rasa has implemented robust policies governing version naming, as well as release pace for major, minor, and patch releases.
 
@@ -351,12 +318,9 @@ Releasing a new version is quite simple, as the packages are build and distribut
 9. If however an error occurs in the build, then we should see a failure message automatically posted in the company's Slack (`dev-tribe` channel) like this [one](https://rasa-hq.slack.com/archives/C01M5TAHDHA/p1701444735622919)
    (In this case do the following checks):
     - Check the workflows in [Github Actions](https://github.com/RasaHQ/rasa-private/actions) and make sure that the merged PR of the current release is completed successfully. To easily find your PR you can use the filters `event: push` and `branch: <version number>` (example on release 2.4 you can see [here](https://github.com/RasaHQ/rasa/actions/runs/643344876))
-    - If the workflow is not completed, then try to re-run the workflow in case that solves the problem
+    - If the workflow is not completed, then try to re run the workflow in case that solves the problem
     - If the problem persists, check also the log files and try to find the root cause of the issue
     - If you still cannot resolve the error, contact the infrastructure team by providing any helpful information from your investigation
-10. If the release is successful, add the newly created release branch to the backporting configuration in the `.backportrc.json` file to
-the `targetBranchesChoices` list. This is necessary for the backporting workflow to work correctly with new release branches.
-
 
 ### Cutting a Patch release
 

rasa/__main__.py

@@ -30,6 +30,7 @@ from rasa.cli.arguments.default_arguments import add_logging_options
 from rasa.cli.utils import (
     parse_last_positional_argument_as_model_path,
     warn_if_rasa_plus_package_installed,
+    check_if_studio_command,
 )
 from rasa.plugin import plugin_manager
 from rasa.shared.exceptions import RasaException
@@ -115,18 +116,22 @@ def main() -> None:
         if hasattr(cmdline_arguments, "func"):
             rasa.utils.io.configure_colored_logging(log_level)
 
-            result = plugin_manager().hook.configure_commandline(
-                cmdline_arguments=cmdline_arguments
-            )
-            endpoints_file = result[0] if result else None
+            is_studio_command = check_if_studio_command()
+
+            if not is_studio_command:
+                result = plugin_manager().hook.configure_commandline(
+                    cmdline_arguments=cmdline_arguments
+                )
+                endpoints_file = result[0] if result else None
 
             rasa.telemetry.initialize_telemetry()
             rasa.telemetry.initialize_error_reporting()
-            plugin_manager().hook.init_telemetry(endpoints_file=endpoints_file)
-            plugin_manager().hook.init_managers(endpoints_file=endpoints_file)
-            plugin_manager().hook.init_anonymization_pipeline(
-                endpoints_file=endpoints_file
-            )
+            if not is_studio_command:
+                plugin_manager().hook.init_telemetry(endpoints_file=endpoints_file)
+                plugin_manager().hook.init_managers(endpoints_file=endpoints_file)
+                plugin_manager().hook.init_anonymization_pipeline(
+                    endpoints_file=endpoints_file
+                )
             # configure structlog
             configure_structlog(log_level)
 

rasa/anonymization/anonymization_pipeline.py

@@ -276,7 +276,6 @@ def _load_orchestrators(
                     continue
 
                 if rule_list.id == topic.get("anonymization_rules"):
-
                     event_broker = create_event_broker(topic_name, event_broker_config)
 
                     orchestrators.append(

rasa/anonymization/anonymization_rule_executor.py

@@ -87,19 +87,19 @@ class AnonymizationAnalyzer(metaclass=Singleton):
         if anonymization_rule_list.model_provider == "transformers":
             nlp_engine = TransformersNlpEngine(
                 models={
-                    anonymization_rule_list.language: anonymization_rule_list.models  # noqa: E501
+                    anonymization_rule_list.language: anonymization_rule_list.models
                 },
             )
         elif anonymization_rule_list.model_provider == "stanza":
             nlp_engine = StanzaNlpEngine(
                 models={
-                    anonymization_rule_list.language: anonymization_rule_list.models  # noqa: E501
+                    anonymization_rule_list.language: anonymization_rule_list.models
                 },
             )
         else:
             nlp_engine = SpacyNlpEngine(
                 models={
-                    anonymization_rule_list.language: anonymization_rule_list.models  # noqa: E501
+                    anonymization_rule_list.language: anonymization_rule_list.models
                 },
             )
 

rasa/anonymization/utils.py

@@ -30,8 +30,9 @@ def read_endpoint_config(
         return content
     except FileNotFoundError:
         logger.error(
-            "Failed to read configuration "
-            "from {}. No such file.".format(os.path.abspath(filename)),
+            "Failed to read configuration from {}. No such file.".format(
+                os.path.abspath(filename)
+            ),
         )
         return None
 
@@ -96,7 +97,7 @@ def validate_anonymization_yaml(yaml_content: Dict[Text, Any]) -> None:
 
     If the yaml_content is not in the right format, an exception will be raised.
     """
-    schema = read_yaml_file(SCHEMA_FILE, reader_type=["safe", "rt"])
+    schema = read_yaml_file(SCHEMA_FILE, reader_type=("safe", "rt"))
     try:
         validate_yaml_content_using_schema(yaml_content, schema)
     except YamlException as exception:

rasa/api.py

@@ -142,5 +142,5 @@ def test(
     if additional_arguments is None:
         additional_arguments = {}
 
-    test_core(model, stories, output, additional_arguments)  # type: ignore[unused-coroutine] # noqa: E501
-    test_nlu(model, nlu_data, output, additional_arguments)  # type: ignore[unused-coroutine] # noqa: E501
+    test_core(model, stories, output, additional_arguments)  # type: ignore[unused-coroutine]
+    test_nlu(model, nlu_data, output, additional_arguments)  # type: ignore[unused-coroutine]

rasa/cli/arguments/default_arguments.py

@@ -73,7 +73,7 @@ def add_config_param(
         "--config",
         type=str,
         default=default,
-        help="The policy and NLU pipeline configuration of your bot.",
+        help="The policy and pipeline configuration of your bot.",
     )
 
 

rasa/cli/arguments/run.py

@@ -28,7 +28,7 @@ def set_run_action_arguments(parser: argparse.ArgumentParser) -> None:
 
 
 def add_interface_argument(
-    parser: Union[argparse.ArgumentParser, argparse._ArgumentGroup]
+    parser: Union[argparse.ArgumentParser, argparse._ArgumentGroup],
 ) -> None:
     """Binds the RASA process to a network interface."""
     parser.add_argument(
@@ -42,7 +42,7 @@ def add_interface_argument(
 
 # noinspection PyProtectedMember
 def add_port_argument(
-    parser: Union[argparse.ArgumentParser, argparse._ArgumentGroup]
+    parser: Union[argparse.ArgumentParser, argparse._ArgumentGroup],
 ) -> None:
     """Add an argument for port."""
     parser.add_argument(

rasa/cli/arguments/test.py

@@ -96,7 +96,7 @@ def add_test_core_argument_group(
 
 
 def add_test_nlu_argument_group(
-    parser: Union[argparse.ArgumentParser, argparse._ActionsContainer]
+    parser: Union[argparse.ArgumentParser, argparse._ActionsContainer],
 ) -> None:
     add_nlu_data_param(parser, help_text="File or folder containing your NLU data.")
 

rasa/cli/arguments/train.py

@@ -75,7 +75,7 @@ def set_train_nlu_arguments(parser: argparse.ArgumentParser) -> None:
 
 
 def add_force_param(
-    parser: Union[argparse.ArgumentParser, argparse._ActionsContainer]
+    parser: Union[argparse.ArgumentParser, argparse._ActionsContainer],
 ) -> None:
     """Specifies if the model should be trained from scratch."""
     parser.add_argument(
@@ -86,7 +86,7 @@ def add_force_param(
 
 
 def add_data_param(
-    parser: Union[argparse.ArgumentParser, argparse._ActionsContainer]
+    parser: Union[argparse.ArgumentParser, argparse._ActionsContainer],
 ) -> None:
     """Specifies path to training data."""
     parser.add_argument(
@@ -110,7 +110,7 @@ def _add_core_config_param(parser: argparse.ArgumentParser) -> None:
 
 
 def _add_compare_params(
-    parser: Union[argparse.ArgumentParser, argparse._ActionsContainer]
+    parser: Union[argparse.ArgumentParser, argparse._ActionsContainer],
 ) -> None:
     parser.add_argument(
         "--percentages",
@@ -125,7 +125,7 @@ def _add_compare_params(
 
 
 def add_dry_run_param(
-    parser: Union[argparse.ArgumentParser, argparse._ActionsContainer]
+    parser: Union[argparse.ArgumentParser, argparse._ActionsContainer],
 ) -> None:
     """Adds `--dry-run` argument to a specified `parser`.
 
@@ -149,7 +149,7 @@ def add_dry_run_param(
 
 
 def add_validate_before_train(
-    parser: Union[argparse.ArgumentParser, argparse._ActionsContainer]
+    parser: Union[argparse.ArgumentParser, argparse._ActionsContainer],
 ) -> None:
     """Adds parameters for validating the domain and data files before training.
 
@@ -180,7 +180,7 @@ def add_validate_before_train(
 
 
 def add_augmentation_param(
-    parser: Union[argparse.ArgumentParser, argparse._ActionsContainer]
+    parser: Union[argparse.ArgumentParser, argparse._ActionsContainer],
 ) -> None:
     """Sets the augmentation factor for the Core training.
 
@@ -196,7 +196,7 @@ def add_augmentation_param(
 
 
 def add_debug_plots_param(
-    parser: Union[argparse.ArgumentParser, argparse._ActionsContainer]
+    parser: Union[argparse.ArgumentParser, argparse._ActionsContainer],
 ) -> None:
     """Specifies if conversation flow should be visualized."""
     parser.add_argument(
@@ -210,7 +210,7 @@ def add_debug_plots_param(
 
 
 def _add_num_threads_param(
-    parser: Union[argparse.ArgumentParser, argparse._ActionsContainer]
+    parser: Union[argparse.ArgumentParser, argparse._ActionsContainer],
 ) -> None:
     parser.add_argument(
         "--num-threads",
@@ -229,7 +229,7 @@ def _add_model_name_param(parser: argparse.ArgumentParser) -> None:
 
 
 def add_persist_nlu_data_param(
-    parser: Union[argparse.ArgumentParser, argparse._ActionsContainer]
+    parser: Union[argparse.ArgumentParser, argparse._ActionsContainer],
 ) -> None:
     """Adds parameters for persisting the NLU training data with the model."""
     parser.add_argument(
@@ -240,7 +240,7 @@ def add_persist_nlu_data_param(
 
 
 def add_finetune_params(
-    parser: Union[argparse.ArgumentParser, argparse._ActionsContainer]
+    parser: Union[argparse.ArgumentParser, argparse._ActionsContainer],
 ) -> None:
     """Adds parameters for model finetuning."""
     parser.add_argument(

rasa/cli/e2e_test.py

@@ -22,7 +22,14 @@ from rasa.exceptions import RasaException
 from rasa.shared.constants import DEFAULT_ENDPOINTS_PATH, DEFAULT_MODELS_PATH
 
 from rasa.e2e_test.constants import SCHEMA_FILE_PATH, KEY_TEST_CASE
-from rasa.e2e_test.e2e_test_case import KEY_FIXTURES, Fixture, TestCase
+from rasa.e2e_test.e2e_test_case import (
+    KEY_FIXTURES,
+    KEY_METADATA,
+    Fixture,
+    Metadata,
+    TestCase,
+    TestSuite,
+)
 from rasa.e2e_test.e2e_test_result import TestResult
 from rasa.e2e_test.e2e_test_runner import E2ETestRunner
 import rasa.utils.io
@@ -194,15 +201,14 @@ def validate_test_case(test_case_name: Text, input_test_cases: List[TestCase]) -
         sys.exit(1)
 
 
-def read_test_cases(path: Text) -> Tuple[List[TestCase], List[Fixture]]:
+def read_test_cases(path: Text) -> TestSuite:
     """Read test cases from the given path.
 
     Args:
         path: Path to the file or folder containing test cases.
 
     Returns:
-        Tuple consisting of the list of all test cases and the
-        list of all global fixtures found in the file or folder.
+        TestSuite.
     """
     path, test_case_name = extract_test_case_from_path(path)
     validate_path_to_test_cases(path)
@@ -212,6 +218,7 @@ def read_test_cases(path: Text) -> Tuple[List[TestCase], List[Fixture]]:
 
     input_test_cases = []
     fixtures: Dict[Text, Fixture] = {}
+    metadata: Dict[Text, Metadata] = {}
 
     for test_file in test_files:
         test_file_content = parse_raw_yaml(Path(test_file).read_text())
@@ -233,6 +240,7 @@ def read_test_cases(path: Text) -> Tuple[List[TestCase], List[Fixture]]:
 
         input_test_cases.extend(test_cases)
         fixtures_content = test_file_content.get(KEY_FIXTURES) or []
+        metadata_contents = test_file_content.get(KEY_METADATA) or []
         for fixture in fixtures_content:
             fixture_obj = Fixture.from_dict(fixture_dict=fixture)
 
@@ -240,8 +248,15 @@ def read_test_cases(path: Text) -> Tuple[List[TestCase], List[Fixture]]:
             if fixtures.get(fixture_obj.name) is None:
                 fixtures[fixture_obj.name] = fixture_obj
 
+        for metadata_content in metadata_contents:
+            metadata_obj = Metadata.from_dict(metadata_dict=metadata_content)
+
+            # avoid adding duplicates from across multiple files
+            if metadata.get(metadata_obj.name) is None:
+                metadata[metadata_obj.name] = metadata_obj
+
     validate_test_case(test_case_name, input_test_cases)
-    return input_test_cases, list(fixtures.values())
+    return TestSuite(input_test_cases, list(fixtures.values()), list(metadata.values()))
 
 
 def execute_e2e_tests(args: argparse.Namespace) -> None:
@@ -269,7 +284,7 @@ def execute_e2e_tests(args: argparse.Namespace) -> None:
         args, "path-to-test-cases", DEFAULT_E2E_INPUT_TESTS_PATH
     )
 
-    input_test_cases, input_fixtures = read_test_cases(path_to_test_cases)
+    test_suite = read_test_cases(path_to_test_cases)
 
     try:
         test_runner = E2ETestRunner(
@@ -283,7 +298,12 @@ def execute_e2e_tests(args: argparse.Namespace) -> None:
         sys.exit(1)
 
     results = asyncio.run(
-        test_runner.run_tests(input_test_cases, input_fixtures, args.fail_fast)
+        test_runner.run_tests(
+            test_suite.test_cases,
+            test_suite.fixtures,
+            args.fail_fast,
+            input_metadata=test_suite.metadata,
+        )
     )
 
     if args.e2e_results is not None:

rasa/cli/export.py

@@ -177,7 +177,6 @@ def export_trackers(args: argparse.Namespace) -> None:
 
 
 async def _export_trackers(args: argparse.Namespace) -> None:
-
     _assert_max_timestamp_is_greater_than_min_timestamp(args)
 
     endpoints = rasa.core.utils.read_endpoints_from_path(args.endpoints)

rasa/cli/license.py

@@ -28,9 +28,9 @@ def display_license_information(_: argparse.Namespace) -> None:
     """Display licensing information to stdout."""
     rasa.shared.utils.cli.print_info(
         "By installing and using this software, you agree to be "
-        "bound by the terms and conditions of the End-User License Agreement "
-        "(EULA) available at https://rasa.com/eula. "
-        "Please review the EULA carefully before proceeding.\n\n"
+        "bound by the terms and conditions of the Developer Terms "
+        "available at https://rasa.com/developer-terms. "
+        "Please review the Developer Terms carefully before proceeding.\n\n"
         "Rasa Pro relies on several 3rd-party dependencies. "
         "The ones below require a license disclorure:\n",
         PSYCOPG2_LICENSE_DISCLOSURE,

rasa/cli/project_templates/calm/actions/action_template.py

@@ -2,7 +2,7 @@
 # custom Python code.
 #
 # See this guide on how to implement these action:
-# https://rasa.com/docs/rasa/custom-actions
+# https://rasa.com/docs/rasa-pro/concepts/custom-actions
 
 
 # This is a simple example for a custom action which utters "Hello World!"

rasa/cli/project_templates/calm/config.yml

@@ -1,7 +1,7 @@
 recipe: default.v1
 language: en
 pipeline:
-- name: LLMCommandGenerator
+- name: SingleStepLLMCommandGenerator
   llm:
     model_name: gpt-4
     request_timeout: 7

rasa/cli/project_templates/calm/credentials.yml

@@ -1,6 +1,6 @@
 # This file contains the credentials for the voice & chat platforms
 # which your bot is using.
-# https://rasa.com/docs/rasa/messaging-and-voice-channels
+# https://rasa.com/docs/rasa-pro/connectors/messaging-and-voice-channels/
 
 rest:
 #  # you don't need to provide anything here - this channel doesn't

rasa/cli/project_templates/calm/data/flows/add_contact.yml

@@ -10,7 +10,7 @@ flows:
       - collect: "add_contact_confirmation"
         ask_before_filling: true
         next:
-          - if: not slots.add_contact_confirmation
+          - if: "slots.add_contact_confirmation is not true"
             then:
               - action: utter_add_contact_cancelled
                 next: END

rasa/cli/project_templates/calm/data/flows/remove_contact.yml

@@ -8,7 +8,7 @@ flows:
       - collect: "remove_contact_confirmation"
         ask_before_filling: true
         next:
-          - if: "not slots.remove_contact_confirmation"
+          - if: "slots.remove_contact_confirmation is not true"
             then:
               - action: utter_remove_contact_cancelled
                 next: END

rasa/cli/project_templates/calm/domain/add_contact.yml

@@ -6,18 +6,24 @@ actions:
 slots:
   add_contact_confirmation:
     type: bool
+    mappings:
+      - type: from_llm
   add_contact_name:
     type: text
+    mappings:
+      - type: from_llm
   add_contact_handle:
     type: text
+    mappings:
+      - type: from_llm
 
 responses:
   utter_ask_add_contact_confirmation:
     - text: Do you want to add {add_contact_name}({add_contact_handle}) to your contacts?
       buttons:
-        - payload: "yes"
+        - payload: "/SetSlots(add_contact_confirmation=true)"
           title: Yes
-        - payload: "no"
+        - payload: "/SetSlots(add_contact_confirmation=false)"
           title: No, cancel
   utter_ask_add_contact_handle:
     - text: What's the handle of the user you want to add?

rasa/cli/project_templates/calm/domain/list_contacts.yml

@@ -6,6 +6,9 @@ actions:
 slots:
   contacts_list:
     type: text
+    mappings:
+      - type: custom
+        action: list_contacts
 
 responses:
   utter_no_contacts:

rasa/cli/project_templates/calm/domain/remove_contact.yml

@@ -6,10 +6,17 @@ actions:
 slots:
   remove_contact_name:
     type: text
+    mappings:
+      - type: custom
+        action: remove_contact
   remove_contact_handle:
     type: text
+    mappings:
+      - type: from_llm
   remove_contact_confirmation:
     type: text
+    mappings:
+      - type: from_llm
 
 responses:
   utter_ask_remove_contact_handle:
@@ -22,9 +29,9 @@ responses:
      - text: "Removed {remove_contact_handle}({remove_contact_name}) from your contacts."
   utter_ask_remove_contact_confirmation:
     - buttons:
-        - payload: "yes"
+        - payload: "/SetSlots(remove_contact_confirmation=true)"
           title: Yes
-        - payload: "false"
+        - payload: "/SetSlots(remove_contact_confirmation=false)"
           title: No, cancel the removal
       text: "Should I remove {remove_contact_handle} from your contact list?"
   utter_remove_contact_cancelled:

rasa/cli/project_templates/calm/domain/shared.yml

@@ -3,3 +3,8 @@ version: "3.1"
 slots:
   return_value:
     type: any
+    mappings:
+      - type: custom
+        action: add_contact
+      - type: custom
+        action: remove_contact

rasa/cli/project_templates/calm/endpoints.yml

@@ -1,21 +1,21 @@
 # This file contains the different endpoints your bot can use.
 
 # Server where the models are pulled from.
-# https://rasa.com/docs/rasa/model-storage#fetching-models-from-a-server
+# https://rasa.com/docs/rasa-pro/production/model-storage#fetching-models-from-a-server
 
 #models:
 #  url: http://my-server.com/models/default_core@latest
 #  wait_time_between_pulls:  10   # [optional](default: 100)
 
 # Server which runs your custom actions.
-# https://rasa.com/docs/rasa/custom-actions
+# https://rasa.com/docs/rasa-pro/concepts/custom-actions
 
 action_endpoint:
   url: "http://localhost:5055/webhook"
 
 # Tracker store which is used to store the conversations.
 # By default the conversations are stored in memory.
-# https://rasa.com/docs/rasa/tracker-stores
+# https://rasa.com/docs/rasa-pro/production/tracker-stores
 
 #tracker_store:
 #    type: redis
@@ -33,7 +33,7 @@ action_endpoint:
 #    password: <password used for authentication>
 
 # Event broker which all conversation events should be streamed to.
-# https://rasa.com/docs/rasa/event-brokers
+# https://rasa.com/docs/rasa-pro/production/event-brokers
 
 #event_broker:
 #  url: localhost

rasa/cli/project_templates/default/actions/actions.py

@@ -2,7 +2,7 @@
 # custom Python code.
 #
 # See this guide on how to implement these action:
-# https://rasa.com/docs/rasa/custom-actions
+# https://rasa.com/docs/rasa-pro/concepts/custom-actions
 
 
 # This is a simple example for a custom action which utters "Hello World!"

rasa/cli/project_templates/default/config.yml

@@ -1,5 +1,5 @@
 # The config recipe.
-# https://rasa.com/docs/rasa/model-configuration/
+# https://rasa.com/docs/rasa-pro/nlu-based-assistants/model-configuration/
 recipe: default.v1
 
 # The assistant project unique identifier
@@ -7,13 +7,13 @@ recipe: default.v1
 assistant_id: placeholder_default
 
 # Configuration for Rasa NLU.
-# https://rasa.com/docs/rasa/nlu/components/
+# https://rasa.com/docs/rasa-pro/nlu-based-assistants/components/
 language: en
 
 pipeline:
 # # No configuration for the NLU pipeline was provided. The following default pipeline was used to train your model.
 # # If you'd like to customize it, uncomment and adjust the pipeline.
-# # See https://rasa.com/docs/rasa/tuning-your-model for more information.
+# # See https://rasa.com/docs/rasa-pro/nlu-based-assistants/tuning-your-model for more information.
 #   - name: WhitespaceTokenizer
 #   - name: RegexFeaturizer
 #   - name: LexicalSyntacticFeaturizer
@@ -32,11 +32,11 @@ pipeline:
 #     ambiguity_threshold: 0.1
 
 # Configuration for Rasa Core.
-# https://rasa.com/docs/rasa/core/policies/
+# https://rasa.com/docs/rasa-pro/concepts/policies/policy-overview/
 policies:
 # # No configuration for policies was provided. The following default policies were used to train your model.
 # # If you'd like to customize them, uncomment and adjust the policies.
-# # See https://rasa.com/docs/rasa/policies for more information.
+# # See https://rasa.com/docs/rasa-pro/concepts/policies/policy-overview/ for more information.
 #   - name: MemoizationPolicy
 #   - name: TEDPolicy
 #     max_history: 5

rasa/cli/project_templates/default/credentials.yml

@@ -1,6 +1,6 @@
 # This file contains the credentials for the voice & chat platforms
 # which your bot is using.
-# https://rasa.com/docs/rasa/messaging-and-voice-channels
+# https://rasa.com/docs/rasa-pro/connectors/messaging-and-voice-channels/
 
 rest:
 #  # you don't need to provide anything here - this channel doesn't