Skip to content

Releases: Azure/draft

v0.0.33

08 Aug 20:45
2142dbc
Compare
Choose a tag to compare

Added

  • #220 Update readme for supported flags
  • #219 Retry releases to get tag name
  • #218 Add gradle wrapper detection
  • #217 Add python entrypoint detection
  • #215 Add reporeader interface and an example extractor for python
  • #213 Integration test for multiple OS

Fixed

  • #225 Fix variable substitution in generate-workflow
  • #216 bump rust version to fix e2e

v0.0.32

04 May 17:46
580337c
Compare
Choose a tag to compare

Added

  • #197 Add dry run support to update command
  • #191 Add variable flag to create command

Fixed

  • #196 Update deprecated node12 actions
  • #207 Default deploy variable fixed

Changed

  • #194 Move generate workflow templates to embedded file system

v0.0.31

14 Mar 20:48
ed57224
Compare
Choose a tag to compare

Added

  • #189 Add example package to show consumption patterns

Fixed

  • #190 Add integration test and Dockerfile fix for go language without modules

v0.0.30

24 Feb 21:52
d3a7ef6
Compare
Choose a tag to compare

Changed

  • #187 OpenJDK Docker image has been deprecated and doesnt have JRE images for Java 11+. This change moves our Java images to Eclipse-Temurin.

v0.0.29

16 Feb 17:33
3ce9021
Compare
Choose a tag to compare

Fixed

  • Bug fix for helm deployments where namespace was created but not respected at the deployment level

v0.0.28

14 Feb 21:28
3a9a1b2
Compare
Choose a tag to compare

BREAKING changes to IMAGE variable

Added

  • New, optional disablePrompt property on Builder Variables in draft config (#180):
    • Default Value: false
    • Variables with disablePrompt: true will not be prompted for when running draft interactive commands
    • Variables with disablePrompt: true can 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
        ...
      
  • For all draft substitutions, draft will now error if unsubstituted variables are found in the final output (#175)

Changed

  • BREAKING the IMAGE variable no longer can include an image tag. The TAG variable should be used instead (#176)
  • BREAKING the imageKey variable on the helm deployment type has been renamed to image to be consistent with the supplied starter workflows (#176)
    • Re-running draft create will update existing files to follow the new convention

v0.0.27

09 Dec 20:14
98c4848
Compare
Choose a tag to compare

Added

  • New displayName and variables.exampeValues properties 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-run and --dry-run-file flags to create command
    • --dry-run enables dry run mode in which no files are written to disk, prints the dry run summary to stdout
    • --dry-run-file specifies a file to write the dry run summary in json format (requires --dry-run flag)
    # 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 - info command output format includes additional information for supported languages with the following format changes:
    • keys are now camelCase
    • supportedLanguages is now an array of objects, enriched with displayName and exampleValues
    # 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",
        ...
      ]
    }

v0.0.26

17 Nov 06:18
7a5311e
Compare
Choose a tag to compare

Added

  • The new draft info command from #157 prints supported language and field information in json format.
  • An integration test was added for the installation shell script to better ensure that the script works as expected.

Fixed

  • File path output for root locations had a bug with string-formatted paths. The path.Join method has been substituted to fix this.

Changed

  • Remaining uses of the viper library have been migrated to gopkg.in/yaml.v3 for consistency.
  • Unused files in the web package have been removed.
  • Minor reorganization across the config and addons packages to reduce the number of exported functions and types.

v0.0.25

05 Oct 18:36
eb7e383
Compare
Choose a tag to compare
  • add IMAGENAME and NAMESPACE variables to the deployment to allow deeper customization

    • The NAMESPACE defaults to the default namespace

    • The IMAGENAME defaults to the APPNAME valu e

  • Add new referenceVar field to variableDefaults type

    • The value of the referenceVar input will be copied as the default
    • A referenceVar has higher precedence when defaulting compared to a static variableDefault value field
    • variableDefaults are processed in order, so a variableDefault can only use a referenceVar that is listed before it in the draft.yaml variables
# valid draft.yaml
variables:       # variables are named in the order they will be prompted
  - name: "FIRST"
    description: "the first variable"
  - name: "SECOND"
    description: "the second variable"
variableDefaults:
  - name: "SECOND"       # "default the value of SECOND  to the value of FIRST"
    referenceVar: "FIRST" # valid config since SECOND comes after FIRST in the `variables` section


# INVALID draft.yaml
variables: 
  - name: "FIRST"
    description: "the first variable"
  - name: "SECOND"
    description: "the second variable"
variableDefaults:
  - name: "FIRST"                  # "default the value of FIRST  to the value of SECOND"
    referenceVar: "SECOND" # SECOND will always be empty when FIRST is being prompted, so the default will be the empty string

v0.0.24

28 Sep 19:19
bb19713
Compare
Choose a tag to compare

add --variable flag to draft update command

builderVariables can be supplied to the update command using the new --variable flag
this allows non-interactive use of the update command

added integration tests for update command for webapp_routing addon that creates an ingress using the non-interactive flags mode