When you build a #terragrunt compliant stack of modules that can be used in any case for any capacity, and your engineers still use #clickops.
Why? oh why do they do this?
When you build a #terragrunt compliant stack of modules that can be used in any case for any capacity, and your engineers still use #clickops.
Why? oh why do they do this?
Today's challenge - Bridge the gaps in #terraform written vs Infrastructure that exists in an account (in this case an #aws account), where in that account has a HUGE amount of #drift because the idiots who built the #IaC originally didnt understand that IaC and #clickops dont exist well together.
oh #microsoft
I opened an #azure support ticket with a quota question and provided the error from #terraform where the quota was hit and I'm just asking for an increase.
Their response, "we must have a screen shot"
But.... you have the text from the error. That is what you'd get from the screenshot IN THE FIRST PLACE.
#clickOps really sucks and it seems to be the primary way people use this cloud.
I know I'm dealing with a contractor or subcontractor following a script and that I'll likely have to make a screenshot of the text and provide it to them to move forward.
It's silly.
Is anybody #azure using #terraform because all of the Microsoft documentation and the support folks seem 100% into #clickOps? I donβt get it.
Iβm presently having fun with the #postgres server az cli lists citext as allowed and psql lists as available but installation fails because itβs not on the allowed list.
this is baffling. I do not understand why the CLI tool and the portal do not agree. This is managed by terraform and one of three environments. Two of them are fine. Itβs just bizarre.
Communick update 1:
In true "YAGNI" fashion, I went by for 2 years without fully automated instance deployments. There was no "#clickops", but I had to manually check some things (customization options, DNS) and run some commands on every new instance.
Now that I'm waking up at least every other day with a new customer requesting their #matrix server, it's finally time to automate this. The goal is to have a server up and running in 5 minutes after the customer filled the checkout form.