[scraper]: Add support for deducing resource name from file path #172
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.
Description of your changes
This PR adds support for deducing resource name from the markdown file's path if the scraper cannot extract it from the markdown file. It also adds the optional
--resource-prefix
command-line option to the scraper so that the calling repo can specify the prefix to be used as a prefix for the name extracted from the markdown file path. For example, for thehashicorp/google
, this prefix isgoogle
because the markdown files are named with this prefix concatenated by the resource's name, e.g.,google_network_management_connectivity_test
.I have:
make reviewable
to ensure this PR is ready for review.backport release-x.y
labels to auto-backport this PR if necessary.How has this code been tested
Tested via the
upbound/provider-gcp
here.Also tested against the upbound/provider-{aws,azure}.