pltr-cli 0.5.0__tar.gz → 0.5.2__tar.gz

{pltr_cli-0.5.0 → pltr_cli-0.5.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: pltr-cli
-Version: 0.5.0
+Version: 0.5.2
 Summary: Command-line interface for Palantir Foundry APIs
 Project-URL: Homepage, https://github.com/anjor/pltr-cli
 Project-URL: Repository, https://github.com/anjor/pltr-cli
@@ -47,7 +47,11 @@ A comprehensive command-line interface for Palantir Foundry APIs, providing 80+
 
 - 🔐 **Secure Authentication**: Token and OAuth2 support with encrypted credential storage
 - 📊 **Dataset Operations**: Complete dataset management with branches, files, transactions, and views (RID-based API)
-- 📁 **Folder Management**: Create, explore, and manage Foundry filesystem structure
+- 📁 **Filesystem Management**: Complete filesystem operations including folders, projects, spaces, and resources
+- 🏗️ **Project Management**: Create, update, and manage Foundry projects within spaces
+- 🌐 **Space Management**: Administer spaces, manage members, and control access
+- 🔐 **Resource Permissions**: Grant, revoke, and manage role-based access to resources
+- 🔗 **Connectivity & Imports**: Manage external connections and import files/tables from various data sources
 - 🎯 **Comprehensive Ontology Access**: 13 commands for objects, actions, and queries
 - 🏗️ **Orchestration Management**: Create, manage, and monitor builds, jobs, and schedules
 - 🎬 **MediaSets Operations**: Upload, download, and manage media content with transaction support
@@ -121,6 +125,15 @@ pltr folder create "My Project"
 # List root folder contents
 pltr folder list ri.compass.main.folder.0
 
+# Manage spaces and projects
+pltr space list
+pltr project create "My Project" ri.compass.main.space.123
+pltr project list --space-rid ri.compass.main.space.123
+
+# Manage resource permissions
+pltr resource-role grant ri.compass.main.dataset.123 user123 User viewer
+pltr resource-role list ri.compass.main.dataset.123
+
 # Execute a simple SQL query
 pltr sql execute "SELECT 1 as test"
 
@@ -129,6 +142,11 @@ pltr dataset get ri.foundry.main.dataset.abc123
 pltr dataset branches list ri.foundry.main.dataset.abc123
 pltr dataset files list ri.foundry.main.dataset.abc123
 
+# Dataset transaction management
+pltr dataset transactions start ri.foundry.main.dataset.abc123
+pltr dataset transactions commit ri.foundry.main.dataset.abc123 <transaction-rid>
+pltr dataset files upload myfile.csv ri.foundry.main.dataset.abc123 --transaction-rid <rid>
+
 # Start interactive mode for exploration
 pltr shell
 ```
@@ -171,6 +189,13 @@ pltr sql execute "SELECT * FROM table"  # Run SQL queries
 pltr ontology list             # List ontologies
 pltr dataset get <rid>         # Get dataset info
 
+# Filesystem Management
+pltr folder create "My Project"         # Create folders
+pltr space create "Team Space" <org-rid> # Create spaces
+pltr project create "New Project" <space-rid> # Create projects
+pltr resource search "dataset name"     # Search resources
+pltr resource-role grant <resource-rid> <user-id> User viewer # Grant permissions
+
 # Orchestration
 pltr orchestration builds search       # Search builds
 pltr orchestration jobs get <job-rid>  # Get job details
@@ -181,6 +206,12 @@ pltr media-sets get <set-rid> <item-rid>  # Get media item info
 pltr media-sets upload <set-rid> file.jpg "/path/file.jpg" <txn-id>  # Upload media
 pltr media-sets download <set-rid> <item-rid> output.jpg  # Download media
 
+# Connectivity & Data Imports
+pltr connectivity connection list              # List available connections
+pltr connectivity connection get <conn-rid>    # Get connection details
+pltr connectivity import file <conn-rid> <source-path> <dataset-rid> --execute  # Import file
+pltr connectivity import table <conn-rid> <table-name> <dataset-rid> --execute  # Import table
+
 # Administrative
 pltr admin user current        # Current user info
 pltr admin user list          # List users
@@ -301,6 +332,74 @@ pltr media-sets download ri.mediasets.main.media-set.abc \
 - Preview mode (`--preview`)
 - Transaction-based upload workflow
 
+### 📊 Dataset Transaction Management
+
+pltr-cli provides comprehensive transaction management for datasets, allowing atomic operations with rollback capability:
+
+#### Transaction Lifecycle
+```bash
+# Start a new transaction
+pltr dataset transactions start ri.foundry.main.dataset.abc123 --branch master --type APPEND
+# Returns transaction RID for use in subsequent operations
+
+# Check transaction status
+pltr dataset transactions status ri.foundry.main.dataset.abc123 ri.foundry.main.transaction.xyz
+
+# List all transactions for a dataset
+pltr dataset transactions list ri.foundry.main.dataset.abc123 --branch master
+
+# Commit a transaction (make changes permanent)
+pltr dataset transactions commit ri.foundry.main.dataset.abc123 ri.foundry.main.transaction.xyz
+
+# Abort a transaction (discard all changes)
+pltr dataset transactions abort ri.foundry.main.dataset.abc123 ri.foundry.main.transaction.xyz --yes
+```
+
+#### File Operations with Transactions
+```bash
+# Upload files within a transaction
+pltr dataset files upload data.csv ri.foundry.main.dataset.abc123 \
+  --transaction-rid ri.foundry.main.transaction.xyz
+
+# Multiple file uploads in same transaction
+pltr dataset files upload file1.csv ri.foundry.main.dataset.abc123 \
+  --transaction-rid ri.foundry.main.transaction.xyz
+pltr dataset files upload file2.csv ri.foundry.main.dataset.abc123 \
+  --transaction-rid ri.foundry.main.transaction.xyz
+
+# Commit when ready
+pltr dataset transactions commit ri.foundry.main.dataset.abc123 ri.foundry.main.transaction.xyz
+```
+
+#### Transaction Types
+- **APPEND**: Add new files to dataset
+- **UPDATE**: Add new files and overwrite existing ones
+- **SNAPSHOT**: Replace entire dataset with new files
+- **DELETE**: Remove files from dataset
+
+#### Example Workflow
+```bash
+# Start a transaction for bulk data update
+TRANSACTION=$(pltr dataset transactions start ri.foundry.main.dataset.abc123 \
+  --type UPDATE --format json | jq -r '.transaction_rid')
+
+# Upload multiple files
+pltr dataset files upload data1.csv ri.foundry.main.dataset.abc123 --transaction-rid $TRANSACTION
+pltr dataset files upload data2.csv ri.foundry.main.dataset.abc123 --transaction-rid $TRANSACTION
+
+# Check status before committing
+pltr dataset transactions status ri.foundry.main.dataset.abc123 $TRANSACTION
+
+# Commit if everything looks good
+pltr dataset transactions commit ri.foundry.main.dataset.abc123 $TRANSACTION
+```
+
+**Benefits:**
+- **Data Integrity**: Atomic operations with rollback capability
+- **Error Recovery**: Clean rollback from failed operations
+- **Collaboration**: Better concurrent modification handling
+- **Automation**: Reliable data pipeline operations
+
 ## ⚙️ Configuration
 
 pltr-cli stores configuration securely using industry best practices:

{pltr_cli-0.5.0 → pltr_cli-0.5.2}/README.md

@@ -10,7 +10,11 @@ A comprehensive command-line interface for Palantir Foundry APIs, providing 80+
 
 - 🔐 **Secure Authentication**: Token and OAuth2 support with encrypted credential storage
 - 📊 **Dataset Operations**: Complete dataset management with branches, files, transactions, and views (RID-based API)
-- 📁 **Folder Management**: Create, explore, and manage Foundry filesystem structure
+- 📁 **Filesystem Management**: Complete filesystem operations including folders, projects, spaces, and resources
+- 🏗️ **Project Management**: Create, update, and manage Foundry projects within spaces
+- 🌐 **Space Management**: Administer spaces, manage members, and control access
+- 🔐 **Resource Permissions**: Grant, revoke, and manage role-based access to resources
+- 🔗 **Connectivity & Imports**: Manage external connections and import files/tables from various data sources
 - 🎯 **Comprehensive Ontology Access**: 13 commands for objects, actions, and queries
 - 🏗️ **Orchestration Management**: Create, manage, and monitor builds, jobs, and schedules
 - 🎬 **MediaSets Operations**: Upload, download, and manage media content with transaction support
@@ -84,6 +88,15 @@ pltr folder create "My Project"
 # List root folder contents
 pltr folder list ri.compass.main.folder.0
 
+# Manage spaces and projects
+pltr space list
+pltr project create "My Project" ri.compass.main.space.123
+pltr project list --space-rid ri.compass.main.space.123
+
+# Manage resource permissions
+pltr resource-role grant ri.compass.main.dataset.123 user123 User viewer
+pltr resource-role list ri.compass.main.dataset.123
+
 # Execute a simple SQL query
 pltr sql execute "SELECT 1 as test"
 
@@ -92,6 +105,11 @@ pltr dataset get ri.foundry.main.dataset.abc123
 pltr dataset branches list ri.foundry.main.dataset.abc123
 pltr dataset files list ri.foundry.main.dataset.abc123
 
+# Dataset transaction management
+pltr dataset transactions start ri.foundry.main.dataset.abc123
+pltr dataset transactions commit ri.foundry.main.dataset.abc123 <transaction-rid>
+pltr dataset files upload myfile.csv ri.foundry.main.dataset.abc123 --transaction-rid <rid>
+
 # Start interactive mode for exploration
 pltr shell
 ```
@@ -134,6 +152,13 @@ pltr sql execute "SELECT * FROM table"  # Run SQL queries
 pltr ontology list             # List ontologies
 pltr dataset get <rid>         # Get dataset info
 
+# Filesystem Management
+pltr folder create "My Project"         # Create folders
+pltr space create "Team Space" <org-rid> # Create spaces
+pltr project create "New Project" <space-rid> # Create projects
+pltr resource search "dataset name"     # Search resources
+pltr resource-role grant <resource-rid> <user-id> User viewer # Grant permissions
+
 # Orchestration
 pltr orchestration builds search       # Search builds
 pltr orchestration jobs get <job-rid>  # Get job details
@@ -144,6 +169,12 @@ pltr media-sets get <set-rid> <item-rid>  # Get media item info
 pltr media-sets upload <set-rid> file.jpg "/path/file.jpg" <txn-id>  # Upload media
 pltr media-sets download <set-rid> <item-rid> output.jpg  # Download media
 
+# Connectivity & Data Imports
+pltr connectivity connection list              # List available connections
+pltr connectivity connection get <conn-rid>    # Get connection details
+pltr connectivity import file <conn-rid> <source-path> <dataset-rid> --execute  # Import file
+pltr connectivity import table <conn-rid> <table-name> <dataset-rid> --execute  # Import table
+
 # Administrative
 pltr admin user current        # Current user info
 pltr admin user list          # List users
@@ -264,6 +295,74 @@ pltr media-sets download ri.mediasets.main.media-set.abc \
 - Preview mode (`--preview`)
 - Transaction-based upload workflow
 
+### 📊 Dataset Transaction Management
+
+pltr-cli provides comprehensive transaction management for datasets, allowing atomic operations with rollback capability:
+
+#### Transaction Lifecycle
+```bash
+# Start a new transaction
+pltr dataset transactions start ri.foundry.main.dataset.abc123 --branch master --type APPEND
+# Returns transaction RID for use in subsequent operations
+
+# Check transaction status
+pltr dataset transactions status ri.foundry.main.dataset.abc123 ri.foundry.main.transaction.xyz
+
+# List all transactions for a dataset
+pltr dataset transactions list ri.foundry.main.dataset.abc123 --branch master
+
+# Commit a transaction (make changes permanent)
+pltr dataset transactions commit ri.foundry.main.dataset.abc123 ri.foundry.main.transaction.xyz
+
+# Abort a transaction (discard all changes)
+pltr dataset transactions abort ri.foundry.main.dataset.abc123 ri.foundry.main.transaction.xyz --yes
+```
+
+#### File Operations with Transactions
+```bash
+# Upload files within a transaction
+pltr dataset files upload data.csv ri.foundry.main.dataset.abc123 \
+  --transaction-rid ri.foundry.main.transaction.xyz
+
+# Multiple file uploads in same transaction
+pltr dataset files upload file1.csv ri.foundry.main.dataset.abc123 \
+  --transaction-rid ri.foundry.main.transaction.xyz
+pltr dataset files upload file2.csv ri.foundry.main.dataset.abc123 \
+  --transaction-rid ri.foundry.main.transaction.xyz
+
+# Commit when ready
+pltr dataset transactions commit ri.foundry.main.dataset.abc123 ri.foundry.main.transaction.xyz
+```
+
+#### Transaction Types
+- **APPEND**: Add new files to dataset
+- **UPDATE**: Add new files and overwrite existing ones
+- **SNAPSHOT**: Replace entire dataset with new files
+- **DELETE**: Remove files from dataset
+
+#### Example Workflow
+```bash
+# Start a transaction for bulk data update
+TRANSACTION=$(pltr dataset transactions start ri.foundry.main.dataset.abc123 \
+  --type UPDATE --format json | jq -r '.transaction_rid')
+
+# Upload multiple files
+pltr dataset files upload data1.csv ri.foundry.main.dataset.abc123 --transaction-rid $TRANSACTION
+pltr dataset files upload data2.csv ri.foundry.main.dataset.abc123 --transaction-rid $TRANSACTION
+
+# Check status before committing
+pltr dataset transactions status ri.foundry.main.dataset.abc123 $TRANSACTION
+
+# Commit if everything looks good
+pltr dataset transactions commit ri.foundry.main.dataset.abc123 $TRANSACTION
+```
+
+**Benefits:**
+- **Data Integrity**: Atomic operations with rollback capability
+- **Error Recovery**: Clean rollback from failed operations
+- **Collaboration**: Better concurrent modification handling
+- **Automation**: Reliable data pipeline operations
+
 ## ⚙️ Configuration
 
 pltr-cli stores configuration securely using industry best practices:

pltr_cli-0.5.2/RELEASE.md

@@ -0,0 +1,163 @@
+# Release Process
+
+This document describes how to create releases for pltr-cli using the automated release script.
+
+## Overview
+
+The release script (`scripts/release.py`) supports both interactive and non-interactive modes to accommodate different use cases:
+- **Interactive mode**: For human developers who want to review and confirm each step
+- **Non-interactive mode**: For AI agents and automated systems that need to create releases programmatically
+
+## Quick Start
+
+### For Humans (Interactive Mode)
+
+```bash
+# Patch release (0.5.1 → 0.5.2)
+python scripts/release.py --type patch
+
+# Minor release (0.5.1 → 0.6.0)
+python scripts/release.py --type minor
+
+# Major release (0.5.1 → 1.0.0)
+python scripts/release.py --type major
+
+# Specific version
+python scripts/release.py --version 0.6.0
+```
+
+### For AI Agents/Automation (Non-Interactive Mode)
+
+```bash
+# Create release without prompts, don't push
+python scripts/release.py --version 0.5.2 --yes --no-push
+
+# Create release and push automatically
+python scripts/release.py --type patch --yes --push
+
+# Test what would happen (dry run)
+python scripts/release.py --version 0.5.2 --dry-run
+```
+
+## Command-Line Arguments
+
+| Argument | Description |
+|----------|-------------|
+| `--version X.Y.Z` | Specify exact version to release |
+| `--type {major\|minor\|patch}` | Bump version automatically |
+| `--yes`, `-y` | Skip all confirmation prompts (non-interactive mode) |
+| `--push` | Push to origin without asking (requires `--yes`) |
+| `--no-push` | Don't push to origin (useful for testing) |
+| `--dry-run` | Show what would be done without making changes |
+
+## What the Script Does
+
+1. **Validates environment**:
+   - Checks that you're in a git repository
+   - Ensures working directory is clean (no uncommitted changes)
+   - Validates version format
+
+2. **Version handling**:
+   - Gets current version from `pyproject.toml`
+   - Calculates or validates new version
+   - Warns if version already exists or is the same as current
+
+3. **Creates release**:
+   - Updates version in `pyproject.toml`
+   - Creates git commit with message like "patch: Release version 0.5.2"
+   - Creates git tag like "v0.5.2"
+
+4. **Optional push**:
+   - Pushes commit and tag to origin (triggers GitHub Actions)
+   - Can be automatic (`--push`), skipped (`--no-push`), or prompted (default)
+
+## Usage Examples
+
+### Interactive Development Workflow
+```bash
+# Make your changes
+git add .
+git commit -m "feat: add new feature"
+
+# Create a patch release interactively
+python scripts/release.py --type patch
+# → Script will prompt for confirmation
+# → Script will ask if you want to push
+
+# The script will:
+# 1. Update pyproject.toml (0.5.1 → 0.5.2)
+# 2. Create commit "patch: Release version 0.5.2"
+# 3. Create tag "v0.5.2"
+# 4. Ask if you want to push to trigger publishing
+```
+
+### AI Agent Workflow
+```bash
+# AI agent creates a release without any prompts
+python scripts/release.py --version 0.5.2 --yes --no-push
+
+# The script will:
+# 1. Update pyproject.toml to version 0.5.2
+# 2. Create commit "release: Release version 0.5.2"
+# 3. Create tag "v0.5.2"
+# 4. NOT push (--no-push specified)
+# 5. Print instructions for manual push if needed
+```
+
+### Testing/Validation Workflow
+```bash
+# See what would happen without making changes
+python scripts/release.py --version 0.6.0 --dry-run
+
+# Create release locally but don't push (for testing)
+python scripts/release.py --version 0.6.0 --yes --no-push
+```
+
+## GitHub Actions Integration
+
+When commits and tags are pushed to the repository, GitHub Actions will automatically:
+1. Build the package
+2. Run tests
+3. Publish to PyPI (for tagged releases)
+4. Create GitHub release with release notes
+
+Monitor the workflow at: https://github.com/anjor/pltr-cli/actions
+
+## Error Handling
+
+The script handles several common error scenarios:
+
+- **Dirty working directory**: Script will fail if there are uncommitted changes
+- **Duplicate versions**: Warns if trying to release the same version as current
+- **Existing tags**: Warns if git tag already exists locally or remotely
+- **Invalid versions**: Validates semantic version format (X.Y.Z)
+- **Missing arguments**: Requires either `--version` or `--type`
+- **Invalid combinations**: Prevents conflicting flags like `--push` and `--no-push`
+
+## Troubleshooting
+
+### "EOFError: EOF when reading a line"
+This happens when running the script in non-interactive mode without the `--yes` flag. Add `--yes` to skip prompts.
+
+### "Tag already exists"
+The script will warn you and ask for confirmation. You can:
+- Delete the existing tag: `git tag -d v0.5.2`
+- Use a different version number
+- Continue anyway (not recommended)
+
+### "Working directory is not clean"
+Commit or stash your changes before running the release script:
+```bash
+git add .
+git commit -m "your changes"
+# OR
+git stash
+```
+
+## Best Practices
+
+1. **Always test with `--dry-run` first** when trying new version numbers
+2. **Use `--no-push` for testing** to avoid accidental pushes
+3. **Follow semantic versioning**: patch for bug fixes, minor for features, major for breaking changes
+4. **Keep working directory clean** before creating releases
+5. **Monitor GitHub Actions** after pushing to ensure successful publishing