I need the Circle CI pipeline that I designed in the present repository: and the Circle CI pipeline has an automatic way to upgrade version of golang, version of all tools used to run commands in the pipline, eg golangci-lintgoreleaser
the generated code is submitter via an automatically created Pull Request:
In that pull request, the Circle CI pipeline will execute tests: build a snapshot of the provider, and runnign the example, against a deployed version of the new release version of the REST API, also running the basic unit tests of the golang code.
the automated code generation is triggered by a new API release event
Well we'll see what we can do there.
Questions to answer:
Should such a code generation process be used only to initiate a source code ?
Should such a code generation process be used only when a minor version change happens in the REST API release? (not for minor updates)?
Should the Circle CI pipeline implementing the code generation be triggered only when we create pull request on a git branch which name matches a given regex, eg regenerate/for/api/<api release version here>/* ?
I wan to try and setup a full tool chain which generates the terraform provider, based on the OpenAPI OAS v3.0:
README.md
of https://github.com/NaverCloudPlatform/terraform-plugin-codegen-openapigolangci-lint
goreleaser
Well we'll see what we can do there.
Questions to answer:
regenerate/for/api/<api release version here>/*
?