Push / Pull Sites

[fabrizzio-dotCMS]

Using the Quarkus example supplied by Steve, we should begin the process of building out a CLI that can "sync" e.g. pull and push Sites to dotCMS.

Questions:

Hostname vs. hostId
Deterministic Ids?
Use content type var everywhere
hide default fields
e.g. don't show props that have false/0/empty string
How to handle content type updates / deletes

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[nollymar]

Internal QA: Needs work

• The host switch is not failing now but the site is never switched even when it says Successfully switching to site: [mysitename].

• I keep seeing this typo Site [test2] **delete** successfully

• I can't push a new site using a json or yml file

[fabrizzio-dotCMS]

host switch command does not work for our CLI client because we're not sending the session tracking bits.
All we send is an authentication token
The site switch operation occurs at the session level on the server side. But it is failing to track a session for the cli
so we're getting the fallback which is the current site.
@spbolton you think is it possible to add the missing bits to accomplish session tracking?

[wezell]

we should not host switch with the CLI. the CLI needs to be stateless.

[fabrizzio-dotCMS]

ok, then I'll remove the site switch command

[dcolina]

Internal QA:

Step by step:

1. Login via CLI with the command login -u [email protected] -p admin.

2. Download the default site with the command site pull --format=YAML -to=backup.dotcms.com.yaml demo.dotcms.com.

3. Using a text editor, change some properties of the file backup.dotcms.com.yaml. For example

---
siteName: "backup.dotcms.com"
tagStorage: "SYSTEM_HOST"
keywords: "CMS, Web Content Management, Open Source, Java, J2EE, DXP, NoCode, OSGI,\
  \ Apache Velocity, Elasticsearch, RESTful Services, REST API, Workflows, Personalization,\
  \ Multilingual, I18N, L10N, Internationalization, Localization, Docker CMS, Containerized\
  \ CMS"
description: "dotCMS testing site pull / push command ::::"
languageId: 1
modDate: "2023-06-02T00:00:00.000+00:00"
modUser: "dotcms.org.1"
live: true
working: true

4. Once the file is saved, we publish it with the command site push --force --format=YAML backup.dotcms.com.yaml.

HINT:
Instead of checking [ERROR] ❗ No site named [backup.dotcms.com] was found. I think that a [WARN] might be better because after all the push operation is running correctly.

5. As a last step, we list all sites with the site command, in the result we can see both the default site and the new site uploaded in the previous step.

NOTE:
When running the site help command, there is a small error in the description of the --force parameter, "Force must me set to true to update a site name". It should read "Force must be set to true to update a site name".

Internal QA: PASSED.

• Functionality works as expected.