I did ping.
Yeah,
it's gonna be a quiet one.
Go ahead and open up the um the tech tree just cos I,
I,
I feel like it and it it usually prompts people to like ask questions.
They're like,
hey,
what's,
what's like
laser beam for world domination?
What's that on the tech tree?
My
leg is also itchy,
like I'm having like a just like a biological day,
you know,
like my legs are itchy,
my eyes are itchy.
Maybe I should just like throw a blanket over myself and go back to bed.
All right,
there we go,
there's there's the,
there's the tech tree.
So update things.
Uh,
yeah,
that's still going.
That's done.
Yep,
yep.
It's over here.
Uh yep,
yep.
Oh,
that one red.
support I can,
I can take a look at again.
I had some help from a QDC member on the whole sharp flu thing.
um
Shan says how oh terraform,
how's that been?
Uh,
it's great,
but like
it's kind of confusing as well.
So we're in,
we're operating in a like what's called a hub and spoke model.
So like
what we basically have here is like
spoke
network.
And this is because,
um,
Azure basically can,
you can like
you used to need like,
you know,
piles of network routers and switches to make
complicated networks with Azure and other cloud providers.
Now you can just like use a JSON file and be like,
hey,
I wanna,
I want a network.
Like,
here you go,
here's a network,
and it's like real complicated and difficult to
understand cos it's not a physical network,
it's a,
it's a virtual network.
Um,
and then this is like hub,
so,
isn't that in there?
I think so,
I thought that was just like random text to your hub network.
Let's get rid of that.
So like
we have a connection
from,
from the hub to the spoke
and then in the spoke network we've got um
front door services,
which I'm just going to do front,
I'll do it front door.
For anyone who doesn't know what front door it is,
it's just like,
it's the part of the edge of the services that exist.
Um,
it's,
you know,
the services that need to respond to
to network connectivity
because then outside of that we've got like,
this is all terraform and we've got the internal network.
And this has things like.
Cosmos,
Redis,
etc.
and then
these,
these connect,
but like it's like a.
Virtual link rather than like an actual network link.
It's like,
it's,
it's a lot.
One of the problems as well is that
when it comes to the production environment that we own to deploy this on,
we won't
have,
like we will have access to like uh the Azure portal for the production instance,
but we won't have access to certain resources,
um.
They want to sort of,
when it's in a production environment,
they're like,
hey,
uh,
if you wanna touch data,
it should be touched with like a process or a piece of code,
it shouldn't be touched raw.
Uh,
so,
so that's fun
cos I,
I just updated the config yesterday,
so the
um.
So that all of these can now send
their data over to Application Insights,
which was like it was set up previously
uh but
just make sure it all goes to the same one.
It means that we can uh we can take a look at
that cos we should have even in in like the productions,
we should have full access to application insights
uh and that allows us to do stuff there.
Uh,
there's some added added complexity because this
hub network is the corporate network,
right,
I should just make it red,
right,
cos it not red there,
background red,
right,
it's really scary
uh cos there are other folks out here that we need to like maybe talk to.
um,
so like this might be.
Uh,
where are we?
Yeah,
this might be like
the
uh.
Business identity provider.
Like
LDA or Azure intra 365 copilot
ID
AI.
I do that because they keep renaming that product.
I don't know what it is right now,
but like it,
it was,
it was
Active Directory and everyone knows it's Active Directory.
Like if you speak like about like the 90s or,
or even the early 2000s,
everyone knows what Active Director is.
But then they renamed it to likeure Active
Directory or like Microsoft Actor Directory because they wanted
to position it more as like a cloud based
offering because Actor Directory like historically was sort of
enterprise on-prem solution stuff,
so they,
you know,
like they wanted to add the cloud stuff to it.
That was around the time where,
you know,
like cloud was big.
But then after that they realised like they were still
um maintaining some baggage from the active directory name like people didn't know
that it was like a new system,
it was global,
it was like,
you know,
um,
all the sort of words for for cloud scaling.
Scalable,
multi-tenant,
secure
cloud,
right?
So that's why they renamed it to
Entra ID,
but then
they sort of had a remarketing effect on the 365 namespace.
The 36 I namespace is meant to be sort of like
we have a solution for every part of your business
and,
Every part of your business is like,
you know,
this one product,
and if you just buy this one product,
your business will be 365 degree like covered,
so that's why
365 came back.
I don't remember what happened with Entra,
but it did need a new name to sort of differentiate from on-prem AD
uh and then of course they threw uh like AI in the end and co-pilot in the end,
so like it,
it's just got like 50 names right now.
But there we go.
That's how terraform one's been going anyway.
Good and bad,
uh,
particularly as well cos I haven't,
I haven't ran,
I haven't like ran a,
uh,
a deployment yet,
and one of the reasons there is that
this hub network has DNS in it,
but I don't understand how to register our own DNS,
right?
So what we need is like coming out of the hub network to our network,
we need like
uh
resinite.corpocorpofa.
Dot com.
Right,
we need a we need a domain
so that
um other people within the the corporate network can then talk to our,
our local cloud.
We're not like it's it's really weird cos it
sounds like an on-prem solution but it's not.
It's basically like
we take our stuff
like this,
which is our stuff,
and
we are,
we're making like a,
you know,
we're making like computer instructions to build it.
Within their larger network.
So
they've got a network which is like huge,
encompasses like all their business factors,
all their organisational schemes,
all of those stuff,
and
we're just sort of operating within it in like one
sort of floor of their office if you like.
So it's,
it's really kind of cool but also scary that like
Azure allows you to do that and we're being.
allowed to do it,
we've never done it before,
but uh I've I've had there.
There are multiple times during this terraform work where I just like,
I stop working,
like I'm not actively typing and I'm just
like scrolling through it and I'm just like,
hmm,
have I remembered to handle that?
Have I remembered to handle this?
And it's like,
yeah.
I'll get braver the more I read about it,
but like it's it's cool.
Moving forwards to the next question.
Is there any fans on the roadmap for saving your dashboard,
creating uh backups before editing your dash,
possibly making mistakes and having the only destroyed dash option remaining?
Yes,
absolutely.
Things like molecule,
uh,
the workshop,
the licence system,
um,
all sorts of things like that,
which I can
illustrate on the,
on the tech tree over here.
Those sorts of things all move us sort of towards,
um,
having
backups,
reloading,
change management on all things like that.
I would love it if like at some point we had like uh a dash screen manager.
Um,
it won't look like this,
but like it's a good analogy.
Like you know when you like,
on the original iPhone,
I think iPhones probably still do this,
I don't know.
The last time I saw iPhone UI they made everything transparent and ugly,
so I don't know.
But like you,
you held on the apps and then all the apps started
wiggling and you can move them around and uninstall them.
Do you remember that?
Right?
Imagine doing that with your with your dash screens.
It probably won't look like that,
but it's a good sort of visual analogy to sort of,
you know,
move around the dash screens,
relocate them.
Um,
and yeah,
I want this one before this one,
I don't want this one to exist.
I want a new one.
I guess we can put,
let's rearrange the wiki a little bit.
Uh,
I hold shift,
will it expand horizontally?
No,
I just,
I just want to expand horizontally guys,
I don't want to expand
shift,
no control,
nope,
not control.
Oh,
no.
OK,
we'll just have to do this manually.
OK,
there we go.
So what I wanna do
is,
you know what,
just go over there for a second,
I'll I'll use your back.
Uh,
fix,
not dicks,
fix
wiki Docker setup.
I do actually want these to be a little bit bigger.
There we go.
Now this is in progress.
I haven't made any progress on it in the last like week or so,
but that's cos I like had to,
you know,
learn terraform and then write stuff for.
Oh yeah,
we kind of need
uh another item here that I'm working on.
This is
um.
So that's big.
Like what's what's going on there?
Why is that huge?
There we go,
we'll just,
this is why I usually copy and paste a box because like it has the right settings on it.
Uh,
so what's going on here is a while ago,
we made it so that all assets,
um,
are
stored and sort of,
uh,
collated on cloudflare
using cloudflare R2,
because for resinite that's a lot cheaper.
Like it's,
it's,
it's a really good cost effective way.
We don't pay,
I always forget which one that we don't pay for,
but we even don't pay for ingress or egress,
um,
and that's great.
But for,
for this environment.
That we're building,
um,
it doesn't make sense to like add another
um provider
because that other provider,
Cloudflare is basically another box.
That we then have to like
talk backwards and forwards to,
and
also the corporate company has to pay for,
um,
and so I had a like brief conversation with them and
like money is different when you're a big corporation,
they're like,
oh we don't really mind.
So
we're just shoving them back in Azure,
um,
but
the way that I'm doing this means that,
well I have to do it because we'll be running resonate cloud and um
this Corpo cloud.
We have to do it so that both are supported.
So what this actually is,
is sort of like
um
like a a small cloud flare asset tidy up as well like.
And the tidying up will be mostly sort of making sure that like
configuration can switch between them so that when we deploy
the
the cloud as the cloud code for Corpo,
it goes yep,
sure,
and we deploy the cloud code for resin,
it goes yep,
cloud play,
great.
Um,
this also will allow us to do in the future,
um.
Because we're extracting it,
it'll be a little bit easier um to do like other providers.
There's this uh provider
called,
here it is.
This is uh Echo 3D.
Echo 3D is a uh the easiest way to understand Echo 3D is,
um,
it is
sketch fab
but like Corpo.
I don't like what I'm seeing on the right here cos this looks like an NFT collection,
but we're just gonna ignore that.
We're just,
we're just,
we're gonna ignore that,
um.
Oh,
here you can see this is much better,
right?
So what they can do is they can have a centralised manager for assets
like
products,
things like that,
that is in Echo 3D and then Echo 3D can do like all the permissioning and stuff.
The reason why they're doing that is because we don't,
like we don't have
like a enterprise
asset sort of retrieval management permissionee system yet.
And so Corpo are looking at exploring this as as potentially a way to do
that faster,
but I,
I don't know.
But because they've sort of,
you know,
part,
oh,
we can do splats.
It can do splats.
Deploy on your company,
and this is the other reason,
right?
Um,
it'll be like,
hey,
deploy on your company.
Uh,
they got like a picture about the commissioning.
I,
I don't know there's there's there's something somewhere about like,
hey,
like,
you know.
Um,
the
Group A can't access this,
this car model because they're not allowed to or whatever.
Um,
so,
so that that's good to look at.
Anyway,
back to the,
back to,
we'll make this one orange,
um,
and we'll also make that line
dotted because it's like,
here,
we don't know if we're gonna do that,
but we're keeping it in mind.
Moving forwards,
on-prem AD is definitely my preference,
uh,
TBH is fluffy.
I'm having this like really weird problem
in like
computing now where for a while.
like when the cloud came out,
it was like,
yeah,
we'll just just move everything to cloud,
but now everyone's like,
hey,
if we do move it to the cloud,
we want to avoid something called vendor lock-in.
Vendor lock-in is where like you
tie your
um architecture and the way that you,
you know,
built your application or your service
so closely to the particular vendor that you're running the
software on that you can't then move it elsewhere and
then before you know it,
it's like,
hey,
we've been on for 10 years.
It's like
day 140,000 on the on the
big brother house.
We're still stuck in in
we're still stuck in Azure.
So I do keep that in mind.
There is some exciting things going on in the land of terraform,
but also in the land of .net aspire,
I don't if anyone's heard of.net Aspire,
that are like trying to sort of
fix vendor locking.
Um,
it's something that we'll have to more largely sort of handle in the future,
but,
uh,
we,
we're good for now.
Off the back of vendor lock-in comes like
weird stuff where it's like,
oh,
so to avoid vendor lock-in,
we should
go completely to on-prem,
right?
So let's buy a server room,
let's put some server racks in there,
let's deploy bare metal services,
and then we'll avoid vendor lock-in.
Uh,
and that's like the bad move.
Like I wish we would go to like the hybrid thing where it's like
all of our software is made
sort of,
um,
abstracted away from that.
Like,
so
a good example might be
if we do like uh
let's do like database retrieval.
So
we have a database
and this is like an Azure database.
And then we have
our business logic.
This is like when we say business logic as a computing term,
we just basically mean what's unique to your code,
cos everyone,
everyone queries in Azure database.
Everyone queries one.
Like it's just universal.
Some sort of database you query it.
But the business logic might be why are you querying it?
Like what business goal are you trying to.
To establish with that.
And so you might write code in this business logic that,
you know,
directly talks to the Azure database.
It uses the Azure APAI,
the Azure SDK,
whatever you're talking about there.
But that means that like,
hey,
if this suddenly is like an AWS database.
Or like a Google Google Cloud platform database,
this this link doesn't work anymore cos like they can't talk to each other.
So,
oh,
that went,
what you might do instead is you write a abstractor layer.
This is usually like interfaces or like config,
service discovery sometimes.
And
your business logic
talks to that abstraction layer and then your abstraction layer can
figure out
where to go.
And that's how you sort of avoid vendor locking.
The solution for vendor locking that I'm trying to illustrate is not
to panic and put your stuff back onto bare metal services,
it's to
think
like differently and think,
plug and play.
You know,
when you move houses or you move apartments.
And you move your computer,
you just plug it into the wall,
because like,
a long time ago,
I mean I know each country's got different rules,
regulations and er socket types,
but like,
hey,
a long time ago,
everyone was like,
this is stupid.
Every single plug in America or Europe or whatever looks like this.
Wherever you go,
you can plug something in.
You'll see
similar stuff going on here,
right?
We have,
currently we have vendor,
we have vendor lock-in in our asset retrieval.
Um,
it is locked
like explicitly in code into cloud flare is where the assets go.
Um,
you know,
data management isn't Azure,
and we're sort of
editing that.
There is,
thankfully like fruits planned ahead.
There is a lot of existing code there.
It just needs like a little little tidy up a
little like rejigger to be configurable and and manageable,
and also to get some updates that sort of cloud fair branch of
the code has that the Azure branch of the code doesn't have.
Um,
moving forwards to Fufi's question,
are there any plans for some kind of in-game wiki browser?
Yeah,
we wanna get sort of in-game documentation going,
um.
Like browsing the wiki like in its entirety is
difficult cos that usually requires like all of the,
the HTML landscape,
etc.
So I'm not quite sure like what form it will take,
but yeah,
we want to get documentation into.
Into the game in some form.
Osey says,
do you know exactly what happens when you upload variants
after saving a newly uploaded texture if they're being uploaded?
Why doesn't spawning out the new resDB of the texture have not have the variance?
Why doesn't spawning out?
Why doesn't spawning out the new resDB version of the texture not have,
could you rephrase your question OC,
there's a bunch of like.
Negative,
positive swapping and
logical contrition.
It's like,
what happens when,
if they are being uploaded,
why doesn't spawning out
not,
you see what I mean,
it's just,
there's too many like,
there's too many like negatory statements and it's just like I
don't know what I'm talking about apologies for that one.
I love the little grabby hand it's like
got your nose.
I was freaked.
Uh freaks more to the left usually.
Yeah we go.
Got your nose.
All right,
what I wanted to do was go back here.
And we will
do that
cos like we don't know if we're gonna do this,
um,
it's just like,
what this is another thing with like Corpu and stuff like that is
like they're always having conversations with like random
uh companies and providers of software
and in some cases like they don't even know what they want.
Um,
it's just sort of part of the,
the corporate stuff is
is doing that.
Actually,
we'll we'll save these.
This is an infinite canvas,
by the way,
we can just like keep panning,
so we can,
we can save some of these like explanatory diagrams like over here,
just in case we need them.
When I'm exporting for the wiki,
I'll just,
what you do is you like can just highlight and go export.
All right,
Ozy has reworded the question.
You don't see the newly uploaded variants on the ResDB version you spawned out,
and I'm wondering why.
Does the cloud do some checking on those uploaded variants,
and that's why it doesn't show you the variants that you uploaded.
Yeah,
so there's um,
when you load in the asset,
like
the fir I don't wanna say the first time cos like the first
isn't like the appropriate like terminology,
it's just like when you load in the asset
and it's a particular like state,
um.
The engine will
query
your local and probably get some of this wrong,
so like don't,
don't write like a scientific paper on this because it's rough,
but
you.
The engine queries the local database
and then sometimes the cloud,
depending on like which is update,
uh,
to find out what variants of that particular asset are available,
and then it will try and sort of figure out which is the best one to use.
If you are generating the assets at the time that it's loading,
they might not be available.
Um,
so I guess like an easy way to figure it out would be do that,
observe the behaviour that you're,
you're questioning me on.
Um,
shut down resonant completely,
wait 10 minutes,
and then reload that world,
and it'll probably have the variants because they'll have been like generated,
uploaded and synced.
But I think it's just like an order of operations thing,
right?
It's like,
hey,
this is being generated so we don't
necessarily have those um
those variants right now when it's being loaded and we might have them next time,
stuff like that,
I think.
Speaking of that,
I think,
um,
yeah,
one of these spikes here,
um,
is Rauvi uploaded a carrysmo map or like a Half-Life map,
and that's one of these spikes of the asset system.
It's like we had some connectivity issues here.
You can see that it was just connectivity because the the numbers didn't change,
right?
We didn't go
from up here
down to like here,
which would be like,
hey,
the,
the service crashed,
we just like had a blip of connectivity.
And then it came back at the same rate.
I don't know why,
but I'm just imagining like a platforming game with like Super Mario woo.
Alright,
that's all the questions we have.
We are at 1:30.
Are there any additional questions?
I do have all the bells and whistles available right now.
Do we have,
oh,
we do,
we do.
Dios are asset variants stored as diffs or something,
no,
they're stored mostly as like raw binary blobs in blob storage.
In this case cloud player like I was saying,
like down here.
So what you have actually,
I realised like I'm so like oh so powerful,
look how many diagramming tools I can do,
um.
No I want middle stroke with hard stroke,
no background.
So let's say we've got like cat.
PNG.
Then
we might have
cat.
PNG but smaller
and then
cat.
PNG but.
Compressed
And there is a relational mapping
in,
I don't remember which variety of databases,
but there's a relational mapping,
um,
and an API that says,
if I look up cat.
PNG in the asset system,
and I say,
hey,
uh,
list variants available.
Then it will,
it will pull and be like,
hey,
look,
there's this variant available,
it's smaller,
and there's this one available and it's compressed.
Osey says,
have you been interesting oh that's how that works
when it comes to freaks engine stuff of late.
No,
not of late.
In terraform,
yeah though,
um,
let me see.
I have to be careful cos some of the terraform stuff like has the,
the name or some like company specifics that exist for
uh the project.
Where are we,
here we are.
All right,
if I don't leave this file,
we're good.
I'm not Satan.
Uh,
I guess we can,
we can swap Window.
How do I change what I'm streaming?
Oh,
there it is.
OK,
change,
change stream.
Here we go.
Uh,
so this is the,
the data configuration for the,
the terraform block,
and you could just like,
it's,
it's
so soupy.
Like,
it's Jason with extra steps.
So this bit is the cool bit
um
down here.
We have
um a bunch of Reddit caches for doing various caching,
and there's one that is used for signal our back uh backbone as well.
And
what we would do historically is we
would shove those into like environment variables,
but now because of this terraform stuff,
it's like,
hey,
create a key volt,
so we create a key vault.
Uh we set up a private endpoint
security stuff.
And then here this block
makes a
key volt secret
for each of these that is labelled correctly
and has the uh value from
um
from.
This redd connection thing,
and if you look at redd connection thing,
it's basically a string format
that takes the port,
the primary access key and like smooshes it together into um the
like
connection string style structure that you'd see if you did a
PHP MySQL setup back when you were a kid in your,
in your bedroom.
You'll see that sort of thing.
Uh,
so yeah,
uh,
we'll call that the,
uh,
interesting,
oh,
that's how that works.
I could also for loop
um where is the blob storage?
Here's the blob storage.
Uh,
so this is blob,
um,
you can see this is fast blob.
cos if you're still there,
I don't know if you are,
it doesn't matter either way,
don't feel bad either way,
but this is why I was asking you about it,
right,
cos we've got fast blob of blob,
uh,
and we'll be making a third one called Asset blob.
Blob.
Um,
this is the stuff that I need to,
I need to look in like account tier,
account replication type,
there's,
there's more stuff elsewhere as well,
um.
I
it's not that I don't like it anymore cos like I,
I don't have a choice really,
but it's just like
looking at terraform code,
it just like most of it is just like useless.
Like,
here's one of the things I hate,
right,
it's like,
hey,
I've every single time I make something I have to inform the something.
That it is located in
this Azure region,
which is a variable that we can pass in from,
from Corpo.
Um,
we'll be hosting most of our stuff for Corpo in Sweden Central.
I didn't know that there was a Sweden Central data centre for Azure,
but I do now.
Uh,
moving forward,
we've got some questions,
so that's.
Uh,
I've noticed and generally appreciate a hesitance towards
band-aid solutions for architectural problems like crashes,
but I think maybe it's reasonable to say a UTC
platform like Resina is always going to have some potential for
sudden unknown crashes and hangs.
In the case of things like the headless software where wow wow.
Where a watchdog command already exists for external software to do
something to kill it to bring the server back up.
Where
uh does that line tend to get drawn between useful
platform reliability aid and hacky band-aid to be avoided?
Uh,
Watchdog is like a holdover from,
from the Dark Ages.
Now Watchdog's been there forever.
You can see the sort of non hacky band-aid solution starting
in um the
Frugs is looking at,
I think they're posting some stuff in the devlog a while ago,
at looking at restarting the,
the renderer.
When the renderer crashes,
um,
I think Frus's phrasing is something in the lines of like
when
residite crashes,
it doesn't crash.
But that's the sort of same thing as as the watchdog,
right?
It's like the,
the non-renderer part of resinite,
the Fruuxing process is like.
Yo,
the renderer crashed.
I'll restart the renderer.
That's it's like similar to the watchdog,
but it's like,
it's gonna be the correct way of doing it,
right?
The,
uh,
fruits and process goes like,
hey,
I can't speak to the renderer.
I don't know what's going on.
Something's bad here.
I will take action and fix this.
As for other cases,
it,
like,
a lot of the like hacky band-aid versus like,
proper,
like fixed solution
is something that like
takes time and experience to.
Um,
figure out
and,
and learn the difference between.
And that's what we get a lot with sort
of mod developers or like hobbyist people who are,
you know,
poking around in our code.
They're like,
oh,
it's real easy,
you just have to like change this one thing.
Whereas like Fruits,
myself,
the rest of the team and the engineering side at least,
we have to sort of think,
is this the best solution,
what would the best solution be?
Would this solution that we are now saying is the best solution take longer,
shorter?
You know,
like what,
what is the,
the cost benefit analysis.
Some cases,
and we try to keep these as minimum as possible,
we are um sort of
controlled or or affected by business requirements,
um,
that will come up in the in the.
Next
question,
of course,
so do wait for that.
But um we just,
we try and do the right thing and what we try and do is we try and do a decision
which means that in
6 to 12 months,
the next engineer that touches that piece of code doesn't groan.
I'm very much a person who's just like trying to make code.
That is
pleasant's the wrong word,
cos like code can't be pleasant all the time,
but like code that is comfortable to touch is like my goal,
right?
It's like I know what this code does,
it's using the best practises,
it's using the best techniques,
it's not hacky,
um,
and I know how to touch it and I know how to edit it.
But it is really difficult.
Um,
we could do a better way of sort of indicating or explaining that in some cases,
so I get it,
like it's a common question that comes up.
Um,
it's also a common thing that happens when.
Uh,
like other engineers that aren't freaks,
like they try and quickly fix something,
and they haven't realised like,
oh yeah,
that's like a rabbit like fixing that one
particular error is gonna be very difficult.
But those times are happening less now,
and there are some features where like
there's like a,
I don't know,
like a tiny fruits
sitting in my brain sometimes.
And like when I look at a piece of code or I look at a desire that I have for the code,
um.
I go,
like there's little fruits inside my head goes like,
oh,
but if you touch that,
you're gonna have to touch this and that and this and that and this and that and
that and that and that and that and it's gonna take hours and days and months.
And I go,
thanks tiny freaks in my head,
I'll find something more productive to do.
Sometimes you have to like
stomp on the little freaks in your head and be like,
shut up.
Corpo's paying for this,
they've been doing it.
But in that case,
at least you're not like squishing actual freaks,
you're just like battling with your self doubts.
There is something that I'm learning to do as well.
There was a period where like I was on engineering um at resinate and
I would like not be able to work cos I'd be paralysed by like,
oh what well like is this the right way to do it?
Like what would,
what would folks think?
Like that's still there,
but like uh it's we have to make forward momentum.
So I would rather work make code that is like
80% of the way there and have fruits come in and be like,
You've forgot these two things,
and we go,
yeah,
fine,
thanks.
Uh,
moving forwards to fluffy.
Fluffy said,
I remember seeing an interaction on Discord between you and one of the Resant
users who used to be some kind of terraform administrator for his job,
but quite a few negative anecdotal things to say about terraform.
Have you had a chance to sit down with that user and plan your terraform approach
to resonate that can avoid any common pitfalls
that person may have experienced in their career.
Um,
no,
that's also not planned.
The reason why that's not planned is like terraform wasn't my first choice.
Um,
my first choice would be some other thing.
I don't even know what it is now because like it all
left my brain when I realised we needed to do terraform.
The company that we're working with requires terraform,
like all of their existing,
um,
other like things.
That they've got working on their sort of enterprise cloud use terraform.
They've got things like policies and security that run on terraform.
So what will happen,
I realise I'm still sharing my screen,
I should probably switch back to the the tech tree.
But like their policy will look at this,
which,
like,
it's basically Jason,
right?
So they look at this,
which is basically Jason.
And they're like,
oh,
we have internal policy number 4382,
it means that every private service connection needs the cheese qualifier set to 4,
right?
And so it will come in and then it will make a PR
and it'll be like the cheese modifier must be set to 4.
It is company policy that mandates it,
and then we'll accept that PR into probably their branch of of the terraform files
and we'll be compliant with their policy a lot faster.
I was actually looking at one of their documentation pages and it linked to
the service provider they use for that policy thing and that advisor thing.
It's something like called AZ Advisor.
I don't know if that's the name of the company or the tool,
I don't know.
I was just on a link called.
A uh AZ Advisor and it was like this huge,
it looked like a a a CV reporting website,
you know,
where there's like so much data but like none of it's useful,
like on a CVE reporting website.
This is the same thing with this policy website.
I was scrolling around forever and then I found like the
the terraform
like diff that needed to be applied.
I was like,
OK,
now I understand what they're doing here.
Um,
so to some extent we're we're stuck,
like we have to use terraform.
I'm
OK with that,
and the reason why I'm OK with that is because there
are a lot of cross infrastructure as code generation tools.
So I should be able to in the future,
throw this terraform code at a um converter and say,
hey,
I want,
was open tofu,
someone was speaking to me the other day.
Open tofu,
bicep,
uh Kuberneta use,
like whatever you might need,
we will be able to generate it a lot easier once this one solution works.
So it's like,
it's not intentional,
but we're not having a conversation with that user,
it's just,
it's not,
sounds this sounds so bad,
it's not relevant.
Like it is relevant,
but it's not relevant to the the project,
right?
There is a deadline on this project as well.
um,
it is end of March next year.
So we we're totally fine,
right,
but I can't,
I can't be lax,
right?
End of,
uh,
gee,
switch back now.
End of March next year
needs to be,
uh,
here,
this one,
I guess we'll make it red.
Like that's,
it needs to be end of March next year,
we need to,
we need to have that going.
And it doesn't need to be production,
it just needs to be a demo,
like a,
a proof of concept.
So,
you know,
I'm over here
and I need to get there.
So there's,
there's a lot to do.
Right,
uh,
I think that's it for now.
I,
I don't see any additional,
sorry,
I don't see any additional questions.
Uh,
I'm gonna leave off here,
uh,
go open those terraform files.
What I need to do today?
Oh yeah,
I need to write,
where is my diagram?
I need to write a ticket
to the
Corpo team.
Yeah,
I need to write the tickets to the corpo team to figure out how this works.
Because you know how right now if you open up Resinite.
You'll see requests going to API.
resonate.com,
assets.resonate.com,
and probably a few hours I've forgotten there,
right,
but
those all need to be like corporate corporateface.com,
and I,
I don't know how to set that up.
There's probably some form of like button I need to push
in an Azure panel or terraform block I need to do,
cos one of the things in Terraform that you
can do is you can export and import resources,
so.
The terraform files might
set up all of this.
What I can do is I can like import it and be like,
yo,
I need this from like another location
and import it,
and then I can,
I can maybe link them up that way,
but I don't know.
And that,
that's something I need to understand.
Otherwise,
I have to configure
their copy of,
of,
of Resinite to be like,
ah,
yes,
API.ressonite.com is like 88.1 blah blah blah blah blah blah blah blah blah blah,
blah blah blah,
slash users slapro,
which is like,
it's not good.
So yeah,
I think that's it.
I will speak to you guys uh
soon.
I will try and get this tech trait on the wiki,
uh,
I think I'm a couple of weeks out of date on that.
Uh,
I do need to move back to my
supplementary diagrams.
Maybe I could just throw my supplementary
diagrams on like another wiki page and then
people can take them and put them where they want,
cos like even this here,
showing like all the things that Modyle
could or is planned to do,
mix them both there.
Uh,
it would be good to sort of log.
I don't these have arrows,
they should have arrows.
Alright,
yep,
see you soon,
bye bye.