Glenn Chia
Solutions Architect, HashiCorp
Singapore
Actions
Glenn is a Solutions Architect Specialist at HashiCorp where he focuses on infrastructure lifecycle management. He works closely with enterprise customers to define strategies for operating infrastructure as code at scale and innovates on product integrations across networking, security, Kubernetes, and artificial intelligence domains. Prior to HashiCorp, Glenn worked at AWS in Professional Services, where he helped customers implement generative AI applications, enterprise backup architectures, data lakes, and cloud landing zones. Glenn is passionate about helping organizations optimize their cloud infrastructure and deployment workflows through automation and modern DevOps practices.
Badges
Area of Expertise
Topics
Managing Terraform Module Lifecycle with Deprecation, Explorer, Change Requests, and Notifications
Modern infrastructure demands regular updates to maintain security, efficiency, and compliance. However, managing the lifecycle of Terraform modules presents unique challenges for platform teams: How do you signal to consumers that a module version should no longer be used? How can you identify workspaces that need updates? How do you effectively communicate these needs across your organization?
In this session, we'll explore comprehensive module lifecycle management strategies within HCP Terraform's private registry. You'll learn practical approaches to:
- Implement effective module versioning strategies that enable seamless updates
- Leverage module deprecation to signal that versions are maintained but not recommended
- Use module revocation to block new usage of problematic versions while maintaining existing workloads
- Utilize the Explorer to identify workspaces using outdated module versions
- Create and manage change requests to track necessary updates
- Configure team notifications to ensure timely communication about required changes
Through practical demonstrations, you'll see how these tools create a complete feedback loop between module publishers and consumers, enabling effective governance without disrupting developer workflows. Whether you're managing a small team or a large enterprise, these practices will help you maintain module health while strengthening communication between platform teams and module consumers.
Migrate Terraform state between providers
Terraform has many providers which support deploying resources into AWS. 2 of such providers are the Terraform AWS Provider and Terraform AWSCC Provider. Practitioners may find updating and keeping up with 2 providers challenging and may want to migrate their state to use only a single provider. This session guides practitioners on how they can migrate state between providers without destroying the resources managed by the state. This gives practitioners the flexibility to also build resource supported in one provider and eventually move those resources to the other provider.
Testing for backward compatibility when developing Terraform AWS Provider resources
When working on building support for new resource arguments in the Terraform AWS Provider, there are situations when we need to deprecate certain arguments while ensuring backward compatibility. This lightning talk goes through a live case study illustrating this scenario in the following pull request: https://github.com/hashicorp/terraform-provider-aws/pull/31035. This gives practitioners confidence that their existing code remains functional while giving them a path to migrate to the latest arguments.
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top