Releases: Azure/draft
Releases · Azure/draft
v0.0.36
Added
- #342 Added k8s/deploy Inputs for Private Cluster Support
- #337 azure pipelines generation support
- #334 template support for private clusters
- #324 workflow template enhancements
- #321 add helm rendering function
- #315 adding logic for generating default app name
Fixed
- #320 Workflows are now generated fully from a draftConfig
v0.0.35
v0.0.34
Added
- #277 Updates/Fixes for draft. Adds generator label to manifests
- #275 Add NOTICE file
- #274 gomodule multistage build
- #273 finishing safeguard additions
- #272 sdk calls for assignsprole
- #271 update draft to go 1.22
- #269 yaml file extension validation
- #262 sdk calls for getTenantID
- #242 changes in correlation with new GH action permission changes
v0.0.33
v0.0.32
v0.0.31
v0.0.30
v0.0.29
Fixed
- Bug fix for helm deployments where namespace was created but not respected at the deployment level
v0.0.28
BREAKING changes to IMAGE variable
Added
- New, optional
disablePromptproperty on Builder Variables in draft config (#180):- Default Value:
false - Variables with
disablePrompt: truewill not be prompted for when runningdraft interactive commands - Variables with
disablePrompt: truecan still be supplied via flags (draft create --var TAG=latest) or draft config files - Example Usage:
# draft.yaml variables: - name: "TAG" description: "the tag of the image to be built" disablePrompt: true # New optional field that is used to disable the prompt for this variable ...
- Default Value:
- For all draft substitutions, draft will now error if unsubstituted variables are found in the final output (#175)
Changed
- BREAKING the
IMAGEvariable no longer can include an image tag. TheTAGvariable should be used instead (#176) - BREAKING the
imageKeyvariable on thehelmdeployment type has been renamed toimageto be consistent with the supplied starter workflows (#176)- Re-running
draft createwill update existing files to follow the new convention
- Re-running
v0.0.27
Added
- New
displayNameandvariables.exampeValuesproperties in draft.yaml# draft.yaml language: swift displayName: Swift # Add a display name for the selected resource (language/deploymentType/addon) variables: - name: "VERSION" description: "the version of swift used by the application" exampleValues: ["5.5","5.4"] # New optional field that is used to populate draft info, and which could be used in the cli for suggestions in the future. variableDefaults: - name: "VERSION" value: 5.5
- Added
--dry-runand--dry-run-fileflags tocreatecommand--dry-runenables dry run mode in which no files are written to disk, prints the dry run summary to stdout--dry-run-filespecifies a file to write the dry run summary in json format (requires--dry-runflag)
# Example dry run output { "variables": { "APPNAME": "testapp", "BUILDERVERSION": "null", "IMAGENAME": "testapp", "LANGUAGE": "gomodule", # Note that this variable is in addition to the draft config variables "NAMESPACE": "default", "PORT": "1323", "SERVICEPORT": "80", "VERSION": "1.18" }, "filesToWrite": [ "langtest/.dockerignore", "langtest/Dockerfile", "langtest/charts/.helmignore", "langtest/charts/Chart.yaml", "langtest/charts/production.yaml", "langtest/charts/templates/_helpers.tpl", "langtest/charts/templates/deployment.yaml", "langtest/charts/templates/namespace.yaml", "langtest/charts/templates/service.yaml", "langtest/charts/values.yaml" ] }
Changed
- BREAKING -
infocommand output format includes additional information for supported languages with the following format changes:- keys are now camelCase
supportedLanguagesis now an array of objects, enriched withdisplayNameandexampleValues
# Example of the new info command output format { # keys are now camelCase, so supported_languages is now supportedLanguages "supportedLanguages": [ { "name": "javascript", "displayName": "JavaScript", # new field "exampleValues": { # new field "VERSION": [ "14.0", "16.0" ] } }, ... ], # keys are now camelCase, so supported_deployment_types is now supportedDeploymentTypes "supportedDeploymentTypes": [ "helm", ... ] }