Releases: microsoft/fabrikate
1.0.0-alpha.1
1.0.0-alpha0
1.0.0-alpha0 is our first prerelease Fabrikate version with support for Helm 3:
0.17.3
0.17.2
2a5db99 Remove overly strict validations and update azure-pipelines.yml (#278)
a889fc1 Handle helm repo aliases (#274)
Fixes
- Fixes issue with component validations being too strict and outputting a error similar to:
unable to stat component.yaml for 'local' component '<some-component-name>' in path '<some/path>'
0.17.0
f0bf9b1 Added the --version option to the Add
command (#276)
85a7085 Preserve manifest ordering when injecting namespace (#273)
fbe8b15 Can specify remote components in root component (non subcomponent)
5d081a3 Leverage Existing Helm Repo (#260)
41cb60f Fix method: git
for non type: component
(#271)
abb92a9 Update Slack link (#269)
Notable Changes
Leveraging Existing Helm Repos
If a component of type: helm
and method: helm
has a source
of a helm
repository already present in your helm client, the existing helm entry is used
and a temporary one is not added. This adds the ability to use the existing auth
mechanisms built into helm.
Special thanks to @runyontr for the work on this
Minor Changes
--version
is now specifiable viafab add
Fixes
- Slack link fixed in docs
- Fixed an issue where
Install()
was skipping for components oftype: helm
andmethod: git
- Ordering of outputted manifests is now maintained when
injectNamespace
is
set for a component
0.16.2
0.16.1
be49c36 bump version number 0.16.1 (#258)
b5f6d76 Fixed permission denied
regression (#257)
Fixes
b5f6d76 - Addresses a long standing issue which we had a troubles finding a reproduction case for. This issue caused users who called fab install
multiple times on the same project to get Error: open <some_file>: permission denied
error. We have resolved this issue by deleting the directory which components and helm charts are installed into prior to install
.
Special thanks to @timfpark for finding a reproduction case as well as @maarek and @smartpcr for their input on resolving this issue.
0.16.0
257d8da Version bump to 0.16.0 (#255)
f9f4bb5 #249 Support remote urls for static components (#254)
542fcda log to stdout by default (#252)
14088b1 #132 Finding Fabrikate components is too hard (#250)
c3d4cdb Add instructions on how to debug fabrikate (#248)
56d5968 Add error handling for bad directory (#247)
a2a946d Release 0.15.3 (#244)
11e4ebc Pass component version field to helm fetch
(#245)
Notable Changes
method: http
Users can now specify method: http
and type: static
for a component if they wish to point directly to YAML manifest hosted on an external URL. For example, to install the Elasticsearch all-in-one deployment:
name: my-component
method: http
type: static
source: https://download.elastic.co/downloads/eck/0.9.0/all-in-one.yaml
fabrikate find
The fabrikate find
function has been added which takes in a single argument and searches the Fabrikate Definitions repository for components that match it.
Example:
$ fabrikate find istio
Search results for 'istio':
fabrikate-istio
fabrikate-cloud-native
fabrikate-bookinfo
fabrikate-jaeger
Correct logging outputs
Due to some limitation of the Logrus library we use for logging, all logging was being piped to stderr
no matter the level. We have added a service layer on top of it to output Debug
, Trace
, Info
, and Warning
to stdout
, and push Error
and Panic
to stderr
.
More concise error handling
Better error messaging is now presented for local static components which point to a non existent directory.
Special Thanks
Thanks to @shubham1172, @basvandenbrink, and @edaena for their bug reports and PR's for this release!
0.15.3
ac02389 Fix: Differentiate between failures to load config file not existing vs. parse errors (#242 )
6ab2287 Fix: Remove branch
configuration when method
!= git in Add() (#235)
This release primary fixes a bug where a config or component parse error was incorrectly interpreted as the configuration for component file not existing. It also correctly ignores branch configuration if the method being used to fetch is not git
.
0.15.2
bd531d7 version bump to 0.15.2 (#234)
75ab3df Fix: Warning messages from helm template break NS injection (#233)
This release fixes a bug where helm template
would inline warning messages (as a raw string) into the outputted k8s manifests, which would cause fab functionality such as namespace injection to fail for that manifest (as it is not a map[string]interface{}
). Non-map entries such as these that are outputted from helm template
are now extracted from the manifest and outputted as warnings to stdout.