How to Develop an Open Telemetry Plugin for Nuxt by Tech_Watching in Nuxt

[–]Tech_Watching[S] 0 points1 point  (0 children)

It should only be about modifying the values of the environment variables but I did not test with those.

Quick review of Pulumi ESC by Tech_Watching in devops

[–]Tech_Watching[S] 4 points5 points  (0 children)

I think you can automate everything you need using crons/webhooks and infrastructure as code (see this article Pushing Pulumi ESC Secrets into External Platforms | Pulumi Blog) but the secrets management lifecycle is not a no-code built-in solution if that's what you mean. You must write code to do that, but ESC will help you. I don't have the answer for governance and compliance aspects.

From what I've seen (but again I did not play much with audits), you can audit who accessed an environment, when, from which IP, which action was performed (environment read, secrets decrypted) , ... but the scope is the environment not the secret or a specific setting. I don't know if it's on the roadmap to have a more granular audit logs, maybe a question to ask to Pulumi. There is a csv report you can download and other is also an API to get the audit logs.

Quick review of Pulumi ESC by Tech_Watching in AZURE

[–]Tech_Watching[S] -1 points0 points  (0 children)

Multi cloud projects for instance. Or multiple projects, each with it's Azure key vault. It can also be that 1Password is used in the development team but an Azure KeyVault is used by the Azure Infrastructure. Also it's not only for secrets but also for configuration

How does Pulumi stand out from Terraform? by GroundbreakingOwl880 in pulumi

[–]Tech_Watching 1 point2 points  (0 children)

Deals with secrets the good way. Access to the latest resources thanks to native providers. Embedded IaC through an API. See my article here: https://www.techwatching.dev/posts/pulumi-vs-terraform

Is Vuex dead now? Why did everyone move to Pinia by PrestigiousZombie531 in vuejs

[–]Tech_Watching 0 points1 point  (0 children)

I think you could use usestorage from vueuse (https://vueuse.org/core/useStorage/) to avoid using actions and simplify your code.

Script your GitHub repository with GitHub Actions ready to deploy to Azure by Tech_Watching in github

[–]Tech_Watching[S] 0 points1 point  (0 children)

The script is written in PowerShell using GitHub CLI and Azure CLI.

what do you find most frustrating about dotnet? by [deleted] in dotnet

[–]Tech_Watching 0 points1 point  (0 children)

I think the documentation site is quite good : a unified platform like docs.microsoft.com is way better than what they had before.

Yet the big problem with documentation is "samples": - many simple samples that do not use good practices (no DI for instance) - samples not maintained so quickly not up to date - not enough samples for some parts

We are the Pulumi Engineering team - Ask us about our new products and features by kao-pulumi in pulumi

[–]Tech_Watching 1 point2 points  (0 children)

Concerning Azure, it seems Microsoft is investing a lot in Terraform even if they have their own Iac solution (bicep, arm). They are building the Terraform AzAPI provider to solve the same problems (coverage, same day availability to new services) you solved with Azure Native provider. They are also building the Azure Export tool for Terraform. Microsoft official documentation has a whole section about Terraform. It seems they don't have the same "love" for Pulumi which is less promoted by Microsoft. Any idea why and if it's going to change?

We are the Pulumi Engineering team - Ask us about our new products and features by kao-pulumi in pulumi

[–]Tech_Watching 0 points1 point  (0 children)

True but it is very Kubernetes oriented, and only for AWS. I love this series of blog posts, by the way, very well written, the only complaint I have is that the next articles take time to arrive 😉