Paul K space : Stakeholders & Discovery for Internal Azure Systems

Wanting to tie together the disparate and out of date information regarding our internal azure management, a collaboration space to allow knowledge holders to supply information and be part of the proposed piece of work - consder the following

Setting the scene

since starting last year, the general sense hat the Azure Resources could and should be delivered in a way more aligned to our values and client engagements - and a personal bug-bear that what we do should make this easier - better - for all involved

so…..

  • What is the appetite in the practice to deliver our infrastructure via IaC mechanisms

    • GitHub and Actions

    • Branch Protection and workflows to review and integrate configuration files

    • Terraform to manage deploy and pull-down

  • Are we authorised - whats teh scope of what we can do?

  • while we can throw a config file in to process deployments a-la a developer workflow, all workflows should have consideration for how support systems can integrate - can we identify all systems or users that provide any input or requests on behalf of users?

    • setup to trigger on web-hooks

    • multiple “user-facing” entry point frontends

    • single backend implementation

Over the last year, as far as I can, I believe I have a really robust solution tat caters for every option I could think of….. I would really like a general consensus of best way to proceed - end to end I want next level vending'… think Landing Zones on steroids… but I mean huuuuuge steroids….

User 00e46 - can you help set the scene so I dont look silly shouting out automation weirdness pointlessly…

if User 00e46 agrees in principal that we can move this forward - can you @tag the others im sure might nave input below

  • Federico

  • Luke Terry

  • People Ops for on/off-boarding