@siloy/hubspot-provisioning 0.1.0 → 0.1.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +7 -7
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -7,7 +7,7 @@ Requires Node 20 or newer.
|
|
|
7
7
|
## Install
|
|
8
8
|
|
|
9
9
|
```sh
|
|
10
|
-
npx -y @siloy/hubspot-provisioning@0.1.
|
|
10
|
+
npx -y @siloy/hubspot-provisioning@0.1.1 validate
|
|
11
11
|
```
|
|
12
12
|
|
|
13
13
|
In CI, run this pinned `npx` form (see "GitHub Actions"); don't install the CLI as a repo dependency in a job that has the deploy key. For editor support of the schema, a local install is fine: `npm install --save-dev @siloy/hubspot-provisioning`.
|
|
@@ -44,7 +44,7 @@ hubspot-provisioning deploy [file] [plan options except --mode]
|
|
|
44
44
|
On a `pull_request` event, `GITHUB_SHA` and `GITHUB_REF` are the merge commit and `refs/pull/N/merge`, not your branch. That is what the plan is recorded under unless you pass the head yourself:
|
|
45
45
|
|
|
46
46
|
```yaml
|
|
47
|
-
- run: npx -y @siloy/hubspot-provisioning@0.1.
|
|
47
|
+
- run: npx -y @siloy/hubspot-provisioning@0.1.1 plan --mode preview --sha "$HEAD_SHA" --ref "$HEAD_REF"
|
|
48
48
|
env:
|
|
49
49
|
npm_config_registry: https://registry.npmjs.org
|
|
50
50
|
HEAD_SHA: ${{ github.event.pull_request.head.sha }}
|
|
@@ -83,7 +83,7 @@ A key expires after 90 days without use, counted from its last use, creation or
|
|
|
83
83
|
|
|
84
84
|
## GitHub Actions
|
|
85
85
|
|
|
86
|
-
Preview on pull requests (with a comment that is updated, not repeated) and deploy on pushes to `main`. Pin the actions by commit SHA as your own policy requires; versions are shown here for readability. The samples pin 0.1.
|
|
86
|
+
Preview on pull requests (with a comment that is updated, not repeated) and deploy on pushes to `main`. Pin the actions by commit SHA as your own policy requires; versions are shown here for readability. The samples pin 0.1.1; pin the version you use and bump it on purpose.
|
|
87
87
|
|
|
88
88
|
```yaml
|
|
89
89
|
# .github/workflows/blueprint.yml
|
|
@@ -111,11 +111,11 @@ jobs:
|
|
|
111
111
|
node-version: 24
|
|
112
112
|
# No npm ci: the job holds the deploy key, so it runs only the pinned CLI, never the branch's dependencies.
|
|
113
113
|
# npm_config_registry outranks a project .npmrc, so a branch cannot point npx at another registry.
|
|
114
|
-
- run: npx -y @siloy/hubspot-provisioning@0.1.
|
|
114
|
+
- run: npx -y @siloy/hubspot-provisioning@0.1.1 validate
|
|
115
115
|
env:
|
|
116
116
|
npm_config_registry: https://registry.npmjs.org
|
|
117
117
|
- run: >-
|
|
118
|
-
npx -y @siloy/hubspot-provisioning@0.1.
|
|
118
|
+
npx -y @siloy/hubspot-provisioning@0.1.1 plan --mode preview
|
|
119
119
|
--comment-file plan-comment.md
|
|
120
120
|
--sha "$HEAD_SHA" --ref "$HEAD_REF"
|
|
121
121
|
env:
|
|
@@ -153,7 +153,7 @@ jobs:
|
|
|
153
153
|
- uses: actions/setup-node@v7
|
|
154
154
|
with:
|
|
155
155
|
node-version: 24
|
|
156
|
-
- run: npx -y @siloy/hubspot-provisioning@0.1.
|
|
156
|
+
- run: npx -y @siloy/hubspot-provisioning@0.1.1 deploy
|
|
157
157
|
env:
|
|
158
158
|
npm_config_registry: https://registry.npmjs.org
|
|
159
159
|
PROVISIONING_URL: ${{ vars.PROVISIONING_URL }}
|
|
@@ -195,7 +195,7 @@ The schema is also available as `@siloy/hubspot-provisioning/schema.json`. It de
|
|
|
195
195
|
|
|
196
196
|
## Upgrading
|
|
197
197
|
|
|
198
|
-
When the blueprint rules change, the server may refuse older CLIs with `cli_outdated`. Upgrade with `npm install --save-dev @siloy/hubspot-provisioning@latest`, or raise the version in your workflow's `npx -y @siloy/hubspot-provisioning@0.1.
|
|
198
|
+
When the blueprint rules change, the server may refuse older CLIs with `cli_outdated`. Upgrade with `npm install --save-dev @siloy/hubspot-provisioning@latest`, or raise the version in your workflow's `npx -y @siloy/hubspot-provisioning@0.1.1`.
|
|
199
199
|
|
|
200
200
|
When a command fails after the server created a run, it prints `Plan run:` and `Apply run:` ids; look them up in the provisioning app. After a timeout or error while waiting for an apply, the apply may still be running: check it before re-running.
|
|
201
201
|
|