This message was deleted.
# general
b
This message was deleted.
s
It should be possible to select the repositories the app should have access to, no default access to whole organization.
w
Thanks @stocky-salesmen-15167 - so youโ€™d prefer to select the repos in GHโ€™s UI to give permissions to, then select all of them or a subset in Infracost to enable the integration on, right?
s
Hmm...yes,maybe. Or I'm thinking of something like renovatebot: enabling repos for the app in GH UI, maybe get a PR with some infracost.yml (don't know if needed) ans after merge the integration is enabled?! Just thinking loud while sitting on my sofa ๐Ÿ›‹๏ธ ๐Ÿ™ƒ
w
Love a good bit of sofa-based feedback ๐Ÿ˜„ The alternative flows could be: ## Option A: GitHub App 1. GH oauth dance, select All repos or a subset of repos in each org you want to give permissions to. This is all happening in GHโ€™s UI. 2. Then in Infracost Cloud you see the repos that weโ€™re permissioned to see, you can select repos to enable the integration on. 3. We parse HCL and if there are warnings (e.g. we need var files), we show you a link to docs so you can add infracost.yml to repo root and the integration automatically runs again on pushes. 4. PR comments are left automatically with
behavior=update
## Option B: OAuth App 1. GH oauth dance, you just enable an org. So there is no repo-selector in GHโ€™s UI. 2. the rest of the steps are the same.
p
Option A for me because I already know that sharing the full org will be a no go for my company
๐Ÿ‘ 2
w
@polite-engineer-31217 perfect! early feedback saves us rework later on ๐Ÿ™‚
s
๐Ÿ…ฐ๏ธ please
๐Ÿ‘ 2
m
thanks @polite-engineer-31217 & @stocky-salesmen-15167 for your feedback infraheart ๐Ÿ’ช
r
+1, GitHub App makes more sense to me given the Infracost app use case.
๐Ÿ‘ 2
v
+1 Option A
๐Ÿ™Œ 1
๐Ÿ™ 1
w
Thanks for the quick feedback everyone! The winner was clear: weโ€™re going with Option A
f
๐Ÿ˜„ It's later, but yes, Option A.
shipitparrot 1
๐Ÿ™Œ 1