Repository navigation
Expand file tree
/
Copy pathMakefile
More file actions
405 lines (351 loc) · 22.1 KB
/
Copy pathMakefile
File metadata and controls
405 lines (351 loc) · 22.1 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
PUBLIC_IMAGE := "hoophq/hoop"
VERSION ?= $(or ${GIT_TAG},${GIT_TAG},v0)
GITCOMMIT ?= $(shell git rev-parse HEAD)
DIST_FOLDER ?= ./dist
MSSQL_JDBC_FIXTURE := agent/integration/testdata/mssql-jdbc
MSSQL_JDBC_CLASSPATH_FILE := $(CURDIR)/$(MSSQL_JDBC_FIXTURE)/target/classpath.txt
DATE ?= $(shell date -u "+%Y-%m-%dT%H:%M:%SZ")
GOOS ?= linux
GOARCH ?= amd64
# compatible with uname -s
OS := $(shell echo "$(GOOS)" | awk '{print toupper(substr($$0, 1, 1)) tolower(substr($$0, 2))}')
SYMLINK_ARCH := $(if $(filter $(GOARCH),amd64),x86_64,$(if $(filter $(GOARCH),arm64),aarch64,$(ARCH)))
POSTREST_ARCH_SUFFIX := $(if $(filter $(GOARCH),amd64),linux-static-x64.tar.xz,$(if $(filter $(GOARCH),arm64),ubuntu-aarch64.tar.xz,$(ARCH)))
UNAME_S := $(shell uname -s)
UNAME_M := $(shell uname -m)
ifeq ($(UNAME_S),Darwin)
ifeq ($(UNAME_M),x86_64)
RUST_TARGET := x86_64-apple-darwin
else ifeq ($(UNAME_M),arm64)
RUST_TARGET := aarch64-apple-darwin
endif
else ifeq ($(UNAME_S),Linux)
ifeq ($(UNAME_M),x86_64)
RUST_TARGET := x86_64-unknown-linux-gnu
else ifeq ($(UNAME_M),aarch64)
RUST_TARGET := aarch64-unknown-linux-gnu
endif
endif
LDFLAGS := "-s -w \
-X github.com/hoophq/hoop/common/version.version=${VERSION} \
-X github.com/hoophq/hoop/common/version.gitCommit=${GITCOMMIT} \
-X github.com/hoophq/hoop/common/version.buildDate=${DATE} \
-X github.com/hoophq/hoop/common/monitoring.honeycombApiKey=${HONEYCOMB_API_KEY} \
-X github.com/hoophq/hoop/common/monitoring.sentryDSN=${SENTRY_DSN} \
-X github.com/hoophq/hoop/gateway/analytics.segmentApiKey=${SEGMENT_API_KEY} \
-X github.com/hoophq/hoop/gateway/analytics.intercomHmacKey=${INTERCOM_HMAC_KEY}"
build-dev-rust:
# since we are in osx machine cross needs to be used to build linux binary because some crypto libs does not have cross compilation
echo "Building hoop_rs for dev"
cd agentrs && cross build --release --target aarch64-unknown-linux-gnu
mkdir -p ${HOME}/.hoop/bin
cp agentrs/target/aarch64-unknown-linux-gnu/release/agentrs ${HOME}/.hoop/bin/hoop_rs
chmod +x ${HOME}/.hoop/bin/hoop_rs
install-rust:
./scripts/install-rust.sh
run-dev:
./scripts/dev/run.sh
# Runs on the host, not in the run-dev container: that container starts an
# agent, and the control plane opens no gRPC transport for it to reach.
run-dev-control-plane:
./scripts/dev/run-control-plane.sh
run-dev-postgres:
./scripts/dev/run-postgres.sh
run-dev-presidio:
./scripts/dev/run-presidio.sh
run-dev-spiffe-prep:
./scripts/dev/spiffe-prep.sh
run-dev-spiffe-agent:
./scripts/dev/run-spiffe-agent.sh
run-dev-spiffe: run-dev-spiffe-agent
build-dev-client:
go build -ldflags "-s -w -X github.com/hoophq/hoop/client/proxy.defaultListenAddrValue=0.0.0.0" -o ${HOME}/.hoop/bin/hoop github.com/hoophq/hoop/client
build-dev-webapp:
./scripts/dev/build-webapp.sh
# Development against a local libhoop clone at ./libhoop. One module,
# github.com/hoophq/libhoop: the protocol proxies and redactors at its root,
# and the codecs the sidecar plugs in under ./v2/codec. That is a plain
# directory, not a second module — the `v2` in the import path names a folder,
# not a major version.
#
# A replace rather than `go work use`: the consumers pin a released version and
# Go resolves it first, so a checkout ahead of the last tag would be ignored
# and one before the first tag fails outright.
#
# Not needed to build or test (the module resolves from the proxy) and
# deliberately not a prerequisite of any target, so a dirty go.work is always
# something you opted into. Undo with:
# go work edit -dropreplace github.com/hoophq/libhoop
libhoop-dev:
go work edit -replace github.com/hoophq/libhoop=./libhoop
# Generate WASM module for RDP parser
generate-wasm:
cd gateway/rdp/parser && go generate
test: test-oss test-enterprise
test-oss: generate-wasm test-sidecar
env CGO_ENABLED=0 go test -json -v github.com/hoophq/hoop/...
test-enterprise: generate-wasm
env CGO_ENABLED=0 go test -json -v github.com/hoophq/hoop/...
# `github.com/hoophq/hoop/...` now matches the sidecar module too, since it
# was renamed to sit under the repository path. What it does NOT do is prove
# each nested module builds on its own: in workspace mode every module
# resolves against the union of the workspace, so a go.mod missing a require
# still passes. This target enters each module directory, which is the only
# way to catch that before the proxy does. One go.mod per optional dependency
# is what keeps the root's dependency set down to libhoop alone, and this is
# what defends it.
#
# The list is discovered rather than written down, so a nested module added
# later is covered on the day it is added. It is then filtered to the modules
# go.work actually lists: `go test` refuses to run in a directory the active
# workspace does not contain ("directory prefix . does not contain modules
# listed in go.work"), which under set -e aborts the loop and takes test-oss
# with it. sidecar/e2e is out of the workspace on purpose and is the module
# this skips today; see test-sidecar-e2e, which is how that one runs.
test-sidecar:
@set -e; for m in $$(find sidecar -name go.mod -exec dirname {} \;); do \
grep -q "^[[:space:]]*\./$$m$$" go.work || continue; \
(cd $$m && env CGO_ENABLED=0 go test -json -v ./...); \
done
# End-to-end sidecar suite (DEP-170): boots a real mysql:8 container through
# testcontainers-go and drives the shipped hoop-inspect binary (sidecar/cmd)
# as a subprocess in front of it, so masking and the auth handshake are proven
# over the wire instead of against a decoder in isolation. `sidecar/e2e` is a
# nested module, and `./sidecar/e2e/...` from here matches nothing for the
# reason above, so the target enters the directory. No -race: the work is in
# the container and the binary under test is a separate process anyway.
#
# GOWORK=off is required, not tidiness: this module is absent from go.work on
# purpose — a testcontainers/docker dependency tree has no business in the
# workspace every other module resolves against — and a workspace that does
# not list it refuses the build outright ("directory prefix . does not contain
# modules listed in go.work"). The harness re-derives the setting for the
# sidecar/cmd build it shells out to, which must keep the workspace.
#
# NOT a dependency of test-oss or test-sidecar, and must not become one. Those
# run in the unit-test job, which has no Docker guarantee and no budget for a
# container pull plus boot plus binary build on every unit run. This target has
# its own CI job (sidecar-e2e in .github/workflows/pullrequest.yml).
test-sidecar-e2e:
cd sidecar/e2e && env GOWORK=off CGO_ENABLED=0 go test -tags integration -v -timeout 10m -count=1 ./...
prepare-mssql-jdbc:
$(RM) $(MSSQL_JDBC_CLASSPATH_FILE)
mvn -q -f $(MSSQL_JDBC_FIXTURE)/pom.xml dependency:build-classpath -DincludeScope=runtime -Dmdep.outputFile=$(MSSQL_JDBC_CLASSPATH_FILE)
# Integration tests drive the real controller.Agent against upstream
# containers via libhoop. Protocol proxying lives in the private
# github.com/hoophq/libhoop module, resolved from the module proxy; a build
# without credentials for it fails outright rather than degrading to no-op
# protocol handling.
test-integration: generate-wasm prepare-mssql-jdbc
env CGO_ENABLED=1 MSSQL_JDBC_CLASSPATH_FILE="$(MSSQL_JDBC_CLASSPATH_FILE)" go test -tags integration -race -v -timeout 10m -count=1 ./agent/integration/...
# Agent↔gateway transport harness. Runs against the real gateway gRPC
# transport; the PG round-trip goes through the proxy implementation in the
# private github.com/hoophq/libhoop module, so a build without credentials
# for it fails outright. Kept a separate target/CI job from test-integration
# so its Postgres containers don't contend with the heavy agent suite on a
# shared runner.
test-transport: generate-wasm
env CGO_ENABLED=1 go test -tags integration -race -v -timeout 8m -count=1 ./gateway/integration/transport/...
# Gateway smoke tests only exercise the HTTP API / model / auth layers. They
# still link the private github.com/hoophq/libhoop module — resolved from
# the module proxy, so the build fails outright without credentials for it —
# but not a fresh WASM build: gateway/rdp/parser embeds the committed
# rdp_parser.wasm via go:embed, so the artifact already exists at build time.
# Skipping generate-wasm keeps this target independent of the Rust toolchain.
# The path is non-recursive on purpose: the transport suite (a subdir) drives
# protocol proxying and runs under test-transport instead.
test-gateway:
env CGO_ENABLED=0 go test -tags integration -v -timeout 8m -count=1 ./gateway/integration/
# Same smoke suite, but the gateway state store is the embedded PGlite (wasm)
# database instead of a PostgreSQL container — the standalone-mode regression
# net. It fails on SQL the embedded backend cannot run and on code that
# deadlocks the pool capped at one connection, both invisible on regular
# PostgreSQL. No Docker required.
test-gateway-pglite:
env CGO_ENABLED=0 GATEWAY_TEST_DB=pglite go test -tags integration -v -timeout 8m -count=1 ./gateway/integration/
# Standalone-mode lifecycle suite (DEP-38): boots the gateway on the embedded
# PGlite database with the full transport stack, provisions the dedicated
# `standalone` agent through the same services code path `hoop start
# standalone` runs, and asserts a real agent controller connects with the
# provisioned DSN. Nothing here proxies a protocol and the committed
# rdp_parser.wasm is embedded, so neither a WASM rebuild nor the Rust
# toolchain is required. No Docker either. The build still links the private
# github.com/hoophq/libhoop module and fails outright without credentials
# for the proxy fetch.
test-standalone:
env CGO_ENABLED=0 go test -tags integration -v -timeout 8m -count=1 ./gateway/integration/standalone/
# True single-binary end-to-end (DEP-38): builds the hoop CLI and runs
# `hoop start standalone` as a subprocess twice against the same throwaway
# $HOME — first boot (initdb + migrations + agent provisioning) and resume
# boot (cluster resume + persisted credentials). The only test layer that
# exercises the shipped artifact itself: go:embed assets, CLI wiring, and
# the gateway+agent single-process composition.
test-standalone-e2e:
./scripts/standalone-e2e.sh
generate-openapi-docs:
cd ./gateway/ && go run github.com/swaggo/swag/cmd/swag@v1.16.3 init -g api/server.go -o api/openapi/autogen --outputTypes go --markdownFiles api/openapi/docs/ --parseDependency
go run gateway/cmd/openapi-gen/main.go
swag-fmt:
swag fmt
publish:
./scripts/publish-release.sh
merge-artifacts:
./scripts/merge-artifacts.sh
# Build all Darwin Rust binaries (for CI) - uses GOOS/GOARCH
build-rust-darwin-all:
GOOS=darwin GOARCH=amd64 $(MAKE) build-rust-single
GOOS=darwin GOARCH=arm64 $(MAKE) build-rust-single
# Build all Linux Rust binaries (for CI) - uses GOOS/GOARCH
build-rust-linux-all:
GOOS=linux GOARCH=amd64 $(MAKE) build-rust-single
GOOS=linux GOARCH=arm64 $(MAKE) build-rust-single
# Build single Rust binary using GOOS/GOARCH variables
build-rust-single: build-empty-folder
cd agentrs && cargo build --release --target ${RUST_TARGET} && \
cp target/${RUST_TARGET}/release/agentrs ../dist/binaries/${GOOS}_${GOARCH}/hoop_rs
build-empty-folder:
mkdir -p ${DIST_FOLDER}/binaries/${GOOS}_${GOARCH}
build-tar-files:
mkdir -p ${DIST_FOLDER}/binaries/${GOOS}_${GOARCH}
tar -czvf ${DIST_FOLDER}/binaries/hoop_${VERSION}_${OS}_${GOARCH}.tar.gz -C ${DIST_FOLDER}/binaries/${GOOS}_${GOARCH} .
tar -czvf ${DIST_FOLDER}/binaries/hoop_${VERSION}_${OS}_${SYMLINK_ARCH}.tar.gz -C ${DIST_FOLDER}/binaries/${GOOS}_${GOARCH} .
sha256sum ${DIST_FOLDER}/binaries/hoop_${VERSION}_${OS}_${GOARCH}.tar.gz > ${DIST_FOLDER}/binaries/hoop_${VERSION}_${OS}_${GOARCH}_checksum.txt
sha256sum ${DIST_FOLDER}/binaries/hoop_${VERSION}_${OS}_${SYMLINK_ARCH}.tar.gz > ${DIST_FOLDER}/binaries/hoop_${VERSION}_${OS}_${SYMLINK_ARCH}_checksum.txt
rm -rf ${DIST_FOLDER}/binaries/${GOOS}_${GOARCH}
build-go: build-empty-folder
env CGO_ENABLED=0 GOOS=${GOOS} GOARCH=${GOARCH} go build -ldflags ${LDFLAGS} -o ${DIST_FOLDER}/binaries/${GOOS}_${GOARCH}/ client/hoop.go
# Hoop Tunnel daemon (hsh-tunneld).
#
# hsh-tunneld is the privileged tunnel daemon shipped with the `hsh` CLI
# (which lives in the separate hoophq/hsh repo). The `hsh` build downloads
# hsh-tunneld from the hoop GitHub Release and bundles it with the bun-built
# `hsh` binary into a per-platform archive.
#
# Output layout (intentionally distinct from build-go's ${GOOS}_${GOARCH}/
# folder): each invocation writes one flat per-target file under
# ${DIST_FOLDER}/release-binaries/ so the release workflow can collect them
# verbatim and attach them to a GitHub Release without unpacking. Windows
# binaries are suffixed `.exe`.
HSH_TUNNELD_EXE := $(if $(filter $(GOOS),windows),hsh-tunneld-${GOOS}-${GOARCH}.exe,hsh-tunneld-${GOOS}-${GOARCH})
build-hsh-tunneld:
mkdir -p ${DIST_FOLDER}/release-binaries
cd tunnel && env CGO_ENABLED=0 GOOS=${GOOS} GOARCH=${GOARCH} \
go build -ldflags ${LDFLAGS} \
-o ../${DIST_FOLDER}/release-binaries/${HSH_TUNNELD_EXE} \
./cmd/hsh-tunneld
# Build hsh-tunneld for every supported target. Used by the release
# workflow and convenient for local cross-build verification.
build-hsh-tunneld-all:
GOOS=linux GOARCH=amd64 $(MAKE) build-hsh-tunneld
GOOS=linux GOARCH=arm64 $(MAKE) build-hsh-tunneld
GOOS=darwin GOARCH=amd64 $(MAKE) build-hsh-tunneld
GOOS=darwin GOARCH=arm64 $(MAKE) build-hsh-tunneld
GOOS=windows GOARCH=amd64 $(MAKE) build-hsh-tunneld
GOOS=windows GOARCH=arm64 $(MAKE) build-hsh-tunneld
# Stage the user-facing install/uninstall scripts (RD-226) into the
# release-binaries directory so they get uploaded as Release assets
# alongside the daemon binaries. Each per-platform archive consumer
# (RD-227's hsh bundle, the brew formula, the linux tarball builder)
# pulls them from there.
#
# Lives in this Makefile target (rather than the workflow file
# itself) so a local `make build-release-checksums` produces the same
# `dist/release-binaries/` tree that the workflow uploads.
stage-release-scripts:
mkdir -p ${DIST_FOLDER}/release-binaries
cp tunnel/dist/scripts/install.sh ${DIST_FOLDER}/release-binaries/install.sh
cp tunnel/dist/scripts/uninstall.sh ${DIST_FOLDER}/release-binaries/uninstall.sh
chmod 0755 ${DIST_FOLDER}/release-binaries/install.sh
chmod 0755 ${DIST_FOLDER}/release-binaries/uninstall.sh
# SHA256SUMS over the release binaries + install scripts, ready to
# attach to a GitHub Release. Generated in
# `dist/release-binaries/SHA256SUMS` so consumers can verify with
# `sha256sum -c SHA256SUMS` after downloading.
#
# We include the scripts in the checksum file because RD-227's
# build-time download pipeline verifies *every* file it pulls from
# the hoop release against this SHA256SUMS — leaving scripts out
# would create a hole in the trust chain.
build-release-checksums: stage-release-scripts
cd ${DIST_FOLDER}/release-binaries && sha256sum hsh-tunneld-* install.sh uninstall.sh > SHA256SUMS
build-webapp:
mkdir -p ${DIST_FOLDER}
# Build CLJS bundle
cd ./webapp && npm install && npm run release:hoop-ui && cd ../
cat ./webapp/src/webapp/version.js | awk -F"'" '{printf "%s", $$2}' > ./webapp/resources/version.txt
# Build React shell (webapp_v2)
cd ./webapp_v2 && npm ci && npm run build && cd ../
# Merge: CLJS resources first, React shell on top (React's index.html wins)
mkdir -p ${DIST_FOLDER}/_ui_merge
cp -a ./webapp/resources/. ${DIST_FOLDER}/_ui_merge/
cp -a ./webapp_v2/dist/. ${DIST_FOLDER}/_ui_merge/public/
tar -czf ${DIST_FOLDER}/webapp.tar.gz -C ${DIST_FOLDER}/_ui_merge .
rm -rf ${DIST_FOLDER}/_ui_merge
extract-webapp:
mkdir -p ./rootfs/app/ui && tar -xf ${DIST_FOLDER}/webapp.tar.gz -C rootfs/app/ui/
# Stage the built webapp (dist/webapp.tar.gz) into the gateway embed
# directory so `make build-go` produces a binary carrying the web UI.
embed-webapp:
rm -rf gateway/webappui/staticui
mkdir -p gateway/webappui/staticui
tar -xf ${DIST_FOLDER}/webapp.tar.gz -C gateway/webappui/staticui --strip-components=2 ./public
touch gateway/webappui/staticui/.gitkeep
build-helm-chart:
mkdir -p ${DIST_FOLDER}
helm package ./deploy/helm-chart/chart/agent/ --app-version ${VERSION} --destination ${DIST_FOLDER}/ --version ${VERSION}
helm package ./deploy/helm-chart/chart/gateway/ --app-version ${VERSION} --destination ${DIST_FOLDER}/ --version ${VERSION}
# The inspection sidecar. Standalone, not a wrapper: it depends on no other
# chart and ships its own image, hoophq/hoopsidecar.
helm package ./deploy/helm-chart/chart/sidecar/ --app-version ${VERSION} --destination ${DIST_FOLDER}/ --version ${VERSION}
# Clean image line (DEP-66): wrapper charts that bundle the base chart via a
# file:// dependency (-u) and default images to the clean-only hoophq/*-ng repos.
helm package -u ./deploy/helm-chart/chart/hoop-ng/ --app-version ${VERSION} --destination ${DIST_FOLDER}/ --version ${VERSION}
helm package -u ./deploy/helm-chart/chart/hoopagent-ng/ --app-version ${VERSION} --destination ${DIST_FOLDER}/ --version ${VERSION}
helm registry login ghcr.io --username ${GITHUB_USERNAME} --password ${GITHUB_CONTAINER_REGISTRY_TOKEN}
helm push ${DIST_FOLDER}/hoop-chart-${VERSION}.tgz oci://ghcr.io/hoophq/helm-charts/
helm push ${DIST_FOLDER}/hoopagent-chart-${VERSION}.tgz oci://ghcr.io/hoophq/helm-charts/
helm push ${DIST_FOLDER}/hoopsidecar-chart-${VERSION}.tgz oci://ghcr.io/hoophq/helm-charts/
helm push ${DIST_FOLDER}/hoop-ng-chart-${VERSION}.tgz oci://ghcr.io/hoophq/helm-charts/
helm push ${DIST_FOLDER}/hoopagent-ng-chart-${VERSION}.tgz oci://ghcr.io/hoophq/helm-charts/
build-gateway-bundle:
rm -rf ${DIST_FOLDER}/hoopgateway
mkdir -p ${DIST_FOLDER}/hoopgateway/opt/hoop/bin
mkdir -p ${DIST_FOLDER}/hoopgateway/opt/hoop/migrations
mkdir -p ${DIST_FOLDER}/hoopgateway/opt/hoop/webapp
tar -xf ${DIST_FOLDER}/binaries/hoop_${VERSION}_Linux_${GOARCH}.tar.gz -C ${DIST_FOLDER}/hoopgateway/opt/hoop/bin/ && \
cp gateway/migrations/*.up.sql ${DIST_FOLDER}/hoopgateway/opt/hoop/migrations/ && \
tar -xf ${DIST_FOLDER}/webapp.tar.gz -C ${DIST_FOLDER}/hoopgateway/opt/hoop/webapp --strip 1 && \
tar -czf ${DIST_FOLDER}/hoopgateway_${VERSION}-Linux_${GOARCH}.tar.gz -C ${DIST_FOLDER}/ hoopgateway
release-s3: release-s3-cf-templates
./scripts/generate-changelog.sh ${VERSION} > ${DIST_FOLDER}/CHANGELOG.txt
find ${DIST_FOLDER}/binaries/ -name *_checksum.txt -exec cat '{}' \; > ${DIST_FOLDER}/checksums.txt
mv ${DIST_FOLDER}/binaries/*.tar.gz ${DIST_FOLDER}/
aws s3 cp ${DIST_FOLDER}/ s3://hoopartifacts/release/${VERSION}/ --exclude "*" --exclude webapp.tar.gz --include checksums.txt --include "*.tgz" --include "*.tar.gz" --recursive
aws s3 cp ${DIST_FOLDER}/CHANGELOG.txt s3://hoopartifacts/release/${VERSION}/CHANGELOG.txt
release-s3-latest:
echo -n "${VERSION}" > ${DIST_FOLDER}/latest.txt
aws s3 cp ${DIST_FOLDER}/latest.txt s3://hoopartifacts/release/latest.txt
aws s3 cp ./scripts/install-cli.sh s3://hoopartifacts/release/install-cli.sh
release-s3-cf-templates-latest:
aws s3 cp --region us-east-1 ${DIST_FOLDER}/hoopdev-platform.template.yaml s3://hoopdev-platform-cf-us-east-1/latest/hoopdev-platform.template.yaml
aws s3 cp --region us-east-2 ${DIST_FOLDER}/hoopdev-platform.template.yaml s3://hoopdev-platform-cf-us-east-2/latest/hoopdev-platform.template.yaml
aws s3 cp --region us-west-1 ${DIST_FOLDER}/hoopdev-platform.template.yaml s3://hoopdev-platform-cf-us-west-1/latest/hoopdev-platform.template.yaml
aws s3 cp --region us-west-2 ${DIST_FOLDER}/hoopdev-platform.template.yaml s3://hoopdev-platform-cf-us-west-2/latest/hoopdev-platform.template.yaml
aws s3 cp --region eu-west-1 ${DIST_FOLDER}/hoopdev-platform.template.yaml s3://hoopdev-platform-cf-eu-west-1/latest/hoopdev-platform.template.yaml
aws s3 cp --region eu-west-2 ${DIST_FOLDER}/hoopdev-platform.template.yaml s3://hoopdev-platform-cf-eu-west-2/latest/hoopdev-platform.template.yaml
aws s3 cp --region eu-central-1 ${DIST_FOLDER}/hoopdev-platform.template.yaml s3://hoopdev-platform-cf-eu-central-1/latest/hoopdev-platform.template.yaml
aws s3 cp --region ap-southeast-2 ${DIST_FOLDER}/hoopdev-platform.template.yaml s3://hoopdev-platform-cf-ap-southeast-2/latest/hoopdev-platform.template.yaml
release-s3-cf-templates:
sed "s|LATEST_HOOP_VERSION|${VERSION}|g" deploy/aws/hoopdev-platform.template.yaml > ${DIST_FOLDER}/hoopdev-platform.template.yaml
aws s3 cp --region us-east-1 ${DIST_FOLDER}/hoopdev-platform.template.yaml s3://hoopdev-platform-cf-us-east-1/${VERSION}/hoopdev-platform.template.yaml
aws s3 cp --region us-east-2 ${DIST_FOLDER}/hoopdev-platform.template.yaml s3://hoopdev-platform-cf-us-east-2/${VERSION}/hoopdev-platform.template.yaml
aws s3 cp --region us-west-1 ${DIST_FOLDER}/hoopdev-platform.template.yaml s3://hoopdev-platform-cf-us-west-1/${VERSION}/hoopdev-platform.template.yaml
aws s3 cp --region us-west-2 ${DIST_FOLDER}/hoopdev-platform.template.yaml s3://hoopdev-platform-cf-us-west-2/${VERSION}/hoopdev-platform.template.yaml
aws s3 cp --region eu-west-1 ${DIST_FOLDER}/hoopdev-platform.template.yaml s3://hoopdev-platform-cf-eu-west-1/${VERSION}/hoopdev-platform.template.yaml
aws s3 cp --region eu-west-2 ${DIST_FOLDER}/hoopdev-platform.template.yaml s3://hoopdev-platform-cf-eu-west-2/${VERSION}/hoopdev-platform.template.yaml
aws s3 cp --region eu-central-1 ${DIST_FOLDER}/hoopdev-platform.template.yaml s3://hoopdev-platform-cf-eu-central-1/${VERSION}/hoopdev-platform.template.yaml
aws s3 cp --region ap-southeast-2 ${DIST_FOLDER}/hoopdev-platform.template.yaml s3://hoopdev-platform-cf-ap-southeast-2/${VERSION}/hoopdev-platform.template.yaml
publish-sentry-sourcemaps:
tar -xvf ${DIST_FOLDER}/webapp.tar.gz
sentry-cli sourcemaps upload --release=$$(cat ./version.txt) ./public/js/app.js.map --org hoopdev --project webapp
.PHONY: run-dev run-dev-control-plane run-dev-postgres build-dev-webapp test-enterprise test-oss test prepare-mssql-jdbc test-integration test-transport test-gateway test-gateway-pglite test-standalone test-standalone-e2e test-gateway-pglite generate-openapi-docs build-go build-dev-client build-webapp build-helm-chart build-gateway-bundle extract-webapp publish release-s3 release-s3-latest release-s3-cf-templates-latest release-s3-cf-templates-latest swag-fmt build-rust-darwin-all build-rust-linux-all build-rust-single build-empty-folder build-dev-rust install-rust merge-artifacts generate-wasm build-hsh-tunneld build-hsh-tunneld-all build-release-checksums stage-release-scripts