[microservice-admin] Add new Admin Microservice #136
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
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.
As discussed previously on Discord, this PR creates the new
adminmicroservice.Which is destined to live at
https://admin.pulsar-edit.dev.It's purpose is to enable multiple team members the ability to preform routine data entry and modification of package's on the PPR.
The initial goal of this page is to allow other maintainers to take charge in adding badges to packages. Although the page's capabilities are very likely to expand in the future, this was the initial use case that inspired it's creation.
The page must be authenticated through GitHub, and is already prepared for local testing of this functionality.
The users that are able to successfully login via GitHub will have their
node_ids added to the secretenv.yamlfile at the root of this microservice, and will only be able to make changes if they are within that list.This is a draft PR until all functionality is finished, but thought it best to put it up for now, since a nearly all client side facing information is done, with simply being able to actually submit the data still in progress, but will likely be modeled exactly as
package-backends tool to add badges.