tinybird 0.0.1.dev225__tar.gz → 0.0.1.dev226__tar.gz

{tinybird-0.0.1.dev225 → tinybird-0.0.1.dev226}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.2
 Name: tinybird
-Version: 0.0.1.dev225
+Version: 0.0.1.dev226
 Summary: Tinybird Command Line Tool
 Home-page: https://www.tinybird.co/docs/forward/commands
 Author: Tinybird

{tinybird-0.0.1.dev225 → tinybird-0.0.1.dev226}/tinybird/prompts.py

@@ -974,6 +974,93 @@ Follow these instructions when evolving a datasource schema:
     )
 
 
+def claude_rules_prompt(source: Optional[str] = None) -> str:
+    base_command = source or "tb"
+    return """
+# Tinybird CLI rules
+
+## Commands
+You have commands at your disposal to develop a tinybird project:
+- {base_command} build: to build the project locally and check it works.
+- {base_command} deployment create --wait --auto: to create a deployment and promote it automatically
+- {base_command} test run: to run existing tests
+- {base_command} endpoint url <pipe_name>: to get the url of an endpoint, token included.
+- {base_command} endpoint data <pipe_name>: to get the data of an endpoint. You can pass parameters to the endpoint like this: {base_command} endpoint data <pipe_name> --param1 value1 --param2 value2
+- {base_command}  token ls: to list all the tokens
+There are other commands that you can use, but these are the most common ones. Run `{base_command} -h` to see all the commands if needed.
+When you need to work with resources or data in cloud, add always the --cloud flag before the command. Example: {base_command} --cloud datasource ls
+
+## Development instructions
+- When asking to create a tinybird data project, if the needed folders are not already created, use the following structure:
+├── connections
+├── copies
+├── sinks
+├── datasources
+├── endpoints
+├── fixtures
+├── materializations
+├── pipes
+└── tests
+- The local development server will be available at http://localhost:7181. Even if some response uses another base url, use always http://localhost:7181.
+- After every change in your .datasource, .pipe or .ndjson files, run `{base_command} build` to build the project locally.
+- When you need to ingest data locally in a datasource, create a .ndjson file with the same name of the datasource and the data you want and run `{base_command} build` so the data is ingested.
+- The format of the generated api endpoint urls is: http://localhost:7181/v0/pipe/<pipe_name>.json?token=<token>
+- Before running the tests, remember to have the project built with `{base_command} build` with the latest changes.
+</development_instructions>
+When asking for ingesting data, adding data or appending data do the following depending on the environment you want to work with:
+
+## Ingestion instructions
+- When building locally, create a .ndjson file with the data you want to ingest and do `{base_command} build` to ingest the data in the build env.
+- We call `cloud` the production environment.
+- When appending data in cloud, use `{base_command} --cloud datasource append <datasource_name> <file_name>`
+- When you have a response that says “there are rows in quarantine”, do `{base_command} [--cloud] datasource data <datasource_name>_quarantine` to understand what is the problem.
+
+## .datasource file instructions
+Follow these instructions when creating or updating .datasource files:
+{datasource_instructions}
+
+## .pipe file instructions
+Follow these instructions when creating or updating .pipe files:
+{pipe_instructions}
+{sql_instructions}
+{datasource_example}
+{pipe_example}
+{copy_pipe_instructions}
+{materialized_pipe_instructions}
+{sink_pipe_instructions}
+{connection_instructions}
+{kafka_connection_example}
+{gcs_connection_example}
+{gcs_hmac_connection_example}
+{s3_connection_example}
+
+## .test file instructions
+Follow these instructions when creating or updating .yaml files for tests:
+{test_instructions}
+
+## Deployment instructions
+Follow these instructions when evolving a datasource schema:
+{deployment_instructions}
+""".format(
+        base_command=base_command,
+        datasource_instructions=datasource_instructions,
+        pipe_instructions=pipe_instructions,
+        sql_instructions=sql_instructions,
+        datasource_example=datasource_example,
+        pipe_example=pipe_example,
+        copy_pipe_instructions=copy_pipe_instructions,
+        materialized_pipe_instructions=materialized_pipe_instructions,
+        sink_pipe_instructions=sink_pipe_instructions,
+        test_instructions=test_instructions,
+        deployment_instructions=deployment_instructions,
+        connection_instructions=connection_instructions,
+        kafka_connection_example=kafka_connection_example,
+        gcs_connection_example=gcs_connection_example,
+        gcs_hmac_connection_example=gcs_hmac_connection_example,
+        s3_connection_example=s3_connection_example,
+    )
+
+
 test_instructions = """
 - The test file name must match the name of the pipe it is testing.
 - Every scenario name must be unique inside the test file.

{tinybird-0.0.1.dev225 → tinybird-0.0.1.dev226}/tinybird/tb/__cli__.py

@@ -4,5 +4,5 @@ __description__ = 'Tinybird Command Line Tool'
 __url__ = 'https://www.tinybird.co/docs/forward/commands'
 __author__ = 'Tinybird'
 __author_email__ = 'support@tinybird.co'
-__version__ = '0.0.1.dev225'
-__revision__ = 'ddc2523'
+__version__ = '0.0.1.dev226'
+__revision__ = '7ee5a2e'

{tinybird-0.0.1.dev225 → tinybird-0.0.1.dev226}/tinybird/tb/modules/create.py

@@ -1,6 +1,7 @@
 import glob
 import os
 import re
+import shutil
 from pathlib import Path
 from typing import Any, Dict, List, Optional
 from urllib.parse import urlparse
@@ -8,7 +9,7 @@ from urllib.parse import urlparse
 import click
 import requests
 
-from tinybird.prompts import create_prompt, readme_prompt, rules_prompt
+from tinybird.prompts import claude_rules_prompt, create_prompt, readme_prompt, rules_prompt
 from tinybird.tb.client import TinyB
 from tinybird.tb.modules.cicd import init_cicd
 from tinybird.tb.modules.cli import cli
@@ -144,6 +145,13 @@ async def create(
             click.echo(FeedbackManager.success(message="✓ Done!\n"))
             created_something = True
 
+        if not already_has_claude_rules(root_folder):
+            click.echo(FeedbackManager.highlight(message="\n» Creating Claude Code rules..."))
+            create_claude_rules(root_folder, "tb")
+            click.echo(FeedbackManager.info(message="CLAUDE.md"))
+            click.echo(FeedbackManager.success(message="✓ Done!\n"))
+            created_something = True
+
         if should_generate_fixtures(result):
             click.echo(FeedbackManager.highlight(message="\n» Generating fixtures..."))
 
@@ -246,6 +254,11 @@ def already_has_cursor_rules(folder: str) -> bool:
     return any((Path(folder) / path).exists() for path in cursor_rules_paths)
 
 
+def already_has_claude_rules(folder: str) -> bool:
+    claude_rules_path = "CLAUDE.md"
+    return (Path(folder) / claude_rules_path).exists()
+
+
 def already_has_env_file(folder: str) -> bool:
     env_file_pattern = ".env.*"
     return any((Path(folder) / path).exists() for path in glob.glob(env_file_pattern))
@@ -466,9 +479,22 @@ def create_rules(folder: str, source: str, agent: str):
     elif agent == "windsurf":
         extension = ".windsurfrules"
     else:
-        extension = ".txt"
+        extension = ".md"
+
     rules_file = Path(folder) / extension
-    rules_file.write_text(rules_prompt(source))
+    rules_content = rules_prompt(source)
+    rules_file.write_text(rules_content)
+
+
+def create_claude_rules(folder: str, source: str):
+    try:
+        is_claude_code_installed = shutil.which("claude") is not None
+        if is_claude_code_installed:
+            rules_content = claude_rules_prompt(source)
+            claude_file = Path(folder) / "CLAUDE.md"
+            claude_file.write_text(rules_content)
+    except Exception:
+        pass
 
 
 def get_context_file() -> Path:

{tinybird-0.0.1.dev225 → tinybird-0.0.1.dev226}/tinybird/tb/modules/feedback_manager.py

@@ -636,6 +636,7 @@ STEP 2: CREATE GCP SERVICE ACCOUNT
 - For GCS Sink (writing to GCS), select all three roles:
   • "Storage Object Creator" - Allows users to create objects
   • "Storage Object Viewer" - Grants access to view objects and their metadata
+  • "Storage Bucket Viewer" - Grants access to view buckets and their metadata
 (You can add IAM condition to provide access to selected buckets. More info in IAM Conditions: https://cloud.google.com/iam/docs/conditions-overview)
 5. Click "Done"
 """

{tinybird-0.0.1.dev225 → tinybird-0.0.1.dev226}/tinybird.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.2
 Name: tinybird
-Version: 0.0.1.dev225
+Version: 0.0.1.dev226
 Summary: Tinybird Command Line Tool
 Home-page: https://www.tinybird.co/docs/forward/commands
 Author: Tinybird