maxmustermann/pulumi
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
pulumi/Makefile

92 lines
5.1 KiB
Makefile
Raw Normal View History

Remove SDK dependencies This change eliminates our dependencies on the SDK repo. Now that SDKs are comprised solely of pulumi/pulumi artifacts, a separate repo isn't required. This allows us to simplify some of the distribution. The install.sh script is modified slightly, to permit overriding the default install location using $PULUMI_INSTALL_PATH.
2018-04-28 22:05:30 +02:00
PROJECT_NAME := Pulumi SDK
Fanout build experiment (#7628) * Experiment with gotestsum and test timings * Fix to locating the helper script * Fix the code for installing gotestsum * Try alternative installation method * Use go to compute test stats; Python fails parsing time values * Try version without v * Try with fixed gorelaser config * Fix test time correlation * Try a stable test stat sort finally * Use more accurate test duration aggregation * Include python and auto-api tests in the Go timing counts * Bring back TESTPARALLELISM * Fix test compilation * Only top 100 slow tests * Try to fracture build matrix to fan out tests * Do not run Publish Test Results on unsuppored Mac * Auto-create test-results-dir * Fix new flaky test by polling for logs * Try to move native tests to their own config * Actually skip * Do not fail on empty test-results folder * Try again * Try once more * Integration test config is the crit path - make it smaller * Squash underutilized test configurations * Remove the test result summary box from PR - counts now incorrec * Remove debugging step
2021-07-27 16:07:15 +02:00
PROJECT_ROOT := $(realpath .)
Add **preview** .NET Core support for pulumi. (#3399)
2019-10-26 01:59:50 +02:00
SUB_PROJECTS := sdk/dotnet sdk/nodejs sdk/python sdk/go
Install GoMetaLinter in Travis And also rejigger the Makefiles to properly error if it's missing.
2017-06-21 23:23:48 +02:00
Fanout build experiment (#7628) * Experiment with gotestsum and test timings * Fix to locating the helper script * Fix the code for installing gotestsum * Try alternative installation method * Use go to compute test stats; Python fails parsing time values * Try version without v * Try with fixed gorelaser config * Fix test time correlation * Try a stable test stat sort finally * Use more accurate test duration aggregation * Include python and auto-api tests in the Go timing counts * Bring back TESTPARALLELISM * Fix test compilation * Only top 100 slow tests * Try to fracture build matrix to fan out tests * Do not run Publish Test Results on unsuppored Mac * Auto-create test-results-dir * Fix new flaky test by polling for logs * Try to move native tests to their own config * Actually skip * Do not fail on empty test-results folder * Try again * Try once more * Integration test config is the crit path - make it smaller * Squash underutilized test configurations * Remove the test result summary box from PR - counts now incorrec * Remove debugging step
2021-07-27 16:07:15 +02:00
include build/common.mk
Fixing up go.mod and go.sum to ensure they don't continually change (#6502)
2021-03-11 21:41:45 +01:00
[breaking] Changing the version of go.mod in sdk / pkg to be v3
2021-03-17 14:20:05 +01:00
PROJECT := github.com/pulumi/pulumi/pkg/v3/cmd/pulumi
Fix tests for clones outside of GOPATH. (#4198) `go list ./foo/...` does not return appropriate package names when this repository is cloned outside GOPATH.
2020-03-26 21:42:43 +01:00
PROJECT_PKGS := $(shell cd ./pkg && go list ./... | grep -v /vendor/)
Fix Makefile (#7485)
2021-07-12 16:42:06 +02:00
TESTS_PKGS := $(shell cd ./tests && go list -tags all ./... | grep -v tests/templates | grep -v /vendor/)
Migrate the version calculation to use pulumictl (#6460)
2021-03-10 20:03:29 +01:00
VERSION := $(shell pulumictl get version)
Sketch a `mu build` command and its scaffolding This adds a bunch of general scaffolding and the beginning of a `build` command. The general engineering scaffolding includes: * Glide for dependency management. * A Makefile that runs govet and golint during builds. * Google's Glog library for logging. * Cobra for command line functionality. The Mu-specific scaffolding includes some packages: * mu/pkg/diag: A package for compiler-like diagnostics. It's fairly barebones at the moment, however we can embellish this over time. * mu/pkg/errors: A package containing Mu's predefined set of errors. * mu/pkg/workspace: A package containing workspace-related convenience helpers. in addition to a main entrypoint that simply wires up and invokes the CLI. From there, the mu/cmd package takes over, with the Cobra-defined CLI commands. Finally, the mu/pkg/compiler package actually implements the compiler behavior. Or, it will. For now, it simply parses a JSON or YAML Mufile into the core mu/pkg/api types, and prints out the result.
2016-11-15 20:30:34 +01:00
Adopt new makefile system See https://github.com/pulumi/home/pull/56 for more details.
2017-11-12 01:20:56 +01:00
TESTPARALLELISM := 10
Install fixed versions of our tools For some tools we used, like `dep` and `gometalinter` we were just calling `go install` which caused us to pick up whatever was in `HEAD` at that time. Now, we move to a model where we install fixed versions, which will change per milestone. While doing this, I changed the way our .travis.yml file runs everything to move as much as possible out into scripts and do so in a way that allows us to share as much common logic across our repositories.
2018-01-24 00:56:58 +01:00
Attempt to avoid triple-building projects in the solution (#7638)
2021-07-29 02:31:11 +02:00
# Motivation: running `make TEST_ALL_DEPS= test_all` permits running
# `test_all` without the dependencies.
TEST_ALL_DEPS = build $(SUB_PROJECTS:%=%_install)
update builds to handle new go mod layout
2020-03-19 00:41:23 +01:00
ensure::
$(call STEP_MESSAGE)
Add that pulumictl is needed to make pulumi (#8196)
2021-10-12 18:51:12 +02:00
@echo "Check for pulumictl"; [ -e "$(shell which pulumictl)" ]
Fixing up go.mod and go.sum to ensure they don't continually change (#6502)
2021-03-11 21:41:45 +01:00
@echo "cd sdk && go mod download"; cd sdk && go mod download
@echo "cd pkg && go mod download"; cd pkg && go mod download
@echo "cd tests && go mod download"; cd tests && go mod download
update builds to handle new go mod layout
2020-03-19 00:41:23 +01:00
Make generate.sh reproducible
2018-07-12 22:29:35 +02:00
build-proto::
cd sdk/proto && ./generate.sh
Update schema-based docs generator (#4035) * Update properties.tmpl to render property comment as-is. WIP splitting out properties to lang-specific tables. * Generate the constructor dynamically from the resource per language. * Add doc functions in each language generator package for getting doc links for types..and later other functions too. * Render the constructor params in the Go code and inject into the template. * Generate nodejs types using the nodejs lang generator. * Add a templates bundler. Added a new Make target for autogenerating a static bundle for the resource docs generator. * Generate type links for all languages based on their schema type. Render the property type with a link if the underlying elements have a supporting type. Fix word-breaks for Python type names. * Various changes including the introduction of an interface type under the codegen package to help with generating some language-specific information for the resource docs generator. * Add a function to explicitly generate links for input types of nested types. Fix the resource doc link generator for Go. Don't replace the module name from the nodejs language type. * Fix bug with C# property type html encoding. * Fix some template formatting. Pass the state inputs for Python to generate the lookup function for it. * Do not generate the examples section if there are none. * Generating the property types per language. * Formatting. Rename function for readability. * Add comments. Update README. * Use relative URLs for doc links within the main site
2020-03-09 18:35:20 +01:00
.PHONY: generate
generate::
$(call STEP_MESSAGE)
[codegen/docs] Use go:embed for templates and use DisplayName from schema for titles (#8389) * Use the display name from the schema, if available * Update comment on the titleLookup map * Add examples of reserved labels that can be used with the Keywords array in the schema
2021-11-10 20:07:43 +01:00
echo "This command does not do anything anymore. It will be removed in a future version."
Update schema-based docs generator (#4035) * Update properties.tmpl to render property comment as-is. WIP splitting out properties to lang-specific tables. * Generate the constructor dynamically from the resource per language. * Add doc functions in each language generator package for getting doc links for types..and later other functions too. * Render the constructor params in the Go code and inject into the template. * Generate nodejs types using the nodejs lang generator. * Add a templates bundler. Added a new Make target for autogenerating a static bundle for the resource docs generator. * Generate type links for all languages based on their schema type. Render the property type with a link if the underlying elements have a supporting type. Fix word-breaks for Python type names. * Various changes including the introduction of an interface type under the codegen package to help with generating some language-specific information for the resource docs generator. * Add a function to explicitly generate links for input types of nested types. Fix the resource doc link generator for Go. Don't replace the module name from the nodejs language type. * Fix bug with C# property type html encoding. * Fix some template formatting. Pass the state inputs for Python to generate the lookup function for it. * Do not generate the examples section if there are none. * Generating the property types per language. * Formatting. Rename function for readability. * Add comments. Update README. * Use relative URLs for doc links within the main site
2020-03-09 18:35:20 +01:00
[codegen/docs] Use go:embed for templates and use DisplayName from schema for titles (#8389) * Use the display name from the schema, if available * Update comment on the titleLookup map * Add examples of reserved labels that can be used with the Keywords array in the schema
2021-11-10 20:07:43 +01:00
build::
[breaking] Changing the version of go.mod in sdk / pkg to be v3
2021-03-17 14:20:05 +01:00
cd pkg && go install -ldflags "-X github.com/pulumi/pulumi/pkg/v3/version.Version=${VERSION}" ${PROJECT}
Clean up the Makefile This adds a bunch of independent targets to the Makefile, to help run individual commands as needed. It also skips running `golint` by default (per golint's advice, actually), because it spews lots of documentation-related things at the moment, which we are intentionally ignoring. (Mainly just hundreds of public members without comments; eventually we'll need to tackle this.)
2017-01-28 00:42:55 +01:00
[codegen/docs] Use go:embed for templates and use DisplayName from schema for titles (#8389) * Use the display name from the schema, if available * Update comment on the titleLookup map * Add examples of reserved labels that can be used with the Keywords array in the schema
2021-11-10 20:07:43 +01:00
build_debug::
[breaking] Changing the version of go.mod in sdk / pkg to be v3
2021-03-17 14:20:05 +01:00
cd pkg && go install -gcflags="all=-N -l" -ldflags "-X github.com/pulumi/pulumi/pkg/v3/version.Version=${VERSION}" ${PROJECT}
Add make target for debug builds (#6001)
2020-12-24 00:10:05 +01:00
Start in on developer documentation. (#7839) Developer documentation is written in Markdown and can be built into HTML, PDF, etc. using Sphinx. Diagrams are written in PlantUML and rendered as SVGs. All developer docs live in the `developer-docs` folder under the root of the repository.
2021-08-26 00:18:13 +02:00
developer_docs::
cd developer-docs && make html
[codegen/docs] Use go:embed for templates and use DisplayName from schema for titles (#8389) * Use the display name from the schema, if available * Update comment on the titleLookup map * Add examples of reserved labels that can be used with the Keywords array in the schema
2021-11-10 20:07:43 +01:00
install::
[breaking] Changing the version of go.mod in sdk / pkg to be v3
2021-03-17 14:20:05 +01:00
cd pkg && GOBIN=$(PULUMI_BIN) go install -ldflags "-X github.com/pulumi/pulumi/pkg/v3/version.Version=${VERSION}" ${PROJECT}
Track resources that are pending deletion in checkpoints. During the course of a `pulumi update`, it is possible for a resource to become slated for deletion. In the case that this deletion is part of a replacement, another resource with the same URN as the to-be-deleted resource will have been created earlier. If the `update` fails after the replacement resource is created but before the original resource has been deleted, the snapshot must capture that the original resource still exists and should be deleted in a future update without losing track of the order in which the deletion must occur relative to other deletes. Currently, we are unable to track this information because the our checkpoints require that no two resources have the same URN. To fix this, these changes introduce to the update engine the notion of a resource that is pending deletion and change checkpoint serialization to use an array of resources rather than a map. The meaning of the former is straightforward: a resource that is pending deletion should be deleted during the next update. This is a fairly major breaking change to our checkpoint files, as the map of resources is no more. Happily, though, it makes our checkpoint files a bit more "obvious" to any tooling that might want to grovel or rewrite them. Fixes #432, #387.
2017-10-05 23:08:35 +02:00
add initial pull-request workflow (#5276) * add initial pull-request workflow * run SDK test all * add SDK tests * fixup make targets * add dist target * revert back to 5 updates * disable test * add issue for test disabling
2020-09-09 22:37:03 +02:00
install_all:: install
Makefile: properly encode dependencies (#4541) This allows for the use of `make -j`, which speeds up a full build dramatically at the cost of rather incomprehensible logs.
2020-05-04 23:26:52 +02:00
dist:: build
[breaking] Changing the version of go.mod in sdk / pkg to be v3
2021-03-17 14:20:05 +01:00
cd pkg && go install -ldflags "-X github.com/pulumi/pulumi/pkg/v3/version.Version=${VERSION}" ${PROJECT}
Added dist target for make, will help with Homebrew (#1731) * Added dist target for make, will help with Homebrew * Try to install go dependencies before building * Make sure dep ensure is called before trying to build SDKs * Removed dep ensure from dist initial step
2018-08-08 22:00:42 +02:00
Add a brew target. This is necessary for the Homebrew build.
2020-05-14 05:27:15 +02:00
# NOTE: the brew target intentionally avoids the dependency on `build`, as it does not require the language SDKs.
Ensure that make brew works as expected rather than passing empty version (#6566) Fixes:#6565 As part of #6460, the logic for determing the version of the build was moved to be a dependency on pulumictl. Unfortunately, the homebrew installs use the "make dist" command to build + install Pulumi to the user maching and as that would have a dependency on pulumictl and it not existing on the user machine, it would pass an empty version to the ldflag This then manifested to the user as: ``` ▶ pulumi version warning: A new version of Pulumi is available. To upgrade from version '0.0.0' to '2.22.0', run $ brew upgrade pulumi or visit https://pulumi.com/docs/reference/install/ for manual instructions and release notes. ``` We are able to mitigate this behaviour by bringing back the get-version script and using that script as part of the make brew installation We can see that the versions are the same between the 2 different installation techniques ``` make dist <------- uses pulumict DIST: go install -ldflags "-X github.com/pulumi/pulumi/sdk/v2/go/common/version.Version=2.24.0-alpha.1616029310+787eb70a" github.com/pulumi/pulumi/sdk/v2/dotnet/cmd/pulumi-language-dotnet DIST: BUILD: ``` ``` make brew <----- uses the legacy script ▶ make brew BREW: go install -ldflags "-X github.com/pulumi/pulumi/sdk/v2/go/common/version.Version=v2.24.0-alpha.1616029310+g787eb70a2" github.com/pulumi/pulumi/sdk/v2/dotnet/cmd/pulumi-language-dotnet BREW: ``` A full post mortem will be carried out to ensure we mitigate these types of errors going forward and that we are able to better test these types of situations
2021-03-18 03:07:02 +01:00
brew:: BREW_VERSION := $(shell scripts/get-version HEAD)
Add a brew target. This is necessary for the Homebrew build.
2020-05-14 05:27:15 +02:00
brew::
[breaking] Changing the version of go.mod in sdk / pkg to be v3
2021-03-17 14:20:05 +01:00
cd pkg && go install -ldflags "-X github.com/pulumi/pulumi/pkg/v3/version.Version=${BREW_VERSION}" ${PROJECT}
Add a brew target. This is necessary for the Homebrew build.
2020-05-14 05:27:15 +02:00
Adopt new makefile system See https://github.com/pulumi/home/pull/56 for more details.
2017-11-12 01:20:56 +01:00
lint::
"make lint" returns an accurate status code
2021-08-25 23:43:50 +02:00
@[ "$(shell cd pkg && golangci-lint run -c ../.golangci.yml --timeout 5m 1>&2; echo $$?)" -eq 0 ] && \
[ "$(shell cd sdk && golangci-lint run -c ../.golangci.yml --timeout 5m 1>&2; echo $$?)" -eq 0 ] && \
[ "$(shell cd tests && golangci-lint run -c ../.golangci.yml --timeout 5m 1>&2; echo $$?)" -eq 0 ]
Clean up the Makefile This adds a bunch of independent targets to the Makefile, to help run individual commands as needed. It also skips running `golint` by default (per golint's advice, actually), because it spews lots of documentation-related things at the moment, which we are intentionally ignoring. (Mainly just hundreds of public members without comments; eventually we'll need to tackle this.)
2017-01-28 00:42:55 +01:00
Makefile: properly encode dependencies (#4541) This allows for the use of `make -j`, which speeds up a full build dramatically at the cost of rather incomprehensible logs.
2020-05-04 23:26:52 +02:00
test_fast:: build
Removing the need for vendoring (#4167)
2020-03-25 23:57:46 +01:00
cd pkg && $(GO_TEST_FAST) ${PROJECT_PKGS}
Make all by default
2017-08-06 17:52:32 +02:00
Attempt to avoid triple-building projects in the solution (#7638)
2021-07-29 02:31:11 +02:00
test_build:: $(TEST_ALL_DEPS)
[sdk/go] Specify known when creating outputs for construct (#7343) If an input is an unknown value or contains unknowns, specify `false` for `known` when creating the output.
2021-06-21 18:51:41 +02:00
cd tests/testprovider && go build -o pulumi-resource-testprovider
Initial support for remote component construction. (#5280) These changes add initial support for the construction of remote components. For now, this support is limited to the NodeJS SDK; follow-up changes will implement support for the other SDKs. Remote components are component resources that are constructed and managed by plugins rather than by Pulumi programs. In this sense, they are a bit like cloud resources, and are supported by the same distribution and plugin loading mechanisms and described by the same schema system. The construction of a remote component is initiated by a `RegisterResourceRequest` with the new `remote` field set to `true`. When the resource monitor receives such a request, it loads the plugin that implements the component resource and calls the `Construct` method added to the resource provider interface as part of these changes. This method accepts the information necessary to construct the component and its children: the component's name, type, resource options, inputs, and input dependencies. It is responsible for dispatching to the appropriate component factory to create the component, then returning its URN, resolved output properties, and output property dependencies. The dependency information is necessary to support features such as delete-before-replace, which rely on precise dependency information for custom resources. These changes also add initial support for more conveniently implementing resource providers in NodeJS. The interface used to implement such a provider is similar to the dynamic provider interface (and may be unified with that interface in the future). An example of a NodeJS program constructing a remote component resource also implemented in NodeJS can be found in `tests/construct_component/nodejs`. This is the core of #2430.
2020-09-08 04:33:55 +02:00
cd tests/integration/construct_component/testcomponent && yarn install && yarn link @pulumi/pulumi && yarn run tsc
Support defining remote components in Go (#6403)
2021-04-16 20:49:21 +02:00
cd tests/integration/construct_component/testcomponent-go && go build -o pulumi-resource-testcomponent
Add output values integration tests (#8421)
2021-11-16 00:42:04 +01:00
cd tests/integration/construct_component_output_values/testcomponent && yarn install && yarn link @pulumi/pulumi && yarn run tsc
cd tests/integration/construct_component_output_values/testcomponent-go && go build -o pulumi-resource-testcomponent
[sdk/nodejs] Fix construct to wait for RPC operations to complete (#6452) This change fixes the provider implementation of `Construct` for multi-lang components written in Node.js to wait for any in-flight RPCs to finish before returning the results, s.t. all registered child resources are created. In additional, invocations of `construct` are now serialized so that each call runs one after another, avoiding concurrent runs, since `construct` modifies global state. We'll follow-up with a more general concurrency fix to allow nested `construct` calls within the same provider.
2021-04-05 20:11:27 +02:00
cd tests/integration/construct_component_slow/testcomponent && yarn install && yarn link @pulumi/pulumi && yarn run tsc
[sdk/nodejs] Keep prompt values prompt in construct (#6522) In order to support prompt values in multi-lang components, if an input value is prompt, keep it as-is instead of wrapping it in an Output.
2021-04-09 23:36:22 +02:00
cd tests/integration/construct_component_plain/testcomponent && yarn install && yarn link @pulumi/pulumi && yarn run tsc
[sdk/go] Support prompt values in `Construct` (#6790) Adds support for prompt values. And renames `ConstructInputs.SetArgs` to `ConstructInputs.CopyTo`.
2021-04-18 18:18:25 +02:00
cd tests/integration/construct_component_plain/testcomponent-go && go build -o pulumi-resource-testcomponent
[sdk/go] Specify known when creating outputs for construct (#7343) If an input is an unknown value or contains unknowns, specify `false` for `known` when creating the output.
2021-06-21 18:51:41 +02:00
cd tests/integration/construct_component_unknown/testcomponent && yarn install && yarn link @pulumi/pulumi && yarn run tsc
cd tests/integration/construct_component_unknown/testcomponent-go && go build -o pulumi-resource-testcomponent
[sdk/nodejs|python] Add GetSchema support to providers (#6892)
2021-05-19 16:11:18 +02:00
cd tests/integration/component_provider_schema/testcomponent && yarn install && yarn link @pulumi/pulumi && yarn run tsc
cd tests/integration/component_provider_schema/testcomponent-go && go build -o pulumi-resource-testcomponent
Fix a hang in nodejs remote components when an error is thrown within an apply (#7365)
2021-06-26 03:41:54 +02:00
cd tests/integration/construct_component_error_apply/testcomponent && yarn install && yarn link @pulumi/pulumi && yarn run tsc
Initial support for resource methods (authoring from Node.js, calling from Python) (#7363) Adds initial support for resource methods (via a new `Call` gRPC method similar to `Invoke`), with support for authoring methods from Node.js, and calling methods from Python.
2021-06-30 16:48:56 +02:00
cd tests/integration/construct_component_methods/testcomponent && yarn install && yarn link @pulumi/pulumi && yarn run tsc
[sdk/go] Support for implementing methods in provider (#7379)
2021-07-02 00:46:16 +02:00
cd tests/integration/construct_component_methods/testcomponent-go && go build -o pulumi-resource-testcomponent
Rehydrate provider resources in `Construct` (#7624) Previously, any provider resource passed to multi-lang components would be instantiated as a `DependencyProviderResource` inside `Construct`, which prevents the component from being able to easily access the provider's state as an instance of of the provider (e.g. `*aws.Provider`). This change attempts to rehydrate the provider resource in the same way that resource references are rehydrated, if it's been registered, s.t. the specific provider resource type is instantiated with its state. Otherwise falling back to returning `DependencyProviderResource`.
2021-07-23 23:10:06 +02:00
cd tests/integration/construct_component_provider/testcomponent && yarn install && yarn link @pulumi/pulumi && yarn run tsc
cd tests/integration/construct_component_provider/testcomponent-go && go build -o pulumi-resource-testcomponent
[sdk/python] Handle unknown results from methods (#7677) This fixes handling of unknown results from methods in the Python SDK. Node.js and Go were already handling this appropriately.
2021-07-29 20:11:52 +02:00
cd tests/integration/construct_component_methods_unknown/testcomponent && yarn install && yarn link @pulumi/pulumi && yarn run tsc
cd tests/integration/construct_component_methods_unknown/testcomponent-go && go build -o pulumi-resource-testcomponent
Add tests that create resources from methods (#7701)
2021-11-15 20:17:53 +01:00
cd tests/integration/construct_component_methods_resources/testcomponent && yarn install && yarn link @pulumi/pulumi && yarn run tsc
cd tests/integration/construct_component_methods_resources/testcomponent-go && go build -o pulumi-resource-testcomponent
Add tests that return failures from Call (#8424) - [sdk/nodejs] - Allow returning failures from Call in the provider without setting result outputs. - [sdk/go] - Allow specifying Call failures from the provider. - Add tests that return failures from Call.
2021-11-16 17:58:46 +01:00
cd tests/integration/construct_component_methods_errors/testcomponent && yarn install && yarn link @pulumi/pulumi && yarn run tsc
cd tests/integration/construct_component_methods_errors/testcomponent-go && go build -o pulumi-resource-testcomponent
Initial support for remote component construction. (#5280) These changes add initial support for the construction of remote components. For now, this support is limited to the NodeJS SDK; follow-up changes will implement support for the other SDKs. Remote components are component resources that are constructed and managed by plugins rather than by Pulumi programs. In this sense, they are a bit like cloud resources, and are supported by the same distribution and plugin loading mechanisms and described by the same schema system. The construction of a remote component is initiated by a `RegisterResourceRequest` with the new `remote` field set to `true`. When the resource monitor receives such a request, it loads the plugin that implements the component resource and calls the `Construct` method added to the resource provider interface as part of these changes. This method accepts the information necessary to construct the component and its children: the component's name, type, resource options, inputs, and input dependencies. It is responsible for dispatching to the appropriate component factory to create the component, then returning its URN, resolved output properties, and output property dependencies. The dependency information is necessary to support features such as delete-before-replace, which rely on precise dependency information for custom resources. These changes also add initial support for more conveniently implementing resource providers in NodeJS. The interface used to implement such a provider is similar to the dynamic provider interface (and may be unified with that interface in the future). An example of a NodeJS program constructing a remote component resource also implemented in NodeJS can be found in `tests/construct_component/nodejs`. This is the core of #2430.
2020-09-08 04:33:55 +02:00
Attempt to avoid triple-building projects in the solution (#7638)
2021-07-29 02:31:11 +02:00
test_all:: test_build
Removing the need for vendoring (#4167)
2020-03-25 23:57:46 +01:00
cd pkg && $(GO_TEST) ${PROJECT_PKGS}
Reduce verbosity on tests
2020-11-12 23:45:06 +01:00
cd tests && $(GO_TEST) -p=1 ${TESTS_PKGS}
Reference in a new issue Copy permalink