Add Additional AM Config Imports and Exports #472
Merged
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR has a bunch of other AM config exports and imports. The majority of the config is read only and doesn't get imported, but some of it can be imported. In order to prevent having separate files for all the exports and imports, I created a more generalized way to handle them. In the future, if we want to have special functionality for them beyond simply exporting/importing their config, we will likely want to separate them out into their own files like with the other exports and imports.
I used a script to scrape endpoint and resource version information from Amster. The goal was to export/import as much as we could that Amster handles and that is missing from Frodo. Resource versions are based on the latest ones contained in the documentation as of version 7.5 (see the Amster entity reference documentation for more information).
This PR should be merged in prior to the PR named "Update Full Config Export with new Imports and Exports" that updates the full config export/import since that PR will rely on the changes from this PR.