feat: generate HTML based on passed environment file#17
Draft
voltlol wants to merge 1 commit intoDonDebonair:mainfrom
Draft
feat: generate HTML based on passed environment file#17voltlol wants to merge 1 commit intoDonDebonair:mainfrom
voltlol wants to merge 1 commit intoDonDebonair:mainfrom
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.
This code generates the html file based on env yaml we use for ploy deployments.
It has couple of columns based on the data from env yaml file:
For now status is just a green checkmark. I thought to work with
ploy verifyoutput to set a proper green checkmark or red cross for example if there is a miss match. But I haven't started to work on this yet as I don't have a complete flow understanding in my head.To make it work I added to the test yaml file 2 new fields:
In HTML I added Source logo and made a dark theme page with table, but I think it should not go within this PR to make a tool more agnostic. I leave it for now so maybe you want to try it yourself and see something more or less beautiful.
I'd like to get some feedback on a go code changes as I put everything into a generate.go to keep it simple and working :) I know you have a lots of suggestions so I can learn more.