feat: add plugin install

[roleyfoley]

Intent of Change

• Documentation (new or update to existing)

Description

Adds an initial how-to guide for installing plugins into a CMDB

Motivation and Context

Makes it easier to understand how plugins work and what they can do

How Has This Been Tested?

Tested locally

Related Changes

Prerequisite PRs:

• None

Dependent PRs:

• None

Consumer Actions:

• None

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/hamlet/hamlet-docs/7eFyW6jge9RhiGztkhTb8ceQR9GL
✅ Preview: https://hamlet-docs-git-add-plugin-install-guide-hamlet.vercel.app

[ken9ross]

When looking at layers I don't get comparable results. I get

$ hamlet --account mswdev02 layer list-layers
| Name   | Id             | Type        | Active   |
|--------|----------------|-------------|----------|
| None   | alm            | Environment | None     |
| None   | shared         | Environment | None     |
| None   | dev            | Environment | None     |
| None   | alpha          | Environment | None     |
| None   | beta           | Environment | None     |
| None   | int            | Environment | None     |
| None   | aat            | Environment | None     |
| None   | uat            | Environment | None     |
| None   | system         | Environment | None     |
| None   | preprod        | Environment | None     |
| None   | stg            | Environment | None     |
| None   | prod           | Environment | None     |
| None   | trn            | Environment | None     |
| None   | ap-southeast-2 | Region      | None     |

This may be that I have the wrong context (as I found that unclear as to whether it was the segment context or the account context), so something else. I was using current unicycle 14 Dec)

[roleyfoley]

Thanks @ken9ross Can you update to the latest unicycle release and see if it works?

I've just tested on the latest version and it seems to be working fine. I think some of the engine Pull requests hadn't caught up.

[ml019]

@roleyfoley I got the correct results when in the segment directory. I also ran it in the root of the cmdb for a product (/cot/ormss) and got the following error

The following has evaluated to null or missing:
==> layerData.Id  [in template "shared/views/info/setup.ftl" at line 139, column 20]


In this case there won't be an environment or segment layer so maybe they are throwing the error?