Automated Regions data #861
Open
+1,377
−281
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
Collaborator
|
This PR includes documentation updates Updated pages: |
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.
Adds an Antora extension at
scripts/regions.js.Data source
The extension reads a json file and parses it into asciidoc tables that are displayed as a series of tabbed sections to display cloud provider region information for the different Aura tiers.
The extension looks for the data at the local filepath data/regions.json in this repository.
Output
The output is added to the Antora contentCatalog, by writing the generated asciidoc to the contents of the partial file at
partials/regions-generated.adoc. (Note that the file is itself is not written). This partial file is included inmanaging-instances/regions.adoc.