@itentialopensource/adapter-amazon_route53 0.4.9 → 0.4.11

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/AUTH.md CHANGED
@@ -34,12 +34,20 @@ you can leave all of the other properties in the authentication section, they wi
34
34
  4. Restart the adapter. If your properties were set correctly, the adapter should go online.
35
35
 
36
36
  ### AWS Security Token Service
37
- The AWS Route53 adapter also supports AWS Security Token Service (STS) Authentication. This can also be referred to as standard credential but then STS assume role based on STS Params on Task.
38
- Adapter Role => Task Role(s) or Pod Role => Task Role(s).
37
+ The AWS Route53 adapter also supports AWS Security Token Service (STS) Authentication. This can also be referred to as standard credential but then STS assume role based on a global role or a task role provided in the STS Params on Task.
38
+ Adapter Role => Global or Task Role(s) or Pod Role => Task Role(s).
39
39
 
40
- Provide access key and secret key in adapter service instance configuration (Adapter Role). Will use these credentials on the assume role request to assume a different role defined in the STSParams on the task (Task Role). The Task Role will then be used to sign the call to AWS. The Adapter Role has to have the right to assume the Task Role or the call will fail. If no access key and/or secret key are provided, it will use AWS Environment variables (which is Saas is the Pod Role) to attempt the assume a different role defined in the STSParams on the task (Task Role). The Task Role will then be used to sign the call to AWS. The Pod Role has to have the right to assume the Task Role or the call will fail.
40
+ Provide access key and secret key in adapter service instance configuration (Adapter Role). Will use these credentials on the assume role request to assume a different role defined in the Global Role or STSParams on the task (Task Role). The Task Role will then be used to sign the call to AWS. The Adapter Role has to have the right to assume the Task Role or the call will fail. If no access key and/or secret key are provided, it will use AWS Environment variables (which is Saas is the Pod Role) to attempt the assume a different role defined in the STSParams on the task (Task Role). The Task Role will then be used to sign the call to AWS. The Pod Role has to have the right to assume the Task Role or the call will fail.
41
41
 
42
- For using this authentication, you need to use the calls in the Adapter that have the STSRole suffix on them and pass the STS information into the method. You will still need to provide the relevant `aws_secret_key` and `aws_access_key` as described above. Below is an example of the data required in the `sts` tasks:
42
+ For using the global role you need to define the global role in the adapter service instance configuration.
43
+
44
+ ```json
45
+ "authentication": {
46
+ "aws_iam_role": "arn:aws:iam::1234567:role/my_role"
47
+ }
48
+ ```
49
+
50
+ For using this authentication dynamically on a task by task basis, you need to use the calls in the Adapter that have the STSRole suffix on them and pass the STS information into the method. You will still need to provide the relevant `aws_secret_key` and `aws_access_key` as described above. Below is an example of the data required in the `sts` tasks:
43
51
 
44
52
  ```json
45
53
  {
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@itentialopensource/adapter-amazon_route53",
3
- "version": "0.4.9",
3
+ "version": "0.4.11",
4
4
  "description": "This adapter integrates with system described as: Amazon Route53.",
5
5
  "main": "adapter.js",
6
6
  "systemName": "Amazon AWS Route53",
@@ -55,10 +55,10 @@
55
55
  "author": "Itential",
56
56
  "homepage": "https://gitlab.com/itentialopensource/adapters/adapter-amazon_route53#readme",
57
57
  "dependencies": {
58
- "@itentialopensource/adapter-utils": "^5.10.1",
58
+ "@itentialopensource/adapter-utils": "^5.10.9",
59
59
  "acorn": "^8.14.0",
60
60
  "ajv": "^8.17.1",
61
- "axios": "^1.7.9",
61
+ "axios": "^1.8.2",
62
62
  "commander": "^11.0.0",
63
63
  "dns-lookup-promise": "^1.0.4",
64
64
  "fs-extra": "^11.2.0",
@@ -1,5 +1,5 @@
1
1
  {
2
- "version": "0.4.7",
2
+ "version": "0.4.9",
3
3
  "configLines": 9948,
4
4
  "scriptLines": 1783,
5
5
  "codeLines": 9292,
@@ -315,7 +315,7 @@ describe('[unit] Amazon_route53 Adapter Test', () => {
315
315
  assert.notEqual(null, packageDotJson.dependencies);
316
316
  assert.notEqual('', packageDotJson.dependencies);
317
317
  assert.equal('^8.17.1', packageDotJson.dependencies.ajv);
318
- assert.equal('^1.7.9', packageDotJson.dependencies.axios);
318
+ assert.equal('^1.8.2', packageDotJson.dependencies.axios);
319
319
  assert.equal('^11.0.0', packageDotJson.dependencies.commander);
320
320
  assert.equal('^11.2.0', packageDotJson.dependencies['fs-extra']);
321
321
  assert.equal('^10.8.2', packageDotJson.dependencies.mocha);