Skip to content
This repository has been archived by the owner on Jul 22, 2024. It is now read-only.

Guide users to additional steps #2

Closed
3 of 4 tasks
andrewDoing opened this issue Jul 2, 2019 · 2 comments · Fixed by #16
Closed
3 of 4 tasks

Guide users to additional steps #2

andrewDoing opened this issue Jul 2, 2019 · 2 comments · Fixed by #16
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@andrewDoing
Copy link
Contributor

andrewDoing commented Jul 2, 2019

As a user I want guidance on the parts that were not automatically generated or some insight into what I might be missing to port over to fabrikate.

  • Determine what information to pre-populate in the yaml, for the additional services that were found in the cluster

  • Determine what information can be added as a comment in the generated yaml.

  • Add more guidance to the yaml by using comments.

  • Add information in the comments about the versions of the components so the user is aware of what version were pre-populated

Information that can be pre-populated

  • Deployments that match existing Fabrikate components
  • Deployments that don't match existing Fabrikate components
    • Name of the deployment

Information that the user must provide

  • Deployments that don't match existing Fabrikate components
    • Source repository link
    • Path (if necessary)
    • Generator (if using Helm)

User Steps

  1. Use hydrate to generate a component.yaml
  2. No Match deployments need information to be added OR they must be commented out.
  3. Follow the Fabrikate Steps to generate your manifests
@andrewDoing andrewDoing added the enhancement New feature or request label Jul 2, 2019
@andrewDoing andrewDoing added this to the Post-MVP milestone Jul 2, 2019
@andrewDoing andrewDoing self-assigned this Jul 2, 2019
@andrewDoing
Copy link
Contributor Author

@andrebriggs @mtarng @madelineliao
What I have currently is the following:

# No Match Deployments
# In order to use these deployments with Fabrikate, follow the steps below.
# 1. Add the source (git repository link)
# 2. Add a path field (path within the git repository) ex: "path: stable/"
# 3. Specify helm for applications generated using a Helm chart ex: "type: helm"
# Otherwise, comment them out to prevent errors with Fabrikate generation.
# See here for Fabrikate steps: https://github.com/Microsoft/fabrikate
- name: spring-boot-api
  source: <source repository url>
  method: git
- name: spring-boot-ui 
  source: <source repository url>
  method: git

I think this should be sufficient information to help edit the generated component.yaml. What does everyone think?

@mtarng
Copy link

mtarng commented Jul 5, 2019

@andrewDoing not sure if we want to get too far into specifics here, but there's now also resources on how to deploy from private repositories: https://github.com/microsoft/fabrikate/blob/master/docs/auth.md

And you could add a direct link to the Component docs: https://github.com/microsoft/fabrikate/blob/master/docs/component.md

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants