Skip Navigation
terraform

Terraform

  • Oracle goes vegan: Dumps Terraform for OpenTofu
    www.thestack.technology Oracle goes vegan: Dumps Terraform for OpenTofu

    OCI tells customers to shift to latest update built on open source. We guess OpenTofu is enterprise-ready!

    Oracle goes vegan: Dumps Terraform for OpenTofu
    2
  • Terraform Enterprise adds Podman support and workflow enhancements
    www.hashicorp.com Terraform Enterprise adds Podman support and workflow enhancements

    Customers can now deploy Terraform Enterprise using Podman on Red Hat Enterprise Linux. Recent releases also improve VCS, policy, and run task workflows at scale.

    Terraform Enterprise adds Podman support and workflow enhancements
    0
  • OpenTofu 1.7.0 is out with State Encryption, Dynamic Provider-Defined Functions, and more
    opentofu.org OpenTofu 1.7.0 is out with State Encryption, Dynamic Provider-Defined Functions, and more | OpenTofu

    OpenTofu 1.7.0 is now available with full state encryption, dynamic provider-defined functions, the removed and loopable import blocks, new migration guides, and much more.

    OpenTofu 1.7.0 is out with State Encryption, Dynamic Provider-Defined Functions, and more | OpenTofu
    0
  • HashiCorp joins IBM to accelerate multi-cloud automation
    www.hashicorp.com HashiCorp joins IBM to accelerate multi-cloud automation

    HashiCorp joins IBM to accelerate the mission of multi-cloud automation and bring the products to a broader audience of users and customers.

    HashiCorp joins IBM to accelerate multi-cloud automation
    0
  • Our Response to Hashicorp's Cease and Desist Letter | OpenTofu
    opentofu.org Our Response to Hashicorp's Cease and Desist Letter | OpenTofu

    On April 3rd, we received a Cease and Desist letter from HashiCorp regarding our implementation of the "removed" block in OpenTofu, claiming copyright infringement on the part of one of our core developers. We were also made aware of an article posted that same day with the same accusations. We have...

    Our Response to Hashicorp's Cease and Desist Letter | OpenTofu

    cross-posted from: https://feddit.nu/post/4403233

    > ! > > On April 3rd, we received a Cease and Desist letter from HashiCorp regarding our implementation of the "removed" block in OpenTofu, claiming copyright infringement on the part of one of our core developers. We were also made aware of an article posted that same day with the same accusations. We have investigated these claims and are publishing the C&D letter, our response and the source code origin document resulting from our investigation. > > The OpenTofu team vehemently disagrees with any suggestion that it misappropriated, mis-sourced, or otherwise misused HashiCorp’s BSL code. All such statements have zero basis in facts. > > HashiCorp has made claims of copyright infringement in a cease & desist letter. These claims are completely unsubstantiated. > > The code in question can be clearly shown to have been copied from older code under the MPL-2.0 license. HashiCorp seems to have copied the same code itself when they implemented their version of this feature. All of this is easily visible in our detailed SCO analysis, as well as their own comments which indicate this. > ### Documents > * HashiCorp's C&D Letter > * Our Response > * Source Code Origin Document: [HTML, PDF] ⇐ For the detailed code analysis, see here. > > To prevent further harassment of individual people, we have redacted any personal information from these documents. > ### Conclusion > > Despite these events, we have managed to carry out significant development on OpenTofu 1.7, including state encryption, “for_each” implementation for “import” blocks, as well as the all-new provider-defined functions supported by the recently released provider plugin protocol. > > On that note, we will be releasing a new pre-release version next week, and we are eager to gather feedback from the community. > > — The OpenTofu Team > > --- > > The image in this blog post contains code licensed under the BUSL-1.1 by HashiCorp. However, for the purposes of this post we are making non-commercial, transformative fair use under 17 U.S. Code § 107. > You can read more about fair use on the website of the US Copyright Office.

    0
  • Help us test OpenTofu 1.7.0-alpha1
    opentofu.org Help us test OpenTofu 1.7.0-alpha1 | OpenTofu

    Hey there, OpenTofu community! Over the last few months we've been hard at work to bring new features, such as the state encryption and the removed block, as well as compatibility improvements to you. A few days ago we released the first preview version of these improvements as OpenTofu 1.7.0-alpha1...

    Help us test OpenTofu 1.7.0-alpha1 | OpenTofu
    0
  • Terraform gains upgrades for module tests, explorer, and more
    www.hashicorp.com Terraform gains upgrades for module tests, explorer, and more

    The latest Terraform Cloud and Enterprise enhancements help users leverage high-quality modules, monitor their workspace health, minimize management overhead, and more.

    Terraform gains upgrades for module tests, explorer, and more
    0
  • Terraform without "prop drilling"

    I have a massive terraform state I maintain for work. After learning about reusing resources using modules I adopted the same rule for terraform I have for other PLs "only call functions in the main func". Meaning I'm only allowed to declare modules that reference resources at the top level.

    My problem is that I have modules calling modules all over the place, the average length of any of my resources is 8 names. I have values I want to share across multiple different kinds of modules that do different things. Currently I have a top level module called "constants" with output blocks to store every constant I need. It works to an extent.

    The thing is that I had a similar problem when web developing in React. Prop drilling is a coding style in React where a component receives a prop just for the purpose of passing the prop to a child component, the receiving component doesn't actually need that prop for itself. React solves this by the context api which lets one component pass a value to any child component of any depth. How can we have something similar in Terraform? Even though every resource I have is defined once in code, it declares the same resources hundreds of times with different appropriate values.

    I wish I could pass things like the dockerSecret to a kubernetes deployment 6 modules deep in such a way that that dependant component of a module waits for the docker secret to be created while other resources that don't depend on it can be scheduled to be created later. Prop drilling doesn't work all that well and it forces you to copy alot of code. Maybe modules aren't the best way to reuse resources.

    I feel like HCL doesn't have syntax that would support such a thing idomatically. Maybe something like decorator syntax or a special type of block where you write a proper data, resource, or module block?

    What do you guys think?

    3
  • Terraform 1.7 adds test mocking and config-driven remove
    www.hashicorp.com Terraform 1.7 adds test mocking and config-driven remove

    Now generally available, HashiCorp Terraform 1.7 adds mocking capabilities to the Terraform test framework and a config-driven state removal workflow.

    Terraform 1.7 adds test mocking and config-driven remove
    1
  • OpenTofu is going GA
    opentofu.org OpenTofu is going GA | OpenTofu

    Today is a big day for OpenTofu! After four months of work, we're releasing the first stable release of OpenTofu, a community-driven open source fork of Terraform. OpenTofu, a Linux Foundation project, is now production-ready. It’s a drop-in replacement for Terraform, and you can easily migrate to i...

    OpenTofu is going GA | OpenTofu
    0
  • OpenTofu Release Candidate Is Out, GA Set for Jan 10th | OpenTofu
    opentofu.org OpenTofu Release Candidate Is Out, GA Set for Jan 10th | OpenTofu

    OpenTofu v1.6.0-rc1, the final stage before the first stable release, is out today. It follows the quick succession of its alpha and beta versions, on the road to an expected General Availability release on January 10, 2024, right after the holidays.

    OpenTofu Release Candidate Is Out, GA Set for Jan 10th | OpenTofu
    0
  • Terraform stacks, explained
    www.hashicorp.com Terraform stacks, explained

    Terraform stacks simplify provisioning and managing resources at scale, reducing the time and overhead of managing infrastructure.

    Terraform stacks, explained
    1
  • OpenTF is now OpenTofu
    opentofu.org OpenTofu

    The open source infrastructure as code tool.

    OpenTofu

    OpenTofu is also officially under the Linux Foundation.

    You will invoke tofu instead of terraform.

    0
  • OpenTF repository is now public
    github.com GitHub - opentofu/opentofu: OpenTofu lets you declaratively manage your cloud infrastructure.

    OpenTofu lets you declaratively manage your cloud infrastructure. - GitHub - opentofu/opentofu: OpenTofu lets you declaratively manage your cloud infrastructure.

    GitHub - opentofu/opentofu: OpenTofu lets you declaratively manage your cloud infrastructure.

    For context: https://opentf.org/

    0
  • Create a general Hashicorp community?

    As Lemmy isn't quite so large yet, wouldn't it be better to have a community to discuss all of the Hashicorp suite, amongst them terraform? I think it would allow for more activity, and better crossfeed of information.

    0
  • Release v3.66.0 · hashicorp/terraform-provider-azurerm
    github.com Release v3.66.0 · hashicorp/terraform-provider-azurerm

    FEATURES: New Data Source: azurerm_mobile_network_attached_data_network (#22168) New Resource: azurerm_graph_account (#22334) New Resource: azurerm_mobile_network_attached_data_network (#22168) E...

    Release v3.66.0 · hashicorp/terraform-provider-azurerm

    FEATURES:

    New Data Source: azurerm_mobile_network_attached_data_network (#22168) New Resource: azurerm_graph_account (#22334) New Resource: azurerm_mobile_network_attached_data_network (#22168)

    ENHANCEMENTS:

    dependencies: bump go-azure-sdk to v0.20230720.1190320 and switch machinelearning, mixedreality, mariadb, storagecache, storagepool, vmware, videoanalyzer, voiceServices and mobilenetwork to new base layer (#22538) dependencies: move azurerm_bastion_host and azurerm_network_connection_monitor over to hashicorp/go-azure-sdk (#22425) dependencies: move azurerm_network_watcher_flow_log to hashicorp/go-azure-sdk (#22575) dependencies: move mysql resources over to hashicorp/go-azure-sdk (#22528) dependencies: move storage_sync resources over to hashicorp/go-azure-sdk (#21928) dependencies: updating to API Version 2022-08-08 (#22440) postgres - updating to API Version 2023-03-01-preview (#22577) data.azurerm_route_table - support for the bgp_route_propagation_enabled property (#21940) data.azurerm_servicebus_* - add deprecation messages for the resource_group_name and namespace_name properties (#22521) azurerm_cdn_frontdoor_rule - allow the conditions.x.url_path_condition.x.match_values property to be set to / (#22610) azurerm_eventhub_namespace - updates properly when encryption is enabled (#22625) azurerm_logic_app_standard - now exports the auto_swap_slot_name attribute (#22525) azurerm_mysql_flexible_server_configuration - the value property can now be changed without creating a new resource (#22557) azurerm_postgresql_flexible_server - support for 33554432 storage (#22574) azurerm_postgresql_flexible_server - support for the geo_backup_key_vault_key_id and geo_backup_user_assigned_identity_id properties (#22612) azurerm_spring_cloud_service - support for the marketplace block (#22553) azurerm_spring_cloud_service - support for the outbound_type property (#22596)

    BUG FIXES:

    provider: the Resource Providers Microsoft.Kubernetes and Microsoft.KubernetesConfiguration are no longer automatically registered (#22580) data.automation_account_variables - correctly populate missing variable attributes (#22611) data.azurerm_virtual_machine_scale_set - fix an issue where computer_name, latest_model_applied, power_state and virtual_machine_id attributes were not correctly set (#22566) azurerm_app_service_public_certificate - poll for certificate during read to get around an eventual consistency bug (#22587) azurerm_application_gateway - send min_protocol_version and correct policy_type when using CustomV2 (#22535) azurerm_cognitive_deployment - remove upper limit on validation for the capacity property in the scale block (#22502) azurerm_cosmosdb_account - fixed regression to default_identity_type being switched to FirstPartyIdentity on update (#22609) azurerm_kubernetes_cluster - the windows_profile.admin_password property will become Required in v4.0 (#22554) azurerm_kusto_cluster - the engine property has been deprecataed and is now non functional as the service team intends to remove it from the API (#22497) azurerm_maintenance_configuration - tge package_names_mask_to_exclude and package_names_mask_to_exclude properties are not set properly (#22555) azurerm_redis_cache - only set the rdb_backup_enabled property when using a premium SKU (#22309) azurerm_site_recovery_replication_recovery_plan - fix an issue where the order of boot recovery groups was not correctly maintained (#22348) azurerm_synapse_firewall_rule - correct an overly strict validation for the name property (#22571)

    0
  • Release v3.65.0 · hashicorp/terraform-provider-azurerm
    github.com Release v3.65.0 · hashicorp/terraform-provider-azurerm

    FEATURES: New Data Source: azurerm_communication_service (#22426) ENHANCEMENTS: dependencies: updating to v0.20230712.1084117 of github.com/hashicorp/go-azure-sdk (#22491) dependencies: updating...

    Release v3.65.0 · hashicorp/terraform-provider-azurerm

    FEATURES:

    New Data Source: azurerm_communication_service (#22426)

    ENHANCEMENTS:

    dependencies: updating to v0.20230712.1084117 of github.com/hashicorp/go-azure-sdk (#22491) dependencies: updating to v0.20230703.1101016 of github.com/tombuildsstuff/kermit (#22390) provider: the Resource Providers Microsoft.Kubernetes and Microsoft.KubernetesConfiguration are now automatically registered (#22463) automation/dscconfiguration - updating to API Version 2022-08-08 (#22403) azurestackhcl - updating to API Version 2023-03-01 (#22411) batch - updating to use API Version 2023-05-01 (#22412) datafactory - moving azurerm_data_factory and azurerm_data_factory_managed_private_endpoint over to hashicorp/go-azure-sdk (#22409) elastic - updating to API Version 2023-06-01 (#22451) kusto - updating to API Version 2023-05-02 [GH-22410 managedapplications - migrate to hashicorp/go-azure-sdk (#21571) privatedns: updating to API Version 2020-06-01 (#22470) storage - updating to Data Plane API Version 2020-08-04 (#22405) network - application_security_group and private_endpoint now use hashicorp/go-azure-sdk (#22396) voiceservices: updating to use API Version 2023-04-03 (#22469) Data Source: azurerm_kubernetes_cluster - add support for the internal_ingress_gateway_enabled and external_ingress_gateway_enabled properties (#22393) azurerm_batch_account - support for the network_profile block (#22356) azurerm_container_app - the min_replicas and max_replicas propertiesnow support a maximum value of 300 (#22511) azurerm_dns_zone - can now use the host_name property with dns_zone for soa_record creation (#22312) azurerm_kubernetes_cluster - add support for the internal_ingress_gateway_enabled and external_ingress_gateway_enabled properties (#22393) azurerm_site_recovery_vmware_replication_policy_association - update validation to correctly handle case (#22443)

    BUG FIXES:

    azurerm_automation_dsc_configuration - fixing an issue where content_embedded couldn't be deserialized (#22403) azurerm_data_factory_dataset_cosmosdb_sqlapi - fix incorrect type/error message during read (#22438) azurerm_data_factory_dataset_mysql - fix incorrect type/error message during read (#22438) azurerm_data_factory_dataset_postgresql - fix incorrect type/error message during read (#22438) azurerm_logic_app_workflow - prevent crash when access_control is empty block (#22486) azurerm_vpn_server_configuration - prevent a potential panic when setting deprecated variables (#22437)

    0
  • Terraform 1.5.3
    github.com Release v1.5.3 · hashicorp/terraform

    1.5.3 (July 12, 2023) BUG FIXES: core: Terraform could fail to evaluate module outputs when they are used in a provider configuration during a destroy operation (#33462) backend/consul: When faili...

    Release v1.5.3 · hashicorp/terraform

    1.5.3 (July 12, 2023) BUG FIXES:

    core: Terraform could fail to evaluate module outputs when they are used in a provider configuration during a destroy operation (#33462)

    backend/consul: When failing to save state, consul CAS failed with transaction errors no longer shows an error instance memory address, but an actual error message. (#33108)

    plan renderer: Fixes crash when rendering the plan if a relevant attribute contains an integer index specified as a string. (#33475)

    0
  • Release v3.64.0 · hashicorp/terraform-provider-azurerm
    github.com Release v3.64.0 · hashicorp/terraform-provider-azurerm

    FEATURES: New Data Source: azurerm_automation_variables (#22216) New Resource: azurerm_arc_private_link_scope (#22314) New Resource: azurerm_kusto_cosmosdb_data_connection (#22295) New Resource: a...

    Release v3.64.0 · hashicorp/terraform-provider-azurerm

    FEATURES:

    New Data Source: azurerm_automation_variables (#22216) New Resource: azurerm_arc_private_link_scope (#22314) New Resource: azurerm_kusto_cosmosdb_data_connection (#22295) New Resource: azurerm_pim_active_role_assignment (#20731) New Resource: azurerm_pim_eligible_role_assignment (#20731) ENHANCEMENTS:

    dependencies: web: updating to API Version 2022-09-01 (#22352) dependencies: cognitive: updating to API Version 2023-05-01 (#22223) dependencies: updating to v1.53.0 of google.golang.org/grpc (#22383) azurerm_cognitive_deployment - suppot for the scale block propeties tier, size, family, and capacity (#22223) azurerm_linux_function_app - added support for the public_network_access_enabled property (#22352) azurerm_linux_function_app_slot - added support for the public_network_access_enabled property (#22352) azurerm_linux_web_app - added support for the public_network_access_enabled property (#22352) azurerm_linux_web_app_slot - added support for the public_network_access_enabled property (#22352) azurerm_windows_function_app - added support for the public_network_access_enabled property (#22352) azurerm_windows_function_app_slot - added support for the public_network_access_enabled property azurerm_windows_web_app - added support for the public_network_access_enabled property (#22352) azurerm_windows_web_app_slot - added support for the public_network_access_enabled property (#22352) azurerm_stream_analytics_output_blob - increase the batch_min_rows property allowed values to 1000000 (#22331) azurerm_spring_cloud_gateway - support for the the allowed_origin_patterns property (#22317) BUG FIXES:

    Data Source azurerm_virtual_machine_scale_set - prevent a nil pointer panic during reads (#22335) azurerm_application_insights_api_key - prevent a nil pointer panic (#22388) azurerm_linux_function_app - the allowed_origins property in the cors block now has a minimum entry count of 1 (#22352) azurerm_linux_function_app_slot - the allowed_origins property in the cors block now has a minimum entry count of 1 (#22352) azurerm_linux_web_app - the allowed_origins property in the cors block now has a minimum entry count of 1 (#22352) azurerm_linux_web_app - prevent a nil pointer panic in docker settings processing (#22347) azurerm_linux_web_app_slot - the allowed_origins property in the cors block now has a minimum entry count of 1 (#22352) azurerm_private_dns_resolver_forwarding_rule_resource - changing the domain_name property now creates a new resource (#22375) azurerm_windows_function_app - the allowed_origins property in the cors block now has a minimum entry count of 1 (#22352) azurerm_windows_function_app_slot - the allowed_origins property in the cors block now has a minimum entry count of 1 (#22352) azurerm_windows_web_app - the allowed_origins property in the cors block now has a minimum entry count of 1 (#22352) azurerm_windows_web_app_slot - the allowed_origins property in the cors block now has a minimum entry count of 1 (#22352) azurerm_network_security_rule - improve validation of the name property and prevent creation of resources that are broken (#22336) DEPRECATION:

    media - all resources and data sources are deprecated ahead of service being retired (#22350)

    0
  • Managing Terraform states with Gitlab

    Check this out if you're hosting your code on Gitlab and don't want to hustle with AWS services or pay for Terraform cloud.

    0
2 Active users