Rebase Test: Rebase master changes into build-pipeline-test #8
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This PR allows the `content-type export` and `content-type-schema export` commands to filter schemaIds with a regex. This behaves similarly to the other commands, in that filters starting and ending with a `/` are treated as a regex. Example: `dc-cli content-type export folder --schemaId /1|2/` Will export content types with schema ID containing either 1 or 2. You can provide multiple regex by providing multiple --schemaId arguments. Similar to how it worked before, if any --schemaId options don't match any types/schemas, an error will be thrown.
Replica names were not being rewritten when importing into a new hub. This PR should fix that issue.
…ounts where it is disabled (#125) This PR fixes an issue where empty import on certain commands would cause the command to error out, which would interrupt the clone command despite the import technically succeeding (as it didn't have to do anything). This also fixes an issue where search index list would throw an exception if it is disabled on the target account. In this case, the export is now simply skipped.
docs(readme): fix duplicate arguments in config examples
This PR adds commands to import and export events, as well as a clone step for the clone. It also depends on the facet changes, as it depends on one of the methods to select date ranges for events. The export command exports events with their editions and edition slots baked into the same json file to make them as portable as possible. Events contain an editions array, and editions contain a slots array. You can provide --fromDate and --toDate to limit the scope of the events you wish to export. You also have the option to export snapshots with your events, by using the --snapshots argument. This will place snapshot json files in a snapshots/ subfolder in your export directory, with the snapshot id as the filename. You can cross reference these from the IDs in event content. Importing is straightforward. Point the import <dir> command to a directory with events in the same format as the export. (events, editions, slots combined) Using the import command requires the --acceptSnapshotLimits argument. Importing snapshots is not supported, as the content items would have to be rapidly updated and reverted to create the snapshots, with a potentially very high number of child content items. Imported edition slots will instead generate snapshots on creation, from the existing state of the content in the hub. This might be revisited in future if a method is added to generate snapshots with more control (custom content? upload snapshot without validation?). Events, Editions and Edition Slots are now present on the mapping file. These are used to allow updating events by re-importing them. To import an event, your mapping file needs to have mappings for the content items contained within it. However, if you want to import events using content items that do not exist in the mapping file, but the ids in your imported json point to real content in your destination, you can use --originalIds to use original content IDs instead of mapped ones when importing events. This is useful for creating your own events to import with content that was not created by the CLI.
This is an alternative implementation to #145 which extends the existing publishing queue to support concurrent publishes. Benefits: - Publish() method actually starts the publish, dispatching is limited by both the rate limit and the concurrency limit. - Not too much change from the existing publish queue. Downsides: - Custom implementation of batching rather than a standard one, though this was technically already in place originally.
this commit adds the commands 'hub ls', 'hub add', and 'hub use' which manipulate dc-cli-config.json * chore: add @types/node * chore: remove yaml configuration support for node 12, update documentation * build(nodejs): removed nodejs 12.x support and added nodejs 18.x * build: require node 14 Co-authored-by: rs-amp <rsimpson@amplience.com>
#150) * fix(content-item): only assume links will be published, not references * test(content-item): add tests for traversing only link dependencies
* fix(event): correctly archive events with unscheduled editions * fix(event): wait for unschedule to complete before deleting editions
…ing updates (#160) * feat(settings): overwrite existing preview settings rather than ignoring updates * feat(settings): new allowDelete option to allow removal of existing settings * test(settings): add documentation and tests for allowDelete option
fix(hub): validateHub respects environment variables (#163)
Calls toJSON() on the various properties, if they are defined
…com:amplience/dc-cli into feature/support-async-search-index-requests
…er--components--dc-cli chore(master): release 0.25.0
…er--components--dc-cli chore(master): release 0.26.0
…er--components--dc-cli chore(master): release 0.26.1
…er--components--dc-cli chore(master): release 0.27.0
* feat: shift node versions to 24 and allow trusted publisher * feat: bumping axios to latest version * build: using update token for release please
* test: update to latest version of jest * feat: adding burstable queue * feat: adding publishing and publishing job services * refactor: update options, command options, modify tests * feat: content item import publish to use new services * feat: pass headers via custom dc http client to match sdk * test: updating import tests to use new publishing service * feat: removing redundant publishing flags * test: updating publish tests to use new publishing service * feat: add publish progress and only log to log file * feat: allow publish checks to occur without user input * test: adding tests for publishing services * fix: improve logging when publishing content * fix: moving publish complete log to correct scope * feat: add min time to burstable queue to spread load * fix: lowering min time to make sure we use the full burst interval reservoir * fix: log immediate children * fix: reintroduce publish content tree child item filtering * feat: bump to latest management sdk * fix: pin specific jest dependency versions --------- Co-authored-by: Ben Pearey <bpearey@amplience.com>
--------- Co-authored-by: Ben Pearey <bpearey@amplience.com>
* fix: resolving pacakge vulnerabilities * feat: adding command handler to manage linked content repositories * test: adding linked content repository list coverage * docs: adding docs for linked content repository list * feat: linked content respository update command * feat: add delete linked content repository command * feat: linked content respository create command * fix: revert to publish package * fix: json option to builder * fix: remove rendering options * fix: use RenderingOptions without wrapping * chore: bump management sdk to latest version --------- Co-authored-by: DB <dbhari@amplience.com>
--------- Co-authored-by: DB <dbhari@amplience.com> Co-authored-by: Neil Mistry <30687441+neilmistryamplience@users.noreply.github.com>
--------- Co-authored-by: Ben Pearey <bpearey@amplience.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
14 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.