chore: add a task to automatically onboard all SDK services#36
Merged
Conversation
ctreatma
force-pushed
the
generate-all
branch
2 times, most recently
from
399c741 to
2840c7c
Compare
ctreatma
force-pushed
the
generate-all
branch
from
2840c7c to
ee5b681
Compare
ctreatma
force-pushed
the
generate-all
branch
from
ee5b681 to
62cdab1
Compare
|
This PR is included in version 0.3.0 🎉 |
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
1 participant
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 adds a
generate-allMake task that can be used to onboard/update every service defined by equinix-sdk-go at once. This task provides a path for automatically introducing CLI support for any service that is onboarded to the Go SDK, rather than requiring each team to onboard themselves to the CLI after they have onboarded to the Go SDK.I have written the
generate-alltask to reuse the existingonboardandupdatetasks rather than replacing it so that we have the option to revisit the question of generating all services automatically vs. explicitly onboarding/updating services one at a time.