boilerplate for plugin interface - #1
Merged
Merged
Conversation
Author
|
@sajit this hasn't been tested, but just sort of wanted to contribute some boilerplate here and sketch out how this interacts with the plugin infrastructure itself. Feel free to ask me questions on what has been done here. next, I'm going to write an integration test harness that invokes the whole plugin to test all that grpc stuff |
ameijer
pushed a commit
to ameijer/opencost-plugins
that referenced
this pull request
Sep 3, 2024
…to atlas-plugin * 'atlas-plugin' of github.com:ameijer/opencost-plugins: Added tests for atlasconfig.go boilerplate for plugin interface (sajit#1)
sajit
pushed a commit
that referenced
this pull request
Oct 16, 2024
Merge Alex's PR to continue work on branch Signed-off-by: sajit <sajit@kunnumkal.com>
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.
What does this PR change?
Does this PR relate to any other PRs?
How will this PR impact users?
Does this PR address any GitHub or Zendesk issues?
How was this PR tested?
Does this PR require changes to documentation?