#azure (2018-11)
Archive: https://archive.sweetops.com/azure/
2018-11-02
![btai avatar](https://avatars.slack-edge.com/2019-09-04/736463433650_34701761239ea7ba8207_72.jpg)
@btai has joined the channel
2018-11-06
![btai avatar](https://avatars.slack-edge.com/2019-09-04/736463433650_34701761239ea7ba8207_72.jpg)
anyone here with a decent amount of azure experience?
![Andriy Knysh (Cloud Posse) avatar](https://avatars.slack-edge.com/2018-06-13/382332470551_54ed1a5d986e2068fd9c_72.jpg)
@geertn mentioned he did
![btai avatar](https://avatars.slack-edge.com/2019-09-04/736463433650_34701761239ea7ba8207_72.jpg)
im curious how people are grouping their resource groups. im not sure if its better to be very granular, or if a single resource group per environment
![geertn avatar](https://avatars.slack-edge.com/2020-10-27/1449291918182_42d49487baccfb1264b1_72.png)
@btai We use a subcription per environment. One subcription for general services to other subscriptions (VPN), one for prod, staging, etc. Next to that generally map resource groups to terraform environment / state files. So eg a RG for WAF with NLB, a RG for Domain Controllers with LDAP NLB, a RG for Recovery Services Vault, One RG for all networking stuff (Vnets/subnets). Mostly becuase it’s handy for deleting/redeploying thing without worrying too much but also to be able to set granular permissions on the RG’s
![btai avatar](https://avatars.slack-edge.com/2019-09-04/736463433650_34701761239ea7ba8207_72.jpg)
ok so youre not super granular with RGs, but within each environment you’ll have a handful of RGs
![btai avatar](https://avatars.slack-edge.com/2019-09-04/736463433650_34701761239ea7ba8207_72.jpg)
@geertn
2018-11-07
![geertn avatar](https://avatars.slack-edge.com/2020-10-27/1449291918182_42d49487baccfb1264b1_72.png)
@btai to give you an idea for an env with 15 servers we use about 8 rg
![geertn avatar](https://avatars.slack-edge.com/2020-10-27/1449291918182_42d49487baccfb1264b1_72.png)
Next to that about 6 RG for things like recovery vault, packer images and build space, keyvault
![geertn avatar](https://avatars.slack-edge.com/2020-10-27/1449291918182_42d49487baccfb1264b1_72.png)
I’d say it’s pretty granular
![btai avatar](https://avatars.slack-edge.com/2019-09-04/736463433650_34701761239ea7ba8207_72.jpg)
@geertn Okay sounds good. so in my environment I have a RG for the vnet + default subnets, RG for my AKS cluster + ALB + cluster subnets, and I’m planning on a RG for the pg database.
![btai avatar](https://avatars.slack-edge.com/2019-09-04/736463433650_34701761239ea7ba8207_72.jpg)
sounds about right?
![btai avatar](https://avatars.slack-edge.com/2019-09-04/736463433650_34701761239ea7ba8207_72.jpg)
@geertn completely different question, do you know why the Azure managed pg database makes the username {admin_login}@{host_name}
?
![geertn avatar](https://avatars.slack-edge.com/2020-10-27/1449291918182_42d49487baccfb1264b1_72.png)
Sounds good to me. I wouldn’t know about PG DB username no
2018-11-12
![btai avatar](https://avatars.slack-edge.com/2019-09-04/736463433650_34701761239ea7ba8207_72.jpg)
@geertn do you use AKS?
2018-11-13
![geertn avatar](https://avatars.slack-edge.com/2020-10-27/1449291918182_42d49487baccfb1264b1_72.png)
No
2018-11-19
![s.p.i avatar](https://secure.gravatar.com/avatar/8b5169bfb85e1f09a32ef0c782666aad.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0006-72.png)
Hi there, has anyone tested the new Python environment for functions ? https://github.com/Azure/azure-functions-python-worker#overview Bonus : have you tested it with Terraform built resources ? I’d like to know if it’s stable enough for simple timed triggered scripts.
Python worker for Azure Functions. Contribute to Azure/azure-functions-python-worker development by creating an account on GitHub.
2018-11-29
![Erik Osterman (Cloud Posse) avatar](https://secure.gravatar.com/avatar/88c480d4f73b813904e00a5695a454cb.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0023-72.png)
@Erik Osterman (Cloud Posse) has joined the channel