OpenParable
Skip to content
← Back to skills

Manage Cloud Project

DevOps & Security
manage-cloud-project

Manage Cloud Project is an Agent Skill for devops & security published in the liferay/liferay-portal repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Authenticate to and operate on a Liferay Cloud (LXC / DXP Cloud) project via the `lcp` CLI — deploy client extensions, view logs, restart services, list resources. Use when the user mentions lcp/LXC/liferay.cloud, when an LCP.json is present in the workspace, or when the user references a console.liferay.cloud URL.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/liferay/liferay-portal/blob/HEAD/workspaces/clarity-solution-workspace/.workspace-rules/skills/manage-cloud-project/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/manage-cloud-project, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Manage Cloud Project

Operate on a Liferay Cloud project from the lcp CLI.

When to Invoke

  • lcp, LXC, liferay.cloud, or DXP Cloud is mentioned.
  • An LCP.json file exists in the workspace.
  • The user references a console.liferay.* URL.

"Deploy to dev/uat/prd" alone is not a trigger. Those names also describe local environments under configs/{env}/. Require an explicit cloud signal.

Establish Context

Resolve each before proceeding:

  1. lcp --version — is the CLI installed?

  2. lcp remote — is a default remote set?

  3. <project>-<env> — what is the intended target?

Workflow

  1. Identify the target. Confirm <project>-<env> with the user. Use lcp list if uncertain.

  2. Deploy. Run lcp deploy. Discover flags via lcp deploy --help.

  3. Verify runtime health. Tail lcp log for the target service. Apply the runtime activation rule from liferay-rules.md: a successful command exit is not success.

For any other operation, discover available commands via lcp --help.

Pitfalls

  • <project>-<env> naming overlaps with local configs/{env}/ directories. Confirm cloud target before assuming.
  • LCP.json placement controls deploy scope: at repo root, lcp deploy deploys all services; from a service folder, it deploys only that one.

Composition

  • Counterpart to deploy-and-verify, which targets local Tomcat or Docker.
  • Consumes the artifacts produced by scaffold-client-extension.
  • Defer credential and secret handling to production-standards.

References

  • lcp --help and lcp <cmd> --help
  • https://learn.liferay.com/w/dxp/cloud/reference/command-line-tool