This message was deleted.
# generals
sparse-intern-71089
03/16/2021, 3:25 PMThis message was deleted.
r
red-match-15116
03/16/2021, 4:43 PMI think this is what you’re looking for: https://github.com/pulumi/pulumi/issues/2617
I believe @white-balloon-205 might have some insight here.
w
white-balloon-205
03/17/2021, 12:45 AM
There’s a few possible things you might have in mind here:
1. Manage desired state of Pulumi stacks from within another Pulumi program.
2. Managing configuration of the Pulumi Service from within a Pulumi program (like stack tags, policy packs, teams, etc)
3. Possibly something else?
(1) is indeed 2617 that @red-match-15116 referenced. We’ve been working on something that will address that - and should have it available soon. If you are interested in trying it out - drop me your GitHub I’d and I'll add you to the repo where we are working on it.
w
wet-noon-14291
03/18/2021, 8:40 AMIt was number two I was more interested in. How can I manage the pulumi service or parts of it.
Please add me, mastoj is my github id.
w
white-balloon-205
03/18/2021, 6:27 PM
How can I manage the pulumi service or parts of it.What in particular in the Pulumi Service did you want to manage?
w
wet-noon-14291
03/18/2021, 10:58 PMI was thinking teams and stack permissions.
wet-noon-14291
03/18/2021, 11:00 PMTo be more concrete. I was thinking of when we establish a new team we want to automate things the team can access through pulumi, but to do so we also need store things the team should not be able to access in pulumi, therefor I would like to explicitly control which stack a team has access to automatically.