@agilecustoms/envctl 0.23.2 → 0.23.3

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.
Files changed (2) hide show
  1. package/README.md +7 -7
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -36,17 +36,17 @@ needs to be secured. There are two main use cases:
36
36
  1. create environment from CI (mainly ephemeral envs)
37
37
  2. create env from dev machine
38
38
 
39
- I (Alex C) chosen IAM authorization as common denominator:
40
- 1. on CI - use OIDC to assume role `/ci/deployer`
41
- 2. on dev machine - use SSO and profile chaining to assume role `/ci/deployer`
39
+ I (Alex C) have chosen IAM authorization as common denominator:
40
+ 1. on CI use OIDC to assume role `/ci/deployer`
41
+ 2. on dev machine use SSO and profile chaining to assume role `/ci/deployer`
42
42
 
43
43
  Then as `/ci/deployer` --call--> `env-api` HTTP API (exposed with API Gateway with IAM authorizer)
44
44
 
45
- Now problem is: any request needs to be signed with AWS signature v4. Originally I planned to use bash scripts, but it
45
+ Now the problem is: any request needs to be signed with AWS signature v4. Originally I planned to use bash scripts, but it
46
46
  quickly became bulky and hard to maintain. Then I thought about Node.js - it is available on dev machines and
47
47
  in GitHub actions (namely in Ubuntu runners). How to distribute it? First I thought about using `ncc` to bundle in one
48
- big .js file (as I do for `gha-upload-3` and `gha-healthcheck`) but it will be hard to use on dev machine...
48
+ big .js file (as I do for `release-s3` and `gha-healthcheck`) but it will be hard to use on dev machine...
49
49
 
50
- So I ended up with publishing this client as npm package in npmjs
51
- - CI environments can install & run it with one command via `npx`
50
+ So I ended up publishing this client as npm package in npmjs
51
+ - CI environments can install it via GH action `agilecustoms/envctl`
52
52
  - 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.23.2",
4
+ "version": "0.23.3",
5
5
  "author": "Alex Chekulaev",
6
6
  "type": "module",
7
7
  "bin": {