@pulumiverse/gandi 0.0.8

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,407 @@
+# Terraform Bridge Provider Boilerplate
+
+This repository contains boilerplate code for building a new Pulumi provider which wraps an existing Terraform provider.  
+
+### Background
+This repository is part of the [guide for authoring and publishing a Pulumi Package](https://www.pulumi.com/docs/guides/pulumi-packages/how-to-author).
+
+Learn about the concepts behind [Pulumi Packages](https://www.pulumi.com/docs/guides/pulumi-packages/#pulumi-packages).
+
+## Creating a Pulumi Terraform Bridge Provider
+
+The following instructions cover:
+- providers maintained by Pulumi (denoted with a "Pulumi Official" checkmark on the Pulumi registry)
+- providers published and maintained by the Pulumi community, referred to as "third-party" providers
+
+We showcase a Pulumi-owned provider based on an upstream provider named `terraform-provider-foo`.  Substitute appropriate values below for your use case.
+
+> Note: If the name of the desired Pulumi provider differs from the name of the Terraform provider, you will need to carefully distinguish between the references - see <https://github.com/pulumi/pulumi-azure> for an example.
+
+### Prerequisites
+
+Ensure the following tools are installed and present in your `$PATH`:
+
+* [`pulumictl`](https://github.com/pulumi/pulumictl#installation)
+* [Go 1.17](https://golang.org/dl/) or 1.latest
+* [NodeJS](https://nodejs.org/en/) 14.x.  We recommend using [nvm](https://github.com/nvm-sh/nvm) to manage NodeJS installations.
+* [Yarn](https://yarnpkg.com/)
+* [TypeScript](https://www.typescriptlang.org/)
+* [Python](https://www.python.org/downloads/) (called as `python3`).  For recent versions of MacOS, the system-installed version is fine.
+* [.NET](https://dotnet.microsoft.com/download)
+
+### Creating and Initializing the Repository
+
+Pulumi offers this repository as a [GitHub template repository](https://docs.github.com/en/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template) for convenience.  From this repository:
+
+1. Click "Use this template".
+1. Set the following options:
+    * Owner: pulumi (third-party: your GitHub organization/username)
+    * Repository name: pulumi-foo (third-party: preface your repo name with "pulumi" as standard practice)
+    * Description: Pulumi provider for Foo
+    * Repository type: Public
+1. Clone the generated repository.
+
+From the templated repository:
+
+1. Run the following command to update files to use the name of your provider (third-party: use your GitHub organization/username):
+
+    ```bash
+    make prepare NAME=foo REPOSITORY=github.com/pulumi/pulumi-foo
+    ```
+
+   This will do the following:
+   - rename folders in `provider/cmd` to `pulumi-resource-foo` and `pulumi-tfgen-foo`
+   - replace dependencies in `provider/go.mod` to reflect your repository name
+   - find and replace all instances of the boilerplate `gandi` with the `NAME` of your provider.
+
+   Note for third-party providers:
+   - Make sure to set the correct GitHub organization/username in all files referencing your provider as a dependency:
+     - `examples/go.mod`
+     - `provider/resources.go`
+     - `sdk/go.mod`
+     - `provider/cmd/pulumi-resource-foo/main.go`
+     - `provider/cmd/pulumi-tfgen-foo/main.go`
+
+2. Modify `README-PROVIDER.md` to include the following (we'll rename it to `README.md` toward the end of this guide):
+    * Any desired build status badges.
+    * An introductory paragraph describing the type of resources the provider manages, e.g. "The Foo provider for Pulumi manages resources for [Foo](http://example.com/).
+    * In the "Installing" section, correct package names for the various SDK libraries in the languages Pulumi supports.
+    * In the "Configuration" section, any configurable options for the provider.  These may include, but are not limited to, environment variables or options that can be set via [`pulumi config set`](https://www.pulumi.com/docs/reference/cli/pulumi_config_set/).
+    * In the "Reference" section, provide a link to the to-be-published documentation.
+    * Feel free to refer to [the Pulumi AWS provider README](https://github.com/pulumi/pulumi-aws) as an example.
+
+### Composing the Provider Code - Prerequisites
+
+Pulumi provider repositories have the following general structure:
+
+* `examples/` contains sample code which may optionally be included as integration tests to be run as part of a CI/CD pipeline.
+* `provider/` contains the Go code used to create the provider as well as generate the SDKs in the various languages that Pulumi supports.
+  * `provider/cmd/pulumi-tfgen-foo` generates the Pulumi resource schema (`schema.json`), based on the Terraform provider's resources.
+  * `provider/cmd/pulumi-resource-foo` generates the SDKs in all supported languages from the schema, placing them in the `sdk/` folder.
+  * `provider/pkg/resources.go` is the location where we will define the Terraform-to-Pulumi mappings for resources.
+* `sdk/` contains the generated SDK code for each of the language platforms that Pulumi supports, with each supported platform in a separate subfolder.
+
+1. In `provider/go.mod`, add a reference to the upstream Terraform provider in the `require` section, e.g.
+
+    ```go
+    github.com/foo/terraform-provider-foo v0.4.0
+    ```
+
+1. In `provider/resources.go`, ensure the reference in the `import` section uses the correct Go module path, e.g.:
+
+    ```go
+    github.com/foo/terraform-provider-foo/foo
+    ```
+
+1. Download the dependencies:
+
+    ```bash
+    cd provider && go mod tidy && cd -
+    ```
+
+1. Create the schema by running the following command:
+
+    ```bash
+    make tfgen
+    ```
+
+    Note warnings about unmapped resources and data sources in the command's output.  We map these in the next section, e.g.:
+
+    ```text
+    warning: resource foo_something not found in provider map; skipping
+    warning: resource foo_something_else not found in provider map; skipping
+    warning: data source foo_something not found in provider map; skipping
+    warning: data source foo_something_else not found in provider map; skipping
+    ```
+
+## Adding Mappings, Building the Provider and SDKs
+
+In this section we will add the mappings that allow the interoperation between the Pulumi provider and the Terraform provider.  Terraform resources map to an identically named concept in Pulumi.  Terraform data sources map to plain old functions in your supported programming language of choice.  Pulumi also allows provider functions and resources to be grouped into _namespaces_ to improve the cohesion of a provider's code, thereby making it easier for developers to use.  If your provider has a large number of resources, consider using namespaces to improve usability.
+
+The following instructions all pertain to `provider/resources.go`, in the section of the code where we construct a `tfbridge.ProviderInfo` object:
+
+1. **Add resource mappings:** For each resource in the provider, add an entry in the `Resources` property of the `tfbridge.ProviderInfo`, e.g.:
+
+    ```go
+    // Most providers will have all resources (and data sources) in the main module.
+    // Note the mapping from snake_case HCL naming conventions to UpperCamelCase Pulumi SDK naming conventions.
+    // The name of the provider is omitted from the mapped name due to the presence of namespaces in all supported Pulumi languages.
+    "foo_something":      {Tok: tfbridge.MakeResource(mainPkg, mainMod, "Something")},
+    "foo_something_else": {Tok: tfbridge.MakeResource(mainPkg, mainMod, "SomethingElse")},
+    ```
+
+1. **Add CSharpName (if necessary):** Dotnet does not allow for fields named the same as the enclosing type, which sometimes results in errors during the dotnet SDK build.
+    If you see something like
+    ```text
+    error CS0542: 'ApiKey': member names cannot be the same as their enclosing type [/Users/guin/go/src/github.com/pulumi/pulumi-artifactory/sdk/dotnet/Pulumi.Artifactory.csproj]
+    ```
+    you'll want to give your Resource a CSharpName, which can have any value that makes sense:
+
+    ```go
+    "foo_something_dotnet": {
+        Tok: tfbridge.MakeResource(mainPkg, mainMod, "SomethingDotnet"),
+        Fields: map[string]*tfbridge.SchemaInfo{
+            "something_dotnet": {
+                CSharpName: "SpecialName",
+            },
+        },
+    },
+    ```
+
+   [See the underlying terraform-bridge code here.](https://github.com/pulumi/pulumi-terraform-bridge/blob/master/pkg/tfbridge/info.go#L168)
+1. **Add data source mappings:** For each data source in the provider, add an entry in the `DataSources` property of the `tfbridge.ProviderInfo`, e.g.:
+
+    ```go
+    // Note the 'get' prefix for data sources
+    "foo_something":      {Tok: tfbridge.MakeDataSource(mainPkg, mainMod, "getSomething")},
+    "foo_something_else": {Tok: tfbridge.MakeDataSource(mainPkg, mainMod, "getSomethingElse")},
+    ```
+
+1. **Add documentation mapping (sometimes needed):**  If the upstream provider's repo is not a part of the `terraform-providers` GitHub organization, specify the `GitHubOrg` property of `tfbridge.ProviderInfo` to ensure that documentation is picked up by the codegen process, and that attribution for the upstream provider is correct, e.g.:
+
+    ```go
+    GitHubOrg: "foo",
+    ```
+
+1. **Add provider configuration overrides (not typically needed):** Pulumi's Terraform bridge automatically detects configuration options for the upstream provider.  However, in rare cases these settings may need to be overridden, e.g. if we want to change an environment variable default from `API_KEY` to `FOO_API_KEY`.  Examples of common uses cases:
+
+    ```go
+    "additional_required_parameter": {},
+    "additional_optional_string_parameter": {
+        Default: &tfbridge.DefaultInfo{
+            Value: "default_value",
+        },
+    "additional_optional_boolean_parameter": {
+        Default: &tfbridge.DefaultInfo{
+            Value: true,
+        },
+    // Renamed environment variables can be accounted for like so:
+    "apikey": {
+        Default: &tfbridge.DefaultInfo{
+            EnvVars: []string{"FOO_API_KEY"},
+        },
+    ```
+
+1. Build the provider binary and ensure there are no warnings about unmapped resources and no warnings about unmapped data sources:
+
+    ```bash
+    make provider
+    ```
+
+    You may see warnings about documentation and examples, including "unexpected code snippets".  These can be safely ignored for now.  Pulumi will add additional documentation on mapping docs in a future revision of this guide.
+
+1. Build the SDKs in the various languages Pulumi supports:
+
+    ```bash
+    make build_sdks
+    ```
+
+1. Ensure the Golang SDK is a proper go module:
+
+    ```bash
+    cd sdk && go mod tidy && cd -
+    ```
+
+    This will pull in the correct dependencies in `sdk/go.mod` as well as setting the dependency tree in `sdk/go.sum`.
+
+1. Finally, ensure the provider code conforms to Go standards:
+
+    ```bash
+    make lint_provider
+    ```
+
+    Fix any issues found by the linter.
+
+**Note:** If you make revisions to code in `resources.go`, you must re-run the `make tfgen` target to regenerate the schema.
+The `make tfgen` target will take the file `schema.json` and serialize it to a byte array so that it can be included in the build output.
+(This is a holdover from Go 1.16, which does not have the ability to directly embed text files. We are working on removing the need for this step.)
+
+## Sample Program
+
+In this section, we will create a Pulumi program in TypeScript that utilizes the provider we created to ensure everything is working properly.
+
+1. Create an account with the provider's service and generate any necessary credentials, e.g. API keys.
+    * Email: bot@pulumi.com
+    * Password: (Create a random password in 1Password with the  maximum length and complexity allowed by the provider.)
+    * Ensure all secrets (passwords, generated API keys) are stored in Pulumi's 1Password vault.
+
+1. Copy the `pulumi-resource-foo` binary generated by `make provider` and place it in your `$PATH` (`$GOPATH/bin` is a convenient choice), e.g.:
+
+    ```bash
+    cp bin/pulumi-resource-foo $GOPATH/bin
+    ```
+
+1. Tell Yarn to use your local copy of the SDK:
+
+    ```bash
+    make install_nodejs_sdk
+    ```
+
+1. Create a new Pulumi program in the `examples/` directory, e.g.:
+
+    ```bash
+    mkdir examples/my-example/ts # Change "my-example" to something more meaningful.
+    cd examples/my-example/ts
+    pulumi new typescript
+    # (Go through the prompts with the default values)
+    npm install
+    yarn link @pulumi/foo
+    ```
+
+1. Create a minimal program for the provider, i.e. one that creates the smallest-footprint resource.  Place this code in `index.ts`.
+1. Configure any necessary environment variables for authentication, e.g `$FOO_USERNAME`, `$FOO_TOKEN`, in your local environment.
+1. Ensure the program runs successfully via `pulumi up`.
+1. Once the program completes successfully, verify the resource was created in the provider's UI.
+1. Destroy any resources created by the program via `pulumi destroy`.
+
+Optionally, you may create additional examples for SDKs in other languages supported by Pulumi:
+
+1. Python:
+
+    ```bash
+    mkdir examples/my-example/py
+    cd examples/my-example/py
+    pulumi new python
+    # (Go through the prompts with the default values)
+    source venv/bin/activate # use the virtual Python env that Pulumi sets up for you
+    pip install pulumi_foo
+    ```
+
+1. Follow the steps above to verify the program runs successfully.
+
+## Add End-to-end Testing
+
+We can run integration tests on our examples using the `*_test.go` files in the `examples/` folder.
+
+1. Add code to `examples_nodejs_test.go` to call the example you created, e.g.:
+
+    ```go
+    // Swap out MyExample and "my-example" below with the name of your integration test.
+    func TestAccMyExampleTs(t *testing.T) {
+        test := getJSBaseOptions(t).
+            With(integration.ProgramTestOptions{
+                Dir: filepath.Join(getCwd(t), "my-example", "ts"),
+            })
+        integration.ProgramTest(t, &test)
+    }
+    ```
+
+1. Add a similar function for each example that you want to run in an integration test.  For examples written in other languages, create similar files for `examples_${LANGUAGE}_test.go`.
+
+1. You can run these tests locally via Make:
+
+    ```bash
+    make test
+    ```
+
+    You can also run each test file separately via test tags:
+
+    ```bash
+    cd examples && go test -v -tags=nodejs
+    ```
+
+## Configuring CI with GitHub Actions
+
+### Third-party providers
+
+1. Follow the instructions laid out in the [deployment templates](./deployment-templates/README-DEPLOYMENT.md).
+
+### Pulumi Internal
+
+In this section, we'll add the necessary configuration to work with GitHub Actions for Pulumi's standard CI/CD workflows for providers.
+
+1. Generate GitHub workflows per [the instructions in the ci-mgmt repository](https://github.com/pulumi/ci-mgmt/) and copy to `.github/` in this repository.
+
+1. Ensure that any required secrets are present as repository-level [secrets](https://docs.github.com/en/actions/security-guides/encrypted-secrets) in GitHub.  These will be used by the integration tests during the CI/CD process.
+
+1. Repository settings: Toggle `Allow auto-merge` on in your provider repo to automate GitHub Actions workflow updates.
+
+## Final Steps
+
+1. Ensure all required configurations (API keys, etc.) are documented in README-PROVIDER.md.
+
+1. Replace this file with the README for the provider and push your changes:
+
+    ```bash
+    mv README-PROVIDER.md README.md
+    ```
+
+1. If publishing the npm package fails during the "Publish SDKs" Action, perform the following steps:
+    1. Go to [NPM Packages](https://www.npmjs.com/) and sign in as pulumi-bot.
+    1. Click on the bot's profile pic and navigate to "Packages".
+    1. On the left, under "Organizations, click on the Pulumi organization.
+    1. On the last page of the listed packages, you should see the new package.
+    1. Under "Settings", set the Package Status to "public".
+
+Now you are ready to use the provider, cut releases, and have some well-deserved :ice_cream:!
+
+
+## Building the Provider Locally
+
+There are 2 ways the provider can be built locally:
+
+`make provider` will use the current operating system and architecture to create a binary that can be used on your PATH.
+
+To build the provider for another set of operating systems / architectures, the project uses [goreleaser](https://goreleaser.com/).
+Goreleaser, a CLI tool, that allows a user to build a matrix of binaries.
+
+Create a `.goreleaser.yml` file in the root of your project:
+```
+archives:
+- id: archive
+  name_template: "{{ .Binary }}-{{ .Tag }}-{{ .Os }}-{{ .Arch }}"
+before:
+  hooks:
+  - make tfgen
+builds:
+- binary: pulumi-resource-gandi
+  dir: provider
+  goarch:
+  - amd64
+  - arm64
+  goos:
+  - darwin
+  - windows
+  - linux
+  ignore: []
+  ldflags:
+  - -X github.com/pulumiverse/pulumi-gandi/provider/pkg/version.Version={{.Tag}}
+  main: ./cmd/pulumi-resource-gandi/
+  sort: asc
+  use: git
+release:
+  disable: false
+snapshot:
+  name_template: "{{ .Tag }}-SNAPSHOT"
+```
+
+To build the provider for the combination of architectures and operating systems, you can run the following CLI command:
+
+```bash
+goreleaser build --rm-dist --skip-validate
+```
+
+That will ensure that a list of binaries are available to use:
+
+```
+▶ tree dist
+dist
+├── CHANGELOG.md
+├── artifacts.json
+├── config.yaml
+├── metadata.json
+├── pulumi-gandi_darwin_amd64_v1
+│   └── pulumi-resource-gandi
+├── pulumi-gandi_darwin_arm64
+│   └── pulumi-resource-gandi
+├── pulumi-gandi_linux_amd64_v1
+│   └── pulumi-resource-gandi
+├── pulumi-gandi_linux_arm64
+│   └── pulumi-resource-gandi
+├── pulumi-gandi_windows_amd64_v1
+│   └── pulumi-resource-gandi.exe
+└── pulumi-gandi_windows_arm64
+    └── pulumi-resource-gandi.exe
+```
+
+Any of the provider binaries can be used to target the correct machine architecture

package/config/index.d.ts

@@ -0,0 +1 @@
+export * from "./vars";

package/config/index.js

@@ -0,0 +1,21 @@
+"use strict";
+// *** WARNING: this file was generated by the Pulumi Terraform Bridge (tfgen) Tool. ***
+// *** Do not edit by hand unless you're certain you know what you are doing! ***
+var __createBinding = (this && this.__createBinding) || (Object.create ? (function(o, m, k, k2) {
+    if (k2 === undefined) k2 = k;
+    var desc = Object.getOwnPropertyDescriptor(m, k);
+    if (!desc || ("get" in desc ? !m.__esModule : desc.writable || desc.configurable)) {
+      desc = { enumerable: true, get: function() { return m[k]; } };
+    }
+    Object.defineProperty(o, k2, desc);
+}) : (function(o, m, k, k2) {
+    if (k2 === undefined) k2 = k;
+    o[k2] = m[k];
+}));
+var __exportStar = (this && this.__exportStar) || function(m, exports) {
+    for (var p in m) if (p !== "default" && !Object.prototype.hasOwnProperty.call(exports, p)) __createBinding(exports, m, p);
+};
+Object.defineProperty(exports, "__esModule", { value: true });
+// Export members:
+__exportStar(require("./vars"), exports);
+//# sourceMappingURL=index.js.map

package/config/index.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../config/index.ts"],"names":[],"mappings":";AAAA,wFAAwF;AACxF,iFAAiF;;;;;;;;;;;;;;;;AAEjF,kBAAkB;AAClB,yCAAuB"}

package/config/vars.d.ts

@@ -0,0 +1,16 @@
+/**
+ * Prevent the Domain provider from taking certain actions
+ */
+export declare const dryRun: boolean | undefined;
+/**
+ * A Gandi API key
+ */
+export declare const key: string | undefined;
+/**
+ * A Gandi Sharing ID
+ */
+export declare const sharingId: string | undefined;
+/**
+ * The Gandi API URL
+ */
+export declare const url: string | undefined;