great

11:18 - It's a little bit ugly.. Me: YEAH!! Was thinking about it this whole time!

{ "errors": [ { "message": "x-hasura-admin-secret/x-hasura-access-key required, but not found", "extensions": { "path": "$", "code": "access-denied" } } ] } Hi how to resolve this error in hasura

I think the pulumi refresh probably can fix this as well?

your course of pulumi is very very helpful! thank you very much :)

Super important concept to know! Thanks

Can you provide an easy Pulumi course from scratch, please

i just have one question why r u coding on white theme

Great info and easy to understand. I have been using Pulumi at my company for about 6 months now and OFTEN use the apply and all methods. Ive seen my coworker use the interpolate function but didnt understand why until now. Thank you!

Wow, it was so amazing and it is such an Underrated Channel

So useful thank you

Damn, your videos are nice!

Nice video thanks

Thanks for this great series of videos. Your an excellent teacher and communicator. I know this is two years on, but please can you continue the series. You were about to talk about dynamic components.

Can you pass config through in the constructor of the dynamic provider instead of the props? That way credentials and such won't need to be stored in the state.

Still relevant, especially considering Terraform switched to a Business Licence 3 days ago 😢

the best hasura course out there, finished the playlist today and learnt so much through the journey thanks very much 😘😘😘

This is sharp stuff! really clear and insightful

I have hit the problem described here at 38:32 about accessing stack config from inside the dynamic provider. The solution in the video is to go the resource and pass the config in as an input to the provider. But what about when the endpoint changes? The changes to the config file will not be reflected in the currently-instantiated-resource in the stack, because they are "cached" as inputs. So when the endpoint changes and you run `pulumi up`, Pulumi will not be able to delete the original resource anymore (because it will try to access the endpoint that was configured when the resource was created, not the one that is currently in the config). Same issue is with credentials. Those are expected to expire regularly and should not be kept as a part of the stack.

Solid video! Really shows the value of Pulumi!

So good! Exactly what I needed

Would love a tutorial on creating a native pulumi provider with Go, the Pulumi team have sucked pretty hard on developing decent docs on creating native providers!

It would be great if you made a git repository & put the codes that you use in videos in that repo, so that we (students) not focused on writing python code, but focus on pulumi hints, commands and tricks.

Thanks a lot for the awesome videos!

Great series of Pulumi fundamentals.

I like your videos!!! Would like to see more videos, please keep them updated ❤

Top Video! I wrote a prvoder bevor, i wish i view this first

These tutorials are better than even the official ones by Hasura. I hope you are able to monetize your channel. Not sure why you have stopped posting, please continue posting!

Thank you for the demonstration. Auth0 was always ambiguous concept, finally cleared.

this is the best tutoriel on Auth0, it removed a lot of ambiguity that I have around it/

prisma could be more intuitive as postresql ORM for event management,

thank you for the summary I get a bit lost starting using Hasura CLI... carry on the good work : always someone , somewhere and someday will search for your upcoming tutorials and will find it as life saver !

best hasura and graphQL complete walkthrough, more in depth complex web development topic !

This is brilliant. Thank you so much for putting this out!

Excellent 👍. This content should reach more people .

Great tutorials. Worth to subscribe your channel

Amazing tutorial thanks. I'd love to see best practices to apply to staging and production. And also could mention squashing migrations too.

Nice video, thank you! Unfortunately you didn't show how to keep migrations and metadata in-sync manually. Hasura documentation around migrations and metadata sucks. Each command should have explanations on what it affects: local files, metadata files, metadata table, etc. No word on that and you can only guess or experiment yourself. E.g. after a down migration you have to restore consistency between both "sources of truth". Hasura will rely on metadata which now may describe removed tables, columns, etc. How would you fix that? Editing metadata files and applying them with 'medata apply' (like it's shown) is error prone - you can easily introduce a new mismatch that will be even harder to remove later. There's 'metadata inconsistency drop' with many other commands. None is properly documented. Now add bugs to the mix. E.g. 'metadata export' does not remove table descriptions that were removed. And now you see why the entry barrier of this tool is still way too high. It takes weeks to learn (which is worth it, IMO, but not all developers or teams have that much time to invest).

thx for the video )

plz make more advanced videos on this

I found this to be extremely valuable, thanks for taking the time.

Thanks for this video! ☺

Really good learning material 😄 Watched the first 7 videos of the series and it was very helpful. Well done 👏

great work

Failed setting foreign key i got this error while setting up foreign key for the type

admin scret should como from .env files

Excellent series, thanks 🙏

Incredible tutorial, thank you. Not sure if it's a latest-update from Hasura, but I didn't need to mark my initial migration as already-applied. It was already marked in the migration history it seems(?). Regardless, fantastic job explaining this. The official documentation should just link to this video :-)

Hey I just recently found these, you should make more videos! You are very succinct and to the point and its great

I get "password authentication failed for user "postgres" error. Any help?