Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add option enables syncing of datasources without their corresponding dimension values #56

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

CaprinaeWT
Copy link
Contributor

@CaprinaeWT CaprinaeWT commented Jun 26, 2023

… dimension values

Pull request type

Jira Link: INT-

  • Bugfix
  • Feature
  • Code style update (formatting, renaming)
  • Refactoring (no functional changes, no api changes)
  • Other (please describe):

How to test this PR

storyblok sync --type datasources --source <SourceSpaceId> --target <TargetSpaceId> --datasource-disable-dimensions-value-sync

The --datasource-disable-dimension-sync options can be useful in certain scenarios where the synchronization of dimension values is not necessary or desired. While datasources are commonly used for translations, there may be cases where you only need to sync the structure or metadata of the datasources without including the actual dimension values.

For example, if you have a large dataset with frequently changing dimension values and you want to reduce the sync time or avoid potential conflicts, you may choose to disable the dimension sync. By doing so, you can focus on syncing the datasources themselves while excluding the specific dimension values, which can be later populated or updated separately if needed.

In summary, the option provides flexibility and efficiency by allowing users to selectively sync datasources without the burden of syncing the associated dimension values.

What is the new behavior?

The expected behavior when using the --datasource-disable-dimension-sync option is that the synchronization process will exclude the dimension values associated with the datasources. Only the structure and metadata of the datasources will be synced over to the target space, while the actual values of the dimensions will not be transferred.

This means that the target space will have the same datasources as the source space, including their names, configurations, but the specific values within those datasources' dimensions will not be replicated.

Other information

src/cli.js Outdated Show resolved Hide resolved
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants