belt 0.3.9 β 0.3.11
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/CHANGELOG.md +22 -0
- data/lib/belt/cli/deploy_command.rb +1 -1
- data/lib/belt/version.rb +1 -1
- data/lib/templates/module/outputs.tf.erb +1 -1
- metadata +1 -1
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: dd99b277649c4757cfd960cbe4a4a86244aa43dc7e03eaf09bef9122eb7404b6
|
|
4
|
+
data.tar.gz: a111df345c23919087c88321b006599e3694ca876132dec468b628dbd9ce0f3b
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: e9dc33ddab33e897db4087a3c89820dbb6ebbc9c9240d407794ea60d4cbaf0d950d2bd83ac5cd113f85efbab764bce9f9e413aac10bb3fa96874fbda6e5cbd9a
|
|
7
|
+
data.tar.gz: ea583edcd87f88545d7f44eb715df5f70006a8cf3b3f7503d8863f2cc6c7cedd3821206a380ba79dcd491a524786d7fd724a61d70a1bb89ec376bb97c27d808b
|
data/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,27 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 0.3.11
|
|
4
|
+
|
|
5
|
+
### Bug Fix
|
|
6
|
+
|
|
7
|
+
- **`belt deploy` skips route generation on first deploy**: The `generate_routes`
|
|
8
|
+
method would silently bail if `lambda/lib/routes/` didn't already exist on disk.
|
|
9
|
+
Since this directory is gitignored (it's a generated build artifact), a fresh clone
|
|
10
|
+
or first deploy would package the Lambda without route manifests, causing a
|
|
11
|
+
`LoadError` at cold start. Now creates the directory with `mkdir_p` before running
|
|
12
|
+
route generation.
|
|
13
|
+
|
|
14
|
+
## 0.3.10
|
|
15
|
+
|
|
16
|
+
### Bug Fix
|
|
17
|
+
|
|
18
|
+
- **`api_url` output missing base path for custom domains**: When a custom domain is
|
|
19
|
+
configured (e.g. `api.dev.example.com`), the `api_url` terraform output was missing
|
|
20
|
+
the gateway's base path segment. Conveyor-belt maps each gateway to a base path
|
|
21
|
+
(gateway "api" β path `/api`), so the correct URL is
|
|
22
|
+
`https://api.dev.example.com/api` not `https://api.dev.example.com`. The frontend
|
|
23
|
+
would get the wrong `VITE_API_URL` and hit a 403 on the custom domain root.
|
|
24
|
+
|
|
3
25
|
## 0.3.9
|
|
4
26
|
|
|
5
27
|
### Bug Fix
|
|
@@ -428,7 +428,7 @@ module Belt
|
|
|
428
428
|
|
|
429
429
|
def generate_routes(lambda_dir)
|
|
430
430
|
routes_dir = File.join(lambda_dir, 'lib', 'routes')
|
|
431
|
-
|
|
431
|
+
FileUtils.mkdir_p(routes_dir)
|
|
432
432
|
|
|
433
433
|
puts ' πΊοΈ Regenerating route manifests...'
|
|
434
434
|
success = system('belt', 'routes', '--namespace', 'all', '--output-dir', routes_dir)
|
data/lib/belt/version.rb
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
output "api_url" {
|
|
2
2
|
description = "API Gateway base URL (custom domain if configured, otherwise default)"
|
|
3
|
-
value = var.domain != "" ? "https://${local.api_domain}" : values(conveyor_belt.main.api_gateway_urls)[0]
|
|
3
|
+
value = var.domain != "" ? "https://${local.api_domain}/${keys(conveyor_belt.main.api_gateway_urls)[0]}" : values(conveyor_belt.main.api_gateway_urls)[0]
|
|
4
4
|
}
|
|
5
5
|
|
|
6
6
|
output "api_urls" {
|