* added empty state text
* update permission group in the dataset
* Enhance dataset asset listing with organization-specific filtering
- Updated the `list_assets` function to include organization ID filtering in dataset permissions queries.
- Removed redundant organization ID filters from the dataset permissions queries to streamline the logic.
- Ensured that only relevant dataset assets are returned based on the user's organization, improving data security and relevance.
These changes enhance the API's ability to serve organization-specific data, aligning with recent improvements in dataset asset APIs.
* containerized class should be white with no border at bottom
* clear query when signing out
* Use correct endpoint for dataset groups
* yaml syntax highligting
* create dataset endpoints
* update disable logic for deploying a dataset
* Refactor user routes to include new endpoint for retrieving user by ID
- Removed the public modifier from `get_user` and `update_user` modules to encapsulate them within the module.
- Added a new route to the user router for fetching a user by their ID, enhancing the API's functionality.
- This change improves the user management capabilities by allowing retrieval of specific user details based on their unique identifier.
* Add organizations module and integrate with user routes
* remove unused imports and abstract variables
* Refactor user update functionality to support role changes
- Enhanced the `update_user` endpoint to accept and process user role updates alongside name changes.
- Introduced a new `UserResponse` struct for improved response handling.
- Updated the `update_user_handler` to handle changes in both user name and organization role, improving the flexibility of user management.
- Adjusted response type to return no content upon successful updates, aligning with RESTful practices.
These changes enhance the user management capabilities by allowing for more comprehensive updates to user information.
* Update user route to use ID parameter for updates
- Changed the user update route to require a user ID in the URL, enhancing RESTful practices.
- Updated the `update_user` function to extract the user ID from the path, ensuring the correct user is updated based on the provided ID.
These changes improve the clarity and functionality of the user update endpoint, aligning it with standard REST conventions.
* simplify hooks imports
* Remove unused component
* restructure folders for layout
* update imports for gloabl components
* add additional routes
* Implement user permission checks in dataset deployment and user update routes
- Added permission validation to the `deploy_datasets` and `post_dataset` functions to ensure only users with workspace admin or data admin roles can execute these actions.
- Enhanced error handling for permission checks, returning appropriate HTTP status codes and messages for insufficient permissions and internal errors.
- Updated imports to include the new security checks module for consistency across routes.
These changes improve security by enforcing role-based access control in critical dataset operations.
* Refactor user update route to enhance RESTful practices
- Updated the user update route to require a user ID in the URL, ensuring the correct user is updated based on the provided ID.
- Improved clarity and functionality of the `update_user` function by extracting the user ID from the path.
These changes align the user update endpoint with standard REST conventions, enhancing overall API usability.
* Enhance dataset listing functionality with user organization roles
- Refactored dataset listing logic to incorporate user organization roles, allowing for more granular access control based on user permissions.
- Introduced new role checks for `WorkspaceAdmin`, `DataAdmin`, `Querier`, `RestrictedQuerier`, and `Viewer` to determine dataset visibility.
- Updated database queries to fetch datasets based on user roles and organization associations, improving data retrieval efficiency.
- Removed deprecated functions and streamlined the dataset fetching process, ensuring clarity and maintainability in the codebase.
These changes improve the API's security and usability by enforcing role-based access control for dataset operations.
* tweaked the post thread permissions handle.
* permission_group string fix
* remove package.json
* fix: Add release please syntax handler and github action (#40)
* fix(buster): Add release please syntax handler and github action
* chore: add version tracking setup
fix: update
update nate rulez
---------
Co-authored-by: dal <dallin@buster.so>
- Added new Dependabot configurations for npm packages in the /api and /web directories, scheduled for weekly updates with a limit of 10 open pull requests.
- Updated the GitHub Actions workflows for both main and staging deployments to trigger on changes within the api directory, specifically for migrations, improving deployment reliability.
These changes streamline dependency management and enhance the deployment process for the application.
- Added a new job for database deployment, including steps for installing Rust, configuring AWS credentials, downloading the Postgres certificate from S3, and running migrations.
- Updated the existing porter-deploy job to include AWS credentials configuration and SSL certificate download from S3.
- Improved organization and reliability of the deployment process by ensuring all steps are correctly defined and executed in the appropriate context.
These changes streamline the deployment workflow and enhance the overall reliability of the application deployment process.
- Added a working-directory specification for the 'Run migrations' step in the GitHub Actions workflow, ensuring that Diesel migrations are executed in the correct context within the './api' directory. This change enhances the reliability of the migration process during deployment.
- Changed the S3 URL variable for downloading the Postgres SSL certificate in the GitHub Actions workflow from `PG_CERT_S3_URL` to `CERT_S3_URL`.
- This update ensures the workflow correctly references the updated secret for SSL certificate retrieval, improving the reliability of the deployment process.
- Added steps to configure AWS credentials and download the Postgres SSL certificate from S3 in the GitHub Actions workflow.
- Updated the Dockerfile to reflect the new path for the SSL certificate, ensuring it is correctly copied to the container.
These changes improve the security and organization of SSL certificate handling during the deployment process.
- Changed the directory structure for SSL certificates in the GitHub Actions workflow, creating a new path `certs/cert` for better organization.
- Updated the Dockerfile to reference the new certificate path, ensuring the SSL certificate is correctly installed in the container.
These changes improve the clarity and maintainability of the deployment process.
- Updated the runner specification for the database-deploy job to correct the Ubuntu version format.
- Ensured consistency in the runner configuration for the porter-deploy job by reverting to the previous Ubuntu version.
These changes enhance the accuracy of the workflow configuration, ensuring proper execution of deployment jobs.
- Added steps to create a directory for SSL certificates and copy the downloaded certificate to the new location in the GitHub Actions workflow.
- Updated the Dockerfile to reference the new certificate path, ensuring proper installation of the SSL certificate in the container.
These changes improve the organization of SSL certificates and enhance the deployment process.
- Added support for pull requests targeting the staging branch to the existing workflow.
- This change improves the deployment process by ensuring that pull requests are also considered for staging deployments.
- Introduced a new job for database deployment, including steps to install Rust, cache dependencies, and run Diesel migrations.
- Updated the existing porter-deploy job to include AWS credentials configuration and SSL certificate retrieval from S3.
- Enhanced the overall structure and organization of the workflow for improved clarity and maintainability.
- Changed the directory for the buster-cli package from "/packages/buster-cli" to "/cli".
- Added a new configuration for the cargo package in the "/api" directory.
- Updated scheduling and branch settings for both packages to improve dependency management.
These changes streamline the dependency update process and enhance the organization of package configurations.
- Added a TODO in the init function for ID retrieval and storage in artifacts.
- Introduced an optional `sql_definition` field in `PostDatasetsRequest` for better model representation.
- Refactored `get_model_files` to support recursive directory processing, improving model file retrieval.
- Implemented logging for model file uploads to Buster, enhancing operational visibility.
These changes streamline the initialization and model file management, laying the groundwork for future enhancements.
Nate Kelley
Nate Kelley
dal
porter-deployment-app[bot]
Dallin Bentley