First go at sync script for Cisco EoX Data from Cisco API #45
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This was related to #44 |
…ndOfServiceContractRenewal
|
Hey, Thanks for all of the effort. My thoughts were to actually integrate this as a background job. If you want to give that a go, feel free as I think a lot of your work would be usable there as well. |
Add data sync options to improve import of EoX data
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A first attempt at a sync script for pulling data from the Cisco Services API and syncing details in the hardware lifecycle models. Created as a command in the plugin. Was based off the cisco_support plugin command with significant change.
You need to generate a client_id and secret from the Cisco API console for the Support (not Services) API.
Open for any feedback.