You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 22, 2024. It is now read-only.
# 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-apisource: <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?
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
Information that the user must provide
User Steps
The text was updated successfully, but these errors were encountered: