@agilecustoms/envctl 0.2.0 → 0.3.0

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.
@@ -17,8 +17,6 @@ jobs:
17
17
  needs:
18
18
  - Build
19
19
  runs-on: ubuntu-latest
20
- permissions:
21
- contents: write
22
20
  steps:
23
21
  - name: Checkout
24
22
  uses: actions/checkout@v4
package/README.md CHANGED
@@ -6,7 +6,7 @@
6
6
  ```shell
7
7
  npm install -g @agilecustoms/envctl # same command for update
8
8
  envctl --version
9
- npm outdated -g
9
+ npm outdated -g
10
10
  npm view @agilecustoms/envctl version # show latest version available (without installing)
11
11
  ```
12
12
 
@@ -23,6 +23,7 @@ npm view @agilecustoms/envctl version # show latest version available (without i
23
23
  1. Name `NPMJS_TOKEN`
24
24
  2. Repository access: `envctl` only
25
25
 
26
+ ## History/motivation
26
27
  dev-env is a microservice hosted in 'maintenance' account and working as garbage collector: every environment first
27
28
  created in dev-env and then 'managed' by dev-env: it deletes env when it is not in use anymore OR can extend lifetime.
28
29
  Creation API yields unique ID, so you can safely manage env (delete, extend lifetime) via this ID. But creation API
@@ -40,4 +41,7 @@ Now problem is: any request needs to be signed with AWS signature v4. Originally
40
41
  quickly became bulky and hard to maintain. Then I thought about Node.js - it is available on dev machines and
41
42
  in GitHub actions (namely in Ubuntu runners). How to distribute it? First I thought about using `ncc` to bundle in one
42
43
  big .js file (as I do for `gha-upload-3` and `gha-healthcheck`) but it will be hard to use on dev machine...
43
- So I ended up with publishing this client as npm package in CodeArtifact and then running from anywhere with `npx`!
44
+
45
+ So I ended up with publishing this client as npm package in npmjs
46
+ - CI environments can install & run it with one command via `npx`
47
+ - developer will install it globally via `npm install -g @agilecustoms/envctl`
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@agilecustoms/envctl",
3
3
  "description": "node.js CLI client for manage environments",
4
- "version": "0.2.0",
4
+ "version": "0.3.0",
5
5
  "author": "Alex Chekulaev",
6
6
  "type": "module",
7
7
  "bin": {