@itentialopensource/adapter-meraki 1.0.4 → 1.2.1

Sign up to get free protection for your applications and to get access to all the features.
package/CHANGELOG.md CHANGED
@@ -1,4 +1,28 @@
1
1
 
2
+ ## 1.2.1 [09-11-2023]
3
+
4
+ * Additional migration and metadata changes
5
+
6
+ See merge request itentialopensource/adapters/sd-wan/adapter-meraki!31
7
+
8
+ ---
9
+
10
+ ## 1.2.0 [08-16-2023]
11
+
12
+ * Minor/2023 migration
13
+
14
+ See merge request itentialopensource/adapters/sd-wan/adapter-meraki!30
15
+
16
+ ---
17
+
18
+ ## 1.1.0 [08-11-2023]
19
+
20
+ * Minor/2023 migration
21
+
22
+ See merge request itentialopensource/adapters/sd-wan/adapter-meraki!30
23
+
24
+ ---
25
+
2
26
  ## 1.0.4 [08-01-2023]
3
27
 
4
28
  * Update adapter base and import order
package/CONTRIBUTING.md CHANGED
@@ -10,163 +10,4 @@ This project and everyone participating in it is governed by the Code of Conduct
10
10
 
11
11
  ## How to Contribute
12
12
 
13
- ### Reporting Bugs
14
-
15
- This section guides you through submitting a bug report. Following these guidelines helps maintainers understand your report :pencil:, reproduce the behavior :computer: :left_right_arrow: :computer:, and find related reports :mag_right:.
16
-
17
- Before creating bug reports, please check before-submitting-a-bug-report, as you might find out that you don't need to create one. When you are creating a bug report, please include as many details as possible. If you have an Itential support contract, please create an Itential Service Desk ticket. If you don't have an Itential support contract, please send an email of the issue to support@itential.com.
18
-
19
- #### Before Submitting A Bug Report
20
-
21
- * **Check the README.md.** You might be able to find the cause of the problem and fix things yourself. Most importantly, check if you can reproduce the problem __in the latest version__.
22
- * **Work through the troubleshooting process.** Troubleshooting will include changing the log level of Itential Automation Platform (IAP) and adapters and checking the logs to see what the issues are. These logs should be included in any ticket you open for this issue.
23
- * **Check for resolutions to the issue.** Check the <a href="https://itential.atlassian.net/servicedesk/customer/kb/view/286883841?applicationId=605994d2-2cb2-3174-af59-ed5b23ff5fd5&spaceKey=PKB&src=1187380921" target="_blank">Itential Knowledge Base</a> to see if there is a known resolution for the issue you are having.
24
- * **Ask around in chat if you are an Itential employee** to see if others are experiencing the same issue.
25
-
26
- #### How to Submit a (Good) Bug Report
27
-
28
- Bugs are tracked through the Itential Service Desk. Explain the problem and include additional details to help maintainers reproduce the problem:
29
-
30
- - **Use a clear and descriptive title** for the issue to identify the problem.
31
- - **Describe the exact steps which reproduce the problem** in as much detail as possible. For example, start by explaining how you configured the adapter (e.g., which properties you used and how they were set) or how you are using an artifact.
32
- - **Provide specific examples to demonstrate the steps**. Include logs, or copy/paste snippets, in your examples.
33
- - **Describe the behavior you observed after following the steps** and point out what exactly is the problem with that behavior.
34
- - **Explain which behavior you expected to see instead and why.**
35
- - **Include screenshots and animated GIFs** which show you following the described steps and clearly demonstrate the problem. You can use <a href="https://www.cockos.com/licecap/" target="_blank">this tool</a> to record GIFs on macOS and Windows. Use <a href="https://github.com/colinkeenan/silentcast" target="_blank">this tool</a> or <a href="https://github.com/rhcarvalho/byzanz-guiz" target="_blank">program</a> on Linux.
36
- - **If the problem wasn't triggered by a specific action**, describe what you were doing before the problem happened and share more information using the guidelines below.
37
-
38
- Provide more context by answering these questions:
39
-
40
- - **Did the problem start happening recently** (e.g. after updating to a new version/tag) or was this always a problem?
41
- - If the problem started happening recently, **can you reproduce the problem in an older version/tag?** What's the most recent version in which the problem does not happen?
42
- - **Can you reliably reproduce the issue?** If not, provide details about how often the problem happens and under which conditions it normally happens.
43
-
44
- Include details about your configuration and environment:
45
-
46
- - **Which version of the adapter/artifact are you using?** You can get the exact version by checking the project version in the package.json file.
47
- - **What's the name and version of the OS you're using**?
48
- - **Are you running or using IAP in a virtual machine?** If so, which VM software are you using and which operating systems and versions are used for the host and guest?
49
- - **Are there firewalls between IAP and any other system you are integrating with?** If so, have you tried running curl from the system IAP is on to the other system to verify you have connectivity between the systems?
50
-
51
- ### Your First Code Contribution
52
-
53
- #### Local development
54
-
55
- This project can be developed locally on all operating systems. For instructions on how to do this, follow the steps highlighted in the README.md. The README.mdprovides many more details on cloning the repository for local development, how to lint and test your changes.
56
-
57
- #### Development Process
58
-
59
- The following provides a local copy of the repository along with dependencies.
60
-
61
- ```json
62
- go to the repository you are interested in working on
63
- click on the Clone button to get the link(s) you can use to clone the repository
64
- git clone <link to clone the project>
65
- npm install
66
- ```
67
-
68
- Prior to making changes you should create a branch to work in. The branch should be named with the type of change (major, minor or patch) and then a Jira issue number or a description of the issue.
69
-
70
- ```json
71
- git checkout -b <name_of_your_new_branch>
72
- ```
73
-
74
- Make all of the desired changes.
75
-
76
- > **Note:** All code changes should be accompanied by additional Unit and Integration tests to minimize the likelihood that any changes will negatively impact the adapter/artifact as well as to ensure the desired functionality is achieved.
77
-
78
-
79
- <table border="1" class="bordered-table">
80
- <tr>
81
- <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Files</span></th>
82
- <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Changes</span></th>
83
- </tr>
84
- <tr>
85
- <td style="padding:15px">.codeclimate.yml, .eslintignore, .eslintrc.js, .gitignore, .gitlab-ci.yml, .jshintrc, .npmignore</td>
86
- <td style="padding:15px">These are foundational files that are used in linting and building of the adapter. Changes to these files are heavily scrutinized and may be implemented in a different manner so that the changes can be implemented across all adapters.</td>
87
- </tr>
88
- <tr>
89
- <td style="padding:15px">CODE_OF_CONDUCT.md, CONTRIBUTING.md, LICENSE, README.md</td>
90
- <td style="padding:15px">These are license and process files for the repository. Changes to these files may require legal review and may also be implemented in a different manner so that the changes can be implemented across all adapters.</td>
91
- </tr>
92
- <tr>
93
- <td style="padding:15px">utils/*, adapterBase.js</td>
94
- <td style="padding:15px">Changes to these files will rarely be accepted. These are process files that need to be changed through the builder process and migration.</td>
95
- </tr>
96
- <tr>
97
- <td style="padding:15px">adapter.js</td>
98
- <td style="padding:15px">Changes to this file are code changes. They should be accompanied by the appropriate unit and integration tests. If new methods are added, they should also be added to the pronghorn.json file, otherwise integration tests are likely to fail.</td>
99
- </tr>
100
- <tr>
101
- <td style="padding:15px">error.json, propertiesSchema.json</td>
102
- <td style="padding:15px">These files are utilized by the Itential Runtime libraries. You can make changes to these files, but the changes should be appending of new errors or properties. Removal of errors and properties can result in rejection of the changes.</td>
103
- </tr>
104
- <tr>
105
- <td style="padding:15px">pacakge.json, package-lock.json</td>
106
- <td style="padding:15px">The package-lock.json is automatically generated and should only be updated when the dependencies inside of the package.json are modified. You can make changes to the package.json to add additional scripts, add new dependencies, modify names, etc. However, changing the scripts or dependencies that are Itential specific will be overriden during the acceptance process.</td>
107
- </tr>
108
- <tr>
109
- <td style="padding:15px">pronghorn.json</td>
110
- <td style="padding:15px">Changes to this file are made for integration into IAP. The most common change here is adding new methods that shoud be exposed to the IAP Workflow.</td>
111
- </tr>
112
- <tr>
113
- <td style="padding:15px">entities/*</td>
114
- <td style="padding:15px">Changes to these files include adding new capabilities, updating existing capabilities, or removing deprecated capabilities in the adapter. Translation configuration can also be modified here.</td>
115
- </tr>
116
- <tr>
117
- <td style="padding:15px">test/*</td>
118
- <td style="padding:15px">Changes to these files include adding, updating, or removing unit and integration tests in the adapter. Tests should never be removed unless the methods that are being tested are removed also. Both the unit and integration test file should have a marker that identifies where modification can take place. Modifications above that marker are likely to be rejected or implemented in a different manner.</td>
119
- </tr>
120
- </table>
121
- <br>
122
-
123
- > **Note:** It is a best practice to lint and test your code prior to committing changes into the repository. You can lint your code by running **npm run lint** and test it by running **node utils/testRunner.sh**. However, there are pre-commit hooks that will run these scripts when you commit your changes.
124
-
125
- Commit the changes to the repository.
126
-
127
- ```json
128
- git commit -a -m "<descriptive message>"
129
- ```
130
-
131
- > **Note:** There are pre-commit hooks in place. If the pre-commit hooks fail, you will need to address those issues before moving forward.
132
-
133
- Push the changes into the repository. This should only be done after the commit has successfully completed.
134
-
135
- ```json
136
- git push origin <name_of_your_new_branch>
137
- ```
138
-
139
- Create a Merge Request.
140
-
141
- ### Merge Requests
142
-
143
- - Fill out the provided merge request template.
144
- - Reference related issues and merge requests liberally.
145
- - Include screenshots and animated GIFs in your merge request whenever possible.
146
- - Follow the project Styleguide.
147
- - End all files with a newline.
148
-
149
- ## Styleguide
150
-
151
- ### Git Commit Messages
152
-
153
- - Use the present tense ("Add feature" not "Added feature")
154
- - Use the imperative mood ("Move cursor to..." not "Moves cursor to...")
155
- - Consider starting the commit message with an applicable emoji _(not required)_:
156
- - :art: `:art:` When improving the format/structure of the code.
157
- - :racehorse: `:racehorse:` When improving performance
158
- - :non-potable_water: `:non-potable_water:` When plugging memory leaks.
159
- - :memo: `:memo:` When writing documentation.
160
- - :penguin: `:penguin:` When fixing something on Linux.
161
- - :apple: `:apple:` When fixing something on macOS.
162
- - :checkered_flag: `:checkered_flag:` When fixing something on Windows.
163
- - :bug: `:bug:` When fixing a bug.
164
- - :fire: `:fire:` When removing code or files.
165
- - :green_heart: `:green_heart:` When fixing the CI build.
166
- - :white_check_mark: `:white_check_mark:` When adding tests,
167
- - :lock: `:lock:` When dealing with security.
168
- - :arrow_up: `:arrow_up:` When upgrading dependencies.
169
- - :arrow_down: `:arrow_down:` When downgrading dependencies.
170
- - :shirt: `:shirt:` When removing linter warnings.
171
-
172
- __Avoid installing unnecessary packages.__ Do not install packages just because they might be "nice to have". Itential Opensource projects are supposed to be minimal, specific, and compact by design.
13
+ Follow the contributing guide (here)[https://gitlab.com/itentialopensource/adapters/contributing-guide]
package/ENHANCE.md CHANGED
@@ -18,7 +18,7 @@ npm run adapter:update
18
18
 
19
19
  If you do not have a Swagger or OpenAPI document, you can use a Postman Collection and convert that to an OpenAPI document using APIMatic and then follow the first process.
20
20
 
21
- If you want to manually update the adapter that can also be done the key thing is to make sure you update all of the right files. Within the entities directory you will find 1 or more entities. You can create a new entity or add to an existing entity. Each entity has an action.json file, any new call will need to be put in the action.json file. It will also need to be added to the enum for the ph_request_type in the appropriate schema files. Once this configuration is complete you will need to add the call to the adapter.js file and, in order to make it available as a workflow task in IAP, it should also be added to the pronghorn.json file. You can optionally add it to the unit and integration test files. There is more information on how to work on each of these files in the <a href="https://www.itential.com/automation-platform/integrations/adapters-resources/" target="_blank">Adapter Technical Resources</a> on Dev Site.
21
+ If you want to manually update the adapter that can also be done the key thing is to make sure you update all of the right files. Within the entities directory you will find 1 or more entities. You can create a new entity or add to an existing entity. Each entity has an action.json file, any new call will need to be put in the action.json file. It will also need to be added to the enum for the ph_request_type in the appropriate schema files. Once this configuration is complete you will need to add the call to the adapter.js file and, in order to make it available as a workflow task in IAP, it should also be added to the pronghorn.json file. You can optionally add it to the unit and integration test files. There is more information on how to work on each of these files in the <a href="https://docs.itential.com/opensource/docs/adapters" target="_blank">Adapter Technical Resources</a> on our Documentation Site.
22
22
 
23
23
  ```text
24
24
  Files to update
@@ -66,4 +66,4 @@ Files to update
66
66
  * test/integration/adapterTestIntegration.js: add better data for the create and update calls so that they will not fail.
67
67
  ```
68
68
 
69
- As mentioned previously, for most of these changes as well as other possible changes, there is more information on how to work on an adapter in the <a href="https://www.itential.com/automation-platform/integrations/adapters-resources/" target="_blank">Adapter Technical Resources</a> on Dev Site.
69
+ As mentioned previously, for most of these changes as well as other possible changes, there is more information on how to work on an adapter in the <a href="https://docs.itential.com/opensource/docs/adapters" target="_blank">Adapter Technical Resources</a> on our Documentation Site.
package/README.md CHANGED
@@ -14,6 +14,7 @@ Some of the page links in this document and links to other GitLab files do not w
14
14
  - [Testing](#testing)
15
15
  - [Configuration](./PROPERTIES.md)
16
16
  - [Using this Adapter](./CALLS.md)
17
+ - [Authentication](./AUTH.md)
17
18
  - [Additional Information](#additional-information)
18
19
  - [Enhancements](./ENHANCE.md)
19
20
  - [Contributing](./CONTRIBUTING.md)
@@ -31,7 +32,7 @@ Itential Product and opensource adapters utilize SemVer for versioning. The curr
31
32
 
32
33
  Any release prior to 1.0.0 is a pre-release. Initial builds of adapters are generally set up as pre-releases as there is often work that needs to be done to configure the adapter and make sure the authentication process to Meraki works appropriately.
33
34
 
34
- Release notes can be viewed in CHANGELOG.md or in the <a href="https://itential.atlassian.net/servicedesk/customer/portals" target="_blank">Customer Knowledge Base</a> for Itential adapters.
35
+ Release notes can be viewed in CHANGELOG.md.
35
36
 
36
37
  ## Supported IAP Versions
37
38
 
@@ -47,17 +48,20 @@ These instructions will help you get a copy of the project on your local machine
47
48
 
48
49
  ### Helpful Background Information
49
50
 
50
- There is adapter documentation available on the Itential Developer Site <a href="https://www.itential.com/automation-platform/integrations/adapters-resources/" target="_blank">HERE</a>. This documentation includes information and examples that are helpful for:
51
+ There is <a href="https://docs.itential.com/opensource/docs/adapters" target="_blank">Adapter documentation available on the Itential Documentation Site</a>. This documentation includes information and examples that are helpful for:
51
52
 
52
53
  ```text
53
54
  Authentication
54
- Properties
55
+ IAP Service Instance Configuration
55
56
  Code Files
56
- Action Files
57
- Schema Files
58
- Mock Data Files
57
+ Endpoint Configuration (Action & Schema)
58
+ Mock Data
59
+ Adapter Generic Methods
60
+ Headers
61
+ Security
59
62
  Linting and Testing
60
- Troubleshooting
63
+ Build an Adapter
64
+ Troubleshooting an Adapter
61
65
  ```
62
66
 
63
67
  Others will be added over time.
@@ -96,6 +100,10 @@ The following list of packages are required for Itential opensource adapters or
96
100
  <td style="padding:15px">commander</td>
97
101
  <td style="padding:15px">Utilized by the node scripts that are included with the adapter; helps to build and extend the functionality.</td>
98
102
  </tr>
103
+ <tr>
104
+ <td style="padding:15px">dns-lookup-promise</td>
105
+ <td style="padding:15px">Utilized by the node scripts that are included with the adapter; helps to build and extend the functionality.</td>
106
+ </tr>
99
107
  <tr>
100
108
  <td style="padding:15px">fs-extra</td>
101
109
  <td style="padding:15px">Utilized by the node scripts that are included with the adapter; helps to build and extend the functionality.</td>
@@ -112,14 +120,14 @@ The following list of packages are required for Itential opensource adapters or
112
120
  <td style="padding:15px">mongodb</td>
113
121
  <td style="padding:15px">Utilized by the node scripts that are included with the adapter; helps to build and extend the functionality.</td>
114
122
  </tr>
115
- <tr>
116
- <td style="padding:15px">network-diagnostics</td>
117
- <td style="padding:15px">Utilized by the node scripts that are included with the adapter; helps to build and extend the functionality.</td>
118
- </tr>
119
123
  <tr>
120
124
  <td style="padding:15px">nyc</td>
121
125
  <td style="padding:15px">Testing coverage library that is utilized by some of the node scripts that are included with the adapter.</td>
122
126
  </tr>
127
+ <tr>
128
+ <td style="padding:15px">ping</td>
129
+ <td style="padding:15px">Utilized by the node scripts that are included with the adapter; helps to build and extend the functionality.</td>
130
+ </tr>
123
131
  <tr>
124
132
  <td style="padding:15px">readline-sync</td>
125
133
  <td style="padding:15px">Utilized by the node script that comes with the adapter; helps to test unit and integration functionality.</td>
@@ -143,7 +151,6 @@ eslint
143
151
  eslint-config-airbnb-base
144
152
  eslint-plugin-import
145
153
  eslint-plugin-json
146
- package-json-validator
147
154
  testdouble
148
155
  ```
149
156
 
@@ -172,7 +179,9 @@ tar -xvf adapter-meraki.tar
172
179
 
173
180
  ```bash
174
181
  cd adapter-meraki
175
- npm run adapter:install
182
+ npm install
183
+ npm run lint:errors
184
+ npm run test
176
185
  ```
177
186
 
178
187
  4. Restart IAP
@@ -181,17 +190,20 @@ npm run adapter:install
181
190
  systemctl restart pronghorn
182
191
  ```
183
192
 
184
- 5. Change the adapter service instance configuration (host, port, credentials, etc) in IAP Admin Essentials GUI
193
+ 5. Create an adapter service instance configuration in IAP Admin Essentials GUI
194
+
195
+ 6. Copy the properties from the sampleProperties.json and paste them into the service instance configuration in the inner/second properties field.
196
+
197
+ 7. Change the adapter service instance configuration (host, port, credentials, etc) in IAP Admin Essentials GUI
185
198
 
186
- npm run adapter:install can be dependent on where the adapter is installed and on the version of IAP so it is subject to fail. If this happens you can replace step 3-5 above with these:
199
+
200
+ For an easier install of the adapter use npm run adapter:install, it will install the adapter in IAP. Please note that it can be dependent on where the adapter is installed and on the version of IAP so it is subject to fail. If using this, you can replace step 3-5 above with these:
187
201
 
188
202
  3. Install adapter dependencies and check the adapter.
189
203
 
190
204
  ```bash
191
205
  cd adapter-meraki
192
- npm run install
193
- npm run lint:errors
194
- npm run test
206
+ npm run adapter:install
195
207
  ```
196
208
 
197
209
  4. Restart IAP
@@ -200,11 +212,8 @@ npm run test
200
212
  systemctl restart pronghorn
201
213
  ```
202
214
 
203
- 5. Create an adapter service instance configuration in IAP Admin Essentials GUI
204
-
205
- 6. Copy the properties from the sampleProperties.json and paste them into the service instance configuration in the inner/second properties field.
215
+ 5. Change the adapter service instance configuration (host, port, credentials, etc) in IAP Admin Essentials GUI
206
216
 
207
- 7. Change the adapter service instance configuration (host, port, credentials, etc) in IAP Admin Essentials GUI
208
217
 
209
218
  ### Testing
210
219
 
@@ -268,7 +277,7 @@ Test should also be written to clean up after themselves. However, it is importa
268
277
 
269
278
  ### Helpful Links
270
279
 
271
- <a href="https://www.itential.com/automation-platform/integrations/adapters-resources/" target="_blank">Adapter Technical Resources</a>
280
+ <a href="https://docs.itential.com/opensource/docs/adapters" target="_blank">Adapter Technical Resources</a>
272
281
 
273
282
  ### Node Scripts
274
283
 
package/SYSTEMINFO.md CHANGED
@@ -1,4 +1,4 @@
1
- # Meraki
1
+ # Cisco Meraki
2
2
 
3
3
  Vendor: Cisco
4
4
  Homepage: https://www.cisco.com/
@@ -7,5 +7,18 @@ Product: Meraki
7
7
  Product Page: https://meraki.cisco.com/
8
8
 
9
9
  ## Introduction
10
+ We classify Cisco Meraki into the SD-WAN/SASE domain as Cisco Meraki devices provide a Software Defined Wide Area Network (SD-WAN) solution. We also classify it into the Inventory domain because it contains an inventory of Meraki devices.
10
11
 
11
- ## Additional Product Documentation
12
+ "Cisco Meraki improves connectivity for remote and hybrid workers."
13
+ "Cisco Meraki makes the workspace safer both digitally and physically."
14
+
15
+ The Cisco Meraki adapter can be integrated to the Itential Device Broker which will allow your Cisco Meraki devices to be managed within the Itential Configuration Manager Application.
16
+
17
+ ## Why Integrate
18
+ The Cisco Meraki adapter from Itential is used to integrate the Itential Automation Platform (IAP) with Cisco Meraki. With this adapter you have the ability to perform operations such as:
19
+
20
+ - Configure and Manage Cisco Meraki Devices.
21
+
22
+ ## Additional Product Documentation
23
+ The [API documents for Cisco Meraki](https://developer.cisco.com/meraki/api-latest/)
24
+ [Cisco Meraki Products](https://www.cisco.com/c/m/en_hk/products/meraki.html)