viktor/infra
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

postiz: wire INSTAGRAM_APP_ID/SECRET via ESO for IG-standalone provider

Browse source 
Standalone provider (instagram-standalone OAuth flow) is what the user
is trying after the FB-Login path was blocked by their Business Account
ad-policy flag. Uses modern scope names (instagram_business_*), so no
JS patch needed unlike the FB-Login provider.
This commit is contained in:
Viktor Barzin 2026-05-09 11:43:01 +00:00
parent e883c9d63f
commit ce9bf5b676
1 changed files with 12 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

12
stacks/postiz/modules/postiz/main.tf
View file

@ -95,6 +95,14 @@ resource "kubernetes_manifest" "external_secret_jwt" {
secretKey = "FACEBOOK_APP_SECRET"
remoteRef = { key = "instagram-poster", property = "facebook_app_secret" }
},
{
secretKey = "INSTAGRAM_APP_ID"
remoteRef = { key = "instagram-poster", property = "instagram_app_id" }
},
{
secretKey = "INSTAGRAM_APP_SECRET"
remoteRef = { key = "instagram-poster", property = "instagram_app_secret" }
},
]
}
}
@ -158,6 +166,10 @@ resource "helm_release" "postiz" {
# placeholder; ESO patches the real values from Vault below.
FACEBOOK_APP_ID = ""
FACEBOOK_APP_SECRET = ""
# IG standalone (Postiz Instagram-Login integration). Uses the modern
# `instagram_business_*` scopes — does not require the FB Login dance.
INSTAGRAM_APP_ID = ""
INSTAGRAM_APP_SECRET = ""
}
# Use our PVC for uploads (overrides the chart's emptyDir default).