[Portuguese] Automate away the toil
32:25
16 сағат бұрын
[Portuguese] Engenharia reversa com Terraform
22:43
Revolutionizing vSphere VM Access
18:52
Using Terraform with Azure
1:14:43
Күн бұрын
Using Terraform with AWS
1:16:18
Күн бұрын
Using Terraform with Google Cloud
1:17:08
Adventures in generating HCL
10:41
14 күн бұрын
Пікірлер
@HasanSattarr
@HasanSattarr 6 сағат бұрын
can you share any video tutorials resource where I can learn terraform CDKTF step by step ?
@antoniothomacelli
@antoniothomacelli 15 сағат бұрын
Thanks for sharing, this content helps us to build the correct Internal Developer Platform, too many companies solving this by creating their own IDP, but Backstage is attractive nowadays
@FredLinhares-x2e
@FredLinhares-x2e 2 күн бұрын
Muito foda o desafio enfrentado (e vencido!). Parabéns também por compartilhar a questão da Neurodivergência.
@ClaytonCavaleiro
@ClaytonCavaleiro Күн бұрын
Obrigado :D
@RT-.
@RT-. 3 күн бұрын
So, practically, what does an employee install and configure on their computer to have access?
@JaredHolgate-i1f
@JaredHolgate-i1f 9 күн бұрын
Hi Nic. Fantastic content, thank you for creating this. In a future iteration it would be great to point out that we strongly advise against using a Client Secret for real world workloads. We recommend using OIDC (Workload identity federation) or failing that a managed identity. This removes the need to manage and rotate a secret. If developing locally you can just use the az cli, no need to create a service principal (app registration). Thanks again for creating this.
@justinclayton42
@justinclayton42 10 күн бұрын
A fantastic demo. Thanks for all the work you did here
@edmaregs
@edmaregs 11 күн бұрын
Could you make use of terraform hooks to check the status of the init cloud config ?
@NicJackson
@NicJackson 10 күн бұрын
You could yes, hooks post apply to check the state of your application and then use this to report back to something like Slack, Discord, etc. However, this is a more complex topic than I wanted to cover in this video and it would also require HCP Terraform or Terraform Enterprise. If you would be interested in a video on using Terraform hooks, let me know. Be happy to cover this. For folks who are not aware of hooks, I have linked the docs below. developer.hashicorp.com/terraform/cloud-docs/agents/hooks
@dus10dnd
@dus10dnd 11 күн бұрын
Can we have some final decision on Stanza versus Block? I have witnessed a few more mentions of "Stanza" with respect to Terraform than I generally have seen. It usually seemed limited to folks that first used Consul or Vault.
@NicJackson
@NicJackson 10 күн бұрын
Personally I use the two interchangeably, traditionally all HCL blocks such as resources were referred to as "Stanza", this was not limited to Terraform but covered all tools that used HCL. I have just checked, it seems that we do not use the term stanza from the current documentation. I am guessing this is to simplify the language and use a term more commonly used with code. It was Terraform that first introduced me to the term Stanza when I started using it almost 10 years ago, the phrase has just stuck. Sorry for any confusion, I will try to stick to the word "Block" for future videos.
@dus10dnd
@dus10dnd 10 күн бұрын
@@NicJackson You’re fine, it was just an observation. I really appreciate the background!
@NicJackson
@NicJackson 10 күн бұрын
@@dus10dnd I appreciate you calling this out, it makes things clearer for other viewers. Hope things were useful.
@JudgeFredd
@JudgeFredd 12 күн бұрын
Great info
@JudgeFredd
@JudgeFredd 12 күн бұрын
Great information !
@matclarkcybersec
@matclarkcybersec 12 күн бұрын
Music opens up very loud
@HashiCorp
@HashiCorp 10 күн бұрын
Thanks for the note and sorry about that, we'll do a better job next time! 👍
@HoussemDellai
@HoussemDellai 14 күн бұрын
Very nice initiative to reach millions of Arab engineers and students. شكرا
@JudgeFredd
@JudgeFredd 17 күн бұрын
Great information from the source
@GurpreetKaur-qb9un
@GurpreetKaur-qb9un 17 күн бұрын
Great Stuff! Thanks for the informative session on Vault Events. I was trying to enable it on my local system by running the command "vault server -experiment events.alpha1" but it says that I need to specify at least one config path by using -config. Any suggestions! Thank you :)
@HashiCorp
@HashiCorp 16 күн бұрын
For that specific use-case, I'd suggest heading over to the Vault Discuss form: discuss.hashicorp.com/c/vault/30
@DimiterStanev
@DimiterStanev 17 күн бұрын
Thank you!!!
@rameshwardwivedi2945
@rameshwardwivedi2945 17 күн бұрын
It was very informative session nicely explained by Rose 🌹 and thanks to Cole for organising such a wonderful meeting.
@bonito1998
@bonito1998 19 күн бұрын
Thanks so much for the video , brother you saved me a lot of trouble
@harshananayakkara4854
@harshananayakkara4854 20 күн бұрын
Hi, I have a a Kubernetes Cluster and a Nomad Cluster. I also have a single Consul Server installed in a VM outside of Nomad & K8S. I want to achieve workload load balancing / failover between K8s and Nomad. So in this case as I only have 1 Consul Server (since this for test purposes) can I still make use of Consul WAN Federation between the 2 clusters or else what path should I take to achieve my expectation. Thanks!
@HashiCorp
@HashiCorp 17 күн бұрын
If you want to keep a single Consul cluster but allow other runtimes (k8s, nomad) to join the cluster, you can use Admin Partitions ( Consul v1.11+) [developer.hashicorp.com/consul/docs/enterprise/admin-partitions]. This feature allows operators/admins to configure Consul with a single cluster control plane (Consul server on VM), while allowing multiple tenants from other cluster run-times to join the Consul cluster. Nomad 1.8 [www.hashicorp.com/blog/nomad-1-8-adds-exec2-task-driver-support-consul-api-gateway-transparent-proxy] now supports Admin partitions. Then you can use something called Consul sameness groups [developer.hashicorp.com/consul/docs/connect/cluster-peering/usage/create-sameness-groups] for failover between the different tenant partitions. Here's a demo video [kzbin.info/www/bejne/amnXp4N5r6mhjpI] using sameness groups for failover. The video shows sameness groups between two separate Consul clusters that are connected (via Cluster peering feature) , but sameness groups can also be done between two tenants of a single cluster.
@harshananayakkara4854
@harshananayakkara4854 17 күн бұрын
@@HashiCorp Thank you for the reply. However, I notice that Admin partition feature needs an Enterprise license. Therefore, for only testing purposes is there any alterative approach (without any licensing requirement) that I could take to realize my objective. I assume without the Admin partitions it is not possible to have a single Consul cluster like I previously mentioned. So, I believe in this case I have 02 options; 1. Have 2 consul DC clusters in both K8s and Nomad (servers) and use WAN Federation between them. 2. Setup Primary Consul DC in Nomad and connect K8s as a Data plane. I sincerely appreciate your advice. Thank you!
@HashiCorp
@HashiCorp 16 күн бұрын
@@harshananayakkara4854 I'd suggest heading over the other Consul Discuss form to dive into this deeper: discuss.hashicorp.com/c/consul/29
@karlkeskyla
@karlkeskyla 22 күн бұрын
Great talk, thank you!
@Bekdorj
@Bekdorj 22 күн бұрын
많이 배웠습니다
@KPreddiePWSP2
@KPreddiePWSP2 23 күн бұрын
How timely
@harungadatia1030
@harungadatia1030 25 күн бұрын
Is there support for events subscription via vault agent side car in kubernetes?
@HashiCorp
@HashiCorp 22 күн бұрын
Events have not yet been enabled for subscription by the Vault Agent, but it's on the product roadmap.
@harungadatia1030
@harungadatia1030 21 күн бұрын
@@HashiCorp Thanks for the reply. We are looking forward to this being available as we heavily use vault agent side car and if vault agent can update the static secrets based on an event instead of the polling via ttl in the path, that would be great.
@wikiaudio956
@wikiaudio956 26 күн бұрын
so i wanted my app to use vault, so i still have 2 places with secrets, vault and the place where my app has the access credentials to vault or am I overseeing something? is it really only 1 place with credentials if you use vault with the other products like consul?
@HashiCorp
@HashiCorp 22 күн бұрын
In general, the only place the secret should live is in Vault and the app accesses it from Vault secrets engine when it needs it. To dive deeper, we recommend you post on the Discuss board here: discuss.hashicorp.com/c/vault/30
@igstan
@igstan 26 күн бұрын
I'm quite puzzled about the purpose of the generic resource modules, the ones imported from the git submodule. At a first glance they're one-to-one mappings to hashicorp/azurerm resources, effectively duplicating their structure. The differences that I see are: 1. This extra layer hides some arguments exposed by the hashicorp/azurerm resources 2. It might provide some defaults for what would otherwise be required arguments in a hashicorp/azurerm resource 3. Sometimes they use `for_each` and `dynamic` to cater for repeated arguments in certain hashicorp/azurerm resources However, out of 33 "generic resources": ``` find . -type f -name '*.tf' -not -name variables.tf | wc -l ``` there are only 10 `for_each` occurrences in 7 files: ``` find . -type f -name '*.tf' -not -name variables.tf -exec grep for_each {} \; | wc -l ``` ``` find . -type f -name '*.tf' -not -name variables.tf -exec grep -c for_each {} \; | sed -n '/0/!p' | wc -l ``` Now, as if this wasn't enough, he's also parameterizing the resource instantiations with locals in his root module, effectively introducing yet another no-op layer. At the end, the two layers don't seem to add much value. If they do, I fail to see in what scenarios they would add that value. In any case, I'm positive they don't _always_ add value. The final idea, of using maps and lists based on which resources get generated is definitely useful, but that's obviously possible without the two indirection layers (or one depending on how you count).
@ravidsinghbiz
@ravidsinghbiz 28 күн бұрын
When can we expect part 2?
@boshkovboban
@boshkovboban 28 күн бұрын
So, the whole benefit over the open-sourced Packer is that introduced Packer Registry where you store the Metadate and control the Image versioning from there, instead doing it from AWS/Azure? In your terraform script instead of reading it from Azure/AWS, you are going to read it from Packer Registry. Any other benefits?
@HashiCorp
@HashiCorp 23 күн бұрын
The HCP Packer registry has multiple benefits to help you build a golden image pipeline and manage image lifecycle, including: - Metadata tracking for all your image artifacts and versions across multiple clouds - Channels that make it easier to promote and discover the right image versions to use - Ancestry tracking for parent/child image relationships - Revocation workflows to make sure old image versions aren’t being used anymore - Integrations with HCP Terraform via run tasks, drift detection, and continuous validation - Audit log streaming to monitor image activity You can learn more at the links below, or check out this on-demand webinar: www.hashicorp.com/events/webinars/ep4-securing-your-infrastructure-with-terraform-and-packer-creating-a-secure-gold www.hashicorp.com/products/packer/features developer.hashicorp.com/hcp/docs/packer
@latheefp2001
@latheefp2001 Ай бұрын
from which file in repository , i can refer the command to create vault policy, key, auth and role creation steps,
@rosemarywang5465
@rosemarywang5465 Ай бұрын
The configurations were not moved into the repository but I have a similar example (configured using Terraform). Kubernetes auth method: github.com/joatmon08/hashicorp-stack-demoapp/blob/hashiconf-eu/vault/setup/auth.tf Database secrets engine (includes policies): github.com/joatmon08/hashicorp-stack-demoapp/blob/hashiconf-eu/vault/app/database.tf
@subbuthiagarajan5787
@subbuthiagarajan5787 Ай бұрын
@Hashicorp - Can HCP rotate Windows and Linux Secrets password? Can you share some documentation
@HashiCorp
@HashiCorp Ай бұрын
Thanks for reaching out! HVS does not currently support this type of password rotation, but HCP Vault Dedicated and Vault do. Here is a link with video and details of how to do it: www.hashicorp.com/resources/painless-password-rotation-hashicorp-vault
@premierde
@premierde Ай бұрын
Wonderful. Can you also please show for Dynamic secret
@HashiCorp
@HashiCorp Ай бұрын
Here you go!: kzbin.info/www/bejne/e2q7dZmFi7OBaLc
@rajatgupta5897
@rajatgupta5897 Ай бұрын
Hi i have a question regrading vault agent. I’m working on integrating HashiCorp Vault into our application using Vault Agent for authentication. The initial setup works well, where the application reads the Vault token from a file generated by Vault Agent and uses it to authenticate with the Vault server. However, I’m concerned about handling scenarios where the token’s max TTL is reached, and a new token is generated by Vault Agent. Currently, our application reads the token once during initialization and uses it for subsequent operations. If the token expires and a new one is generated, the application wouldn’t automatically know about the new token, which could lead to failed operations. To address this, I am thinking to implement a file watcher that monitors the token file for changes. When a new token is generated, the watcher reloads the token and updates the Vault client. While this seems to work in theory, I want to ensure that we’re following best practices and not missing any important considerations. Here are the specific questions I have: Is monitoring the token file for changes and reloading the token dynamically the recommended approach for handling token renewal with Vault Agent? Are there any potential pitfalls or edge cases I should be aware of when implementing this solution? Are there more efficient or reliable methods to ensure the application always has access to a valid token, especially in high-availability or production environments? I’d appreciate any feedback or suggestions on improving this implementation.
@leetharp1968
@leetharp1968 Ай бұрын
Do you have a video on using boundary client to rds?
@HashiCorp
@HashiCorp Ай бұрын
8:55 in this video covers that to some extent. Is there anything specific you're looking for?
@JeffBeagley
@JeffBeagley Ай бұрын
Great video! however for me.. in order to reference the appropriate git tag, I had to do [email protected]:org/repo.git//<module>?ref=v1.0 instead of doing repo.git?ref=tag//module
@vinothkdarvin
@vinothkdarvin Ай бұрын
When is part 2 coming?
@HashiCorp
@HashiCorp Ай бұрын
Hi there, thanks for reaching out. Our part 2 is a bit delayed. We're working on scheduling it now, and hoping to launch it by the end of August. I'll follow up here once it goes live!
@gialamhuynh5448
@gialamhuynh5448 Ай бұрын
Dear Mr Dadgar, Thank you. This short presentation is enlightening, insightful and inspires some ideas. Among developers, please include machine learning engineers and data engineers who are at least consumers of platforms too.
@mfm35b
@mfm35b Ай бұрын
Does terraform cloud work best with github, or will it work equally well with github and gitlab?
@HashiCorp
@HashiCorp Ай бұрын
HCP Terraform (the new name for Terraform Cloud) supports GitHub, GitLab, Bitbucket, and Azure DevOps. You can check our documentation about VCS connectivity here: developer.hashicorp.com/terraform/cloud-docs/vcs
@MrNonrepetitive
@MrNonrepetitive Ай бұрын
This duo explained things so well that I'm looking for more videos of these two.
@orlandokelly5011
@orlandokelly5011 Ай бұрын
Can you show details of calling terraform no code provisioning using the apis , so we can call from our itsm tool , can you link to your sample code
@HashiCorp
@HashiCorp Ай бұрын
Hi there, thanks for reaching out! If you are using ServiceNow as your ITSM, the official Service Catalog for Terraform integration now natively supports provisioning workspaces from no-code modules, you can learn more in this blog post: www.hashicorp.com/blog/servicenow-catalog-for-terraform-adds-no-code-integration Otherwise, you can find the API documentation for creating a no-code module workspace here: developer.hashicorp.com/terraform/cloud-docs/api-docs/no-code-provisioning#create-a-no-code-module-workspace
@JudgeFredd
@JudgeFredd Ай бұрын
Great to have such information from the source
@zhenqili9732
@zhenqili9732 Ай бұрын
Charming and interesting explanation, thank you
@DevopsCarioca
@DevopsCarioca Ай бұрын
Muito conteúdo de excelência em uma só palestra, parabéns a Hashicorp por montar esse timaço
@antoniothomacelli
@antoniothomacelli Ай бұрын
Thanks for sharing!
@Saman-cq6hg
@Saman-cq6hg Ай бұрын
Can waypoint action be used to run custom scripts or perform toolkit installations on a newly deployed EC2 instance / VM ?
@HashiCorp
@HashiCorp Ай бұрын
You could possibly configure a Waypoint action of “agent” type to run a script or a provisioning tool to install packages on a EC2 instance. This blog post covers the use of “agent” type of Waypoint actions → www.hashicorp.com/blog/hcp-waypoint-actions-is-now-in-public-beta Ideally, Waypoint actions are used for app development related day-2+ operations such as build, deploy, or toggling a feature flag.
@SeeRay
@SeeRay Ай бұрын
Hi! Can we run tests for modules with tags instead of branches? It is not possible to change anything in the configuration.
@HashiCorp
@HashiCorp Ай бұрын
Currently, the integrated testing feature is limited to the branch-based module publishing method. Extending this to tag-based modules is something we plan to address in the future based on customer feedback.
@kapilsharma4722
@kapilsharma4722 Ай бұрын
Is HCP boundary is a identity provider tool like Okta, luminate ??
@HashiCorp
@HashiCorp Ай бұрын
Boundary is not an Identity Provider (IDP) but rather a modern PAM solution that works very well with any identity provider that supports OIDC or LDAP like Okta, Azure Entra ID, Auth0, Active Directory, etc. Boundary helps organizations securely control how end users (like developers) access resources (like Linux hosts via SSH, Windows via RDP, databases, Kubernetes clusters via kubectl, web apps, etc). From an end user point of view, they log onto Boundary (which can be redirected to an Identity provider for SSO+MFA). Once they log on, they can use their normal client tools (rdp, ssh, etc) to connect to their resources. Boundary in the background will securely perform the connection and handle the credentials for the resources (linux/windows hosts, databases, etc) on the users behalf. End result is organization is more secure, and end users has a simpler experience. Here's a link to Boundary doc that includes video on How Boundary works: developer.hashicorp.com/boundary/docs/overview/what-is-boundary Here are some great tutorials on trying out Boundary: developer.hashicorp.com/boundary/tutorials/get-started-hcp
@premierde
@premierde Ай бұрын
Can an external storage be hooked with Vault Cluster. Like the external secret operator does
@rosemarywang5465
@rosemarywang5465 Ай бұрын
A Vault cluster deployed in Kubernetes can have some kind of external storage, check out the list of supported storage backends for more information (developer.hashicorp.com/vault/docs/configuration/storage). I am not sure how external secrets operator does external storage but if it is in reference to other secrets managers outside of Vault, the Vault secrets operator only supports Vault as a secrets store.
@mweingar
@mweingar Ай бұрын
Great session team!
@simonpoon2819
@simonpoon2819 2 ай бұрын
What a excellent and well facilitated session. Way to go Team India!
@d3adstarr
@d3adstarr 2 ай бұрын
great talk thnx
@bschaatsbergen
@bschaatsbergen 2 ай бұрын
🖤
@premierde
@premierde 2 ай бұрын
I watched it for 2nd time for the Vault dynamic secrets. So. $vault lease reovke -force -prefix <>. should not be used ? What is the preferred way here then.
@rosemarywang5465
@rosemarywang5465 Ай бұрын
A common challenge with Vault dynamic secrets is that Vault handles the lease, but it is up to the application (or client like Vault agent or VSO) to track when the lease expires and get a new secret from Vault before it does. `vault lease revoke` works best if you intend on revoking a potentially compromised secret and you will proactively restart the application to get a new one. You will have to restart teh application manually, as agent and VSO will not be aware that the lease no longer exists until the 2/3 the time of expected lease expiration.