pulumi-dokploy

18 Commits 1 Branch 2 Tags

3 Commits

Include renames

Author	SHA1	Message	Date
max-voitcov	466e162efe	Keep the schema check honest across a version bump build / build (push) Successful in 10m48s Details The build job regenerates schema.json and diffs it against the checked-in copy, to catch a resources.go edit that never got a `make tfgen`. The comment above it claimed the schema carries no version. It does: tfgen writes the upstream version into `packageDescription`. So the job, which builds at the Makefile's default VERSION, regenerated a schema stamped v0.1.0 and diffed it against the committed v0.2.0 one. The v0.2.0 push failed on a mismatch that had nothing to do with the mapping. Bump the default to match the committed schema and say plainly in both places that the two move together. Verified by running the job's exact command -- `make provider` with no override, then the diff -- which now exits 0. The release job was unaffected: it derives VERSION from the tag.	2026-08-26 01:32:04 +03:00
usr_unknown	ad3e908c98	Fix the upstream checkout and skip the dead cache server build / build (push) Failing after 49s Details Two separate CI failures: - The cross-repo checkout of terraform-provider-dokploy asked the API for the default branch and got "not found", failing the build. An explicit ref: main skips the lookup entirely. - setup-go caches by default, and this runner's cache server is unreachable from job containers, so restore and save each block until they time out. The same change cut the upstream provider's build from 15m46s to 2m37s.	2026-08-09 14:00:20 +03:00
usr_unknown	a44ebd4432	Resolve the plugin and SDKs from Gitea build / build (push) Has been cancelled Details release / plugin (push) Failing after 3m46s Details release / sdks (push) Has been skipped Details PluginDownloadURL moves off github:// to a templated Gitea release URL. Pulumi interpolates ${VERSION}, then appends pulumi-resource-dokploy-v<version>-<os>-<arch>.tar.gz -- which is what the GoReleaser archive template already produces. Schema, bridge metadata and all four SDKs regenerated to carry it. Releases publish to this instance's npm, PyPI, NuGet and Go registries using the GITEA_TOKEN that Gitea injects, so no secrets need configuring. The Go SDK keeps its github.com module path, which is exactly why it goes to Gitea's Go registry: pointing GOPROXY there is what makes that path resolve at all. Verified locally by serving the module zip from a file proxy and building a consumer against it -- note zip -D, without which go get rejects the archive's directory entries.	2026-08-09 12:37:19 +03:00

Author

SHA1

Message

Date

max-voitcov

466e162efe

Keep the schema check honest across a version bump

build / build (push) Successful in 10m48s

Details

The build job regenerates schema.json and diffs it against the checked-in
copy, to catch a resources.go edit that never got a `make tfgen`. The comment
above it claimed the schema carries no version. It does: tfgen writes the
upstream version into `packageDescription`.

So the job, which builds at the Makefile's default VERSION, regenerated a
schema stamped v0.1.0 and diffed it against the committed v0.2.0 one. The
v0.2.0 push failed on a mismatch that had nothing to do with the mapping.

Bump the default to match the committed schema and say plainly in both places
that the two move together. Verified by running the job's exact command --
`make provider` with no override, then the diff -- which now exits 0.

The release job was unaffected: it derives VERSION from the tag.

2026-08-26 01:32:04 +03:00

usr_unknown

ad3e908c98

Fix the upstream checkout and skip the dead cache server

build / build (push) Failing after 49s

Details

Two separate CI failures:

- The cross-repo checkout of terraform-provider-dokploy asked the API
  for the default branch and got "not found", failing the build. An
  explicit ref: main skips the lookup entirely.
- setup-go caches by default, and this runner's cache server is
  unreachable from job containers, so restore and save each block until
  they time out. The same change cut the upstream provider's build from
  15m46s to 2m37s.

2026-08-09 14:00:20 +03:00

usr_unknown

a44ebd4432

Resolve the plugin and SDKs from Gitea

build / build (push) Has been cancelled

Details

release / plugin (push) Failing after 3m46s

Details

release / sdks (push) Has been skipped

Details

PluginDownloadURL moves off github:// to a templated Gitea release URL.
Pulumi interpolates ${VERSION}, then appends
pulumi-resource-dokploy-v<version>-<os>-<arch>.tar.gz -- which is what
the GoReleaser archive template already produces. Schema, bridge
metadata and all four SDKs regenerated to carry it.

Releases publish to this instance's npm, PyPI, NuGet and Go registries
using the GITEA_TOKEN that Gitea injects, so no secrets need
configuring.

The Go SDK keeps its github.com module path, which is exactly why it
goes to Gitea's Go registry: pointing GOPROXY there is what makes that
path resolve at all. Verified locally by serving the module zip from a
file proxy and building a consumer against it -- note zip -D, without
which go get rejects the archive's directory entries.

2026-08-09 12:37:19 +03:00