User Content Homepage

the homepage displays a list of content packages, along with the ability to push and pull changes with git integration if a remote repository is configured here’s what is displayed title the name of the content package origin the originating tenant where the content was published or shared from version displays the version of the published content the version displays version information only for content published from version 25 1 0 onward for ssps published before this version, the field appears empty however, performing a revert operation on such ssps will populate version information for their earlier publishes published on the date and time the content was published new with git integration push and pull content the push and pull buttons are enabled only if git integration is enabled and if a remote repository is set \# after publishing content into your library, click the push button in the top right to commit and push the changes to your connected remote repository # retrieve updates from the remote repository by clicking the pull button this will sync the latest changes from the repository into your swimlane turbine library ellipses menu options clicking on the ellipses (⋮) next to each content item opens additional options \# view detailed information and description about the content package and what it contains # review the history of changes made to the content, allowing you to track updates and revert to previous versions if necessary # deploy the playbook or component to another environment or tenant # permanently remove the selected content from the library pull changes from a remote repository click the pull button located at the top right corner of the content tab to start pulling the latest changes from the remote git repository pull button is not displayed when remote repository is not configured it also displays the number of commits the remote repository has if there are no differences between the two repositories, when you hover the mouse on the button it displays there are no changes to pull if there are any merge conflicts between the remote repository and your turbine library, a merge conflict dialog will appear the dialog lists the list of affected content and provide options keep library changes retain the current version in your turbine library keep remote changes use the version from the remote git repository click apply to resolve conflicts with your selected option once the process is complete, a success message confirming that all changes were successfully pulled into your library is displayed click close to finish the process push changes to a remote repository (same here, need to add details the "push" button will not display when the remote repository is not configured it will also display the number of commits that the local repository have that the remote repo do not if there are no differences between the two repos, on hover the button will say "there are no changes to push " when a remote repository configured, click the push button located at the top right corner to start pushing changes in your turbine library to the remote repository a progress dialog appears to show the status of the push if there are any merge conflicts between the remote repository and your turbine library, a merge conflict dialog will appear the dialog will list the affected content and provide options keep library changes retain the current version in your turbine library keep remote changes use the version from the remote repository click "apply" to resolve conflicts with your selected option once the process is complete, a success message confirming that all changes were successfully pulled into your library is displayed click close to finish the process resolving merge conflicts in swimlane turbine merge conflicts in swimlane turbine are rare but can occur in the following situations the remote repository is modified outside of swimlane turbine , such as via direct commits or edits made in github or gitlab the repository is shared across multiple turbine accounts , and concurrent changes lead to inconsistencies during push or pull operations unless one of these scenarios occurs, conflicts are unlikely during regular use conflict resolution in swimlane turbine swimlane turbine resolves merge conflicts at the application (package) level when multiple content items have conflicts between the turbine library and the remote git repository, the conflict resolution dialog presents each item individually for each conflicted application, you can keep local changes retain the version currently in your turbine library keep remote changes accept the version from the remote repository each option is accompanied by metadata to help inform your decision, including last published time published by (username) each conflicted item supports independent resolution using local or remote changes, with contextual metadata displayed steps to resolve merge conflicts trigger conflict detection during a push or pull operation, if any conflicts are found, a merge conflict dialog will appear review conflicted items all applications with detected conflicts will be listed individually in the dialog you will see the local and remote versions side by side, along with metadata such as last published time and user choose a resolution for each item keep local changes preserve the version in your turbine library and overwrite the remote version keep remote changes accept the version in the git repository and discard your local version after making selections, click apply to resolve the conflicts complete the operation once conflicts are resolved, the system continues the push or pull operation to synchronize your content key considerations application level resolution conflicts are resolved per application or package line by line resolution is not currently supported change tracking metadata such as timestamps and authorship help clarify which version to keep in complex scenarios conflict rarity merge conflicts are most likely in environments with shared repositories or manual remote changes handling errors in swimlane turbine during git operations when pushing or pulling changes to/from a remote repository in swimlane turbine, you may encounter various errors below are common errors and their respective handling instructions error cause solution unable to connect to remote repository this error typically occurs when the repository credentials are incorrect or missing verify the repository url and authentication credentials (for example, personal access token) update the credentials in the account settings > git integration section, and try the operation again wait a few minutes and retry the operation if the issue persists, contact your support team or the repository provider to verify the server status | \| 500 internal server error | this error is likely due to server issues on the repository side or connectivity problems | | \| unable to connect to remote repository | this error is likely due to server issues on the repository side or connectivity problems | | \| unable to connect to your remote repository (push failure) | any unexpected errors that has occurred in the system | | \| unable to connect to your remote repository (pull failure) | any unexpected errors that has occurred in the system | | \| content published locally but remote sync failed | the content was successfully published locally, but there was an error syncing with the remote repository | | \| content deleted locally but remote sync failed | the local deletion was successful, but the change could not be synced to the remote repository | | \| unexpected error occurred | this error is likely due to server issues on the repository side or connectivity problems | | understanding the content details tab the details tab within a content package in user content provides a comprehensive overview of content package following are the key features of the details tab title the name of the content (for example, csc update invoking record) created date the date when the content was originally created (for example, 02 01 24) description a detailed description or summary of the content this is used to explain the purpose and key details of the content workspace overview (at the top) displays a summary of content items associated in the package , such as workspaces the number of workspaces linked to this content (for example, 1) playbooks the number of playbooks associated with this content (for example, 2 in one area and 3 in another) components , assets , applications , applets , reports , and dashboards lists the numbers of these items linked to the content understanding the package contents tab the package contents tab provides a detailed breakdown of the entities included within the selected content item, such as playbooks, webhooks, workspaces, reports, and more this tab allows users to see all associated entities at a glance the package contents tab allows administrators and users to quickly view all the assets and resources tied to a specific content item, making it easy to understand how the various entities work together understanding the version history tab the version history tab provides a record of all the versions associated with a particular content item this tab allows users to track the changes made over time, review past modifications, and, if necessary, revert to a previous version key features of the version history tab version number each version is labeled with a specific number (for example, 2 0 0 , 1 1 0 ) the current version is clearly marked, helping users easily identify the latest version in use last modified this column displays the date and time when each version was last modified (for example, 03 31 24 , 02 24 19pm ) it helps users track when changes were applied message this column provides a brief message or description of the changes made in each version (for example, bug fix , initial release , or more detailed change notes like updated app to reflect current crowdstrike auth token ) these messages give insight into the purpose of each update, whether it was for a bug fix, new feature, or enhancement version selection users can select a previous version if they need to review or restore it deploying content to tenants swimlane turbine provides a secure method for deploy a content in the turbine library to tenatns below is a step by step process for deleting content steps to deploy a content navigate to the content you wish to deploy and click deploy from the list deploy window is displayed from the list of tenants, select the tenant where you want to deploy by clicking deploy to tenant select the components you would like to deploy click deploy reverting content in swimlane turbine to a previous version the version history tab within a content package in swimlane turbine provides the option to revert content to a previous version if necessary this feature allows you to undo updates and restore content to a specific earlier version while maintaining a clear log of changes steps to revert content select a version in the version history tab, select the version you want to revert to by clicking the corresponding radio button (for example, version 1 1 0) click revert after selecting the desired version, click the revert button a dialog will appear with a summary of the version selected, the current version, and additional details (for example, commit message for the current version) provide a reason for reverting in the additional information section, provide a reason for reverting the content (for example, content reverted in library ) user will also have the option to revise the new version number associated with this change this reason will be logged and tracked for future reference confirm reversion click revert to proceed with the action once the content is reverted, you will see a success message indicating success! the content has been successfully reverted in your library redeploy notice after reverting, you may see a redeploy notice, indicating that the version in your library might now be out of sync with the content in your tenants you will need to redeploy the reverted content to your tenants deleting content in swimlane turbine swimlane turbine provides a secure method for deleting content in the turbine library, ensuring that users understand the implications of the action and provide a reason for deletion below is a step by step process for deleting content steps to delete content initiate deletion navigate to the content you wish to delete (for example, csc update invoking record) open the delete option from the menu enter a reason for deletion the delete content dialog box will appear, requiring you to provide a reason for deleting the content enter reason for deleting content there is no default message for deletion, so the user must manually enter the reason this helps in tracking the context for deletion in logs and reports the delete button remains disabled until a reason for deletion is provided confirm deletion after entering the reason, click delete to proceed a confirmation dialog will appear, stating that the action will delete the content and its entire history from your library and any connected remote repository click and hold the delete icon to confirm the action successful deletion after confirmation, a success message will appear indicating success! the content was successfully deleted resetting the turbine library to a previous version swimlane turbine allows users to reset their entire content library to a previous point in time this feature is useful when a user needs to revert the library to a specific state, undoing any subsequent changes below are the steps for resetting the library steps to reset the library access library history click on the icon to navigate to the library history this section shows all commit activities or changes made to the library along with the user who made the changes, the commit message, and the date of modification select the commit select the commit at the point in time to which you want to reset the library you can only select one commit at a time, and all other rows become disabled once a selection is made click reset click the reset button to begin the process a dialog box will appear with information about the selected commit, including the date and commit message (for example, bug fix) a warning message will appear stating that resetting will reset the library to its previous state , and any changes made after the selected time will be reverted provide a reason enter a reason for resetting the library in the additional information field this will be logged to maintain a clear record of why the reset occurred confirm the reset to confirm, click and hold the reset button a message will appear asking if you are sure you want to reset the library, along with the date and time of the selected version success notification after successfully resetting the library, a success message will appear success! your turbine library has been reset to its state as of {selected date and time} a redeploy notice will appear, indicating that your content might be out of sync with tenants you will need to manually redeploy the content to each tenant by combining these features with the git integration options, you can now easily manage, track, and version control all of your turbine content across tenants and environments see / / /orchestration/playbooks md and / / /orchestration/components md for details on how to publish either from their respective canvas's and homepages