Skip to content
Extension for AutoRest ( that generates Go code
Go C# HTML Other
Branch: master
Clone or download
jhendrixMSFT Treat inclusiveMinimum as an int64 (#183)
Apply fix from PR#134 to inclusiveMinimum
Latest commit 4842cb4 Dec 3, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
.gulp Add support for collection format 'multi' (#178) Sep 7, 2019
.vscode initial (#1) Aug 25, 2017
autorest.common @ 04b5593 Support generation of go.mod files (#172) May 15, 2019
src Treat inclusiveMinimum as an int64 (#183) Dec 3, 2019
test/src/tests Treat inclusiveMinimum as an int64 (#183) Dec 3, 2019
.gitignore Support generation of go.mod files (#172) May 15, 2019
.gitmodules Use AutoRest.common as a submodule (#135) Jun 20, 2018
.npmignore Publish With Yarn (#20) Sep 23, 2017
.travis.yml Support generation of go.mod files (#172) May 15, 2019
LICENSE Initial commit Aug 14, 2017 Use AutoRest.common as a submodule (#135) Jun 20, 2018
autorest.go.sln Ensure client parameters match their definition (#140) Jul 13, 2018
gulpfile.js initial (#1) Aug 25, 2017


If you're reading this, you've likely noticed that this repository hasn't enabled issues. That isn't because we don't want your feedback! Please file issues for the repository in one of the following repositories as appropriate:

  • Azure/azure-sdk-for-go : When you're experiencing trouble with the Go SDK, but not with other languages, this is the repository to report bugs to. i.e. What we generate for Long Running Operations doesn't make sense or there's something hard coded that shouldn't be.
  • Azure/go-autorest : File bugs here when your troubles aren't related to a particular operation, or even the pattern of generation, but the core infrastructure that we use to build HTTP request or authenticate. i.e. Retry or Authentication aren't working the way you wanted.
  • Azure/autorest : Should you run into duplicated types, or fundamentally flawed enums, and it seems consistent across languages, but doesn't seem like the problems lies with the actual Azure Service, the problem could lie with how we're modeling the problem as we see it in the Open API Spec. File bugs matching this description to our parent project, "Autorest".
  • Azure/azure-rest-api-specs : If you're getting an error message from the service, saying that it requires a different set of parameters, or you're targeting the wrong endpoint, the problem is likely with the Azure OpenAPI Specs repository. i.e. It seems like the service isn't acurately described.


This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact with any additional questions or comments.


This project uses a git submodule for dependent code. When cloning this repository use git clone --recursive ... or perform a git submodule init after the project is cloned.

AutoRest extension configuration

  "": "2.3.38"

    input: openapi-document/identity
    output-artifact: code-model-v1
    scope: go
    input: imodeler1
    output-artifact: code-model-v1
    input: commonmarker
    output-artifact: code-model-v1
    input: transform
    scope: scope-cm/emitter
    plugin: go
    input: cm/transform
    output-artifact: source-file-go
    input: generate
    output-artifact: source-file-go
    scope: scope-transform-string
    input: transform
    scope: scope-go/emitter

  input-artifact: source-file-go
  output-uri-expr: $key

- source-file-go
You can’t perform that action at this time.