Migrated from github.com/shafiqalibhai/terraform-template-user-data-nfs https://cloudposse.com/
  • Shell 38.7%
  • HCL 38.5%
  • Dockerfile 12.9%
  • Makefile 9.9%
Find a file
2026-04-27 23:04:55 +00:00
docs Migrate readme yaml (#6) 2018-07-19 11:59:58 +03:00
examples Fix structure (#3) 2017-10-13 12:10:48 +06:00
templates Fix flavor (#4) 2017-11-27 13:48:02 +06:00
.gitignore Migrate readme yaml (#6) 2018-07-19 11:59:58 +03:00
Dockerfile Add Dockerfile: terraform runner with the user-data NFS template module 2026-04-27 23:04:55 +00:00
LICENSE Initial commit 2017-08-02 18:32:08 +06:00
main.tf Fix flavor (#4) 2017-11-27 13:48:02 +06:00
Makefile Migrate readme yaml (#6) 2018-07-19 11:59:58 +03:00
outputs.tf Fix structure (#3) 2017-10-13 12:10:48 +06:00
README.md Update README with comprehensive project information 2026-04-27 20:39:44 +00:00
README.yaml Migrate readme yaml (#6) 2018-07-19 11:59:58 +03:00
variables.tf Migrate readme yaml (#6) 2018-07-19 11:59:58 +03:00

terraform-template-user-data-nfs

Overview

Terraform module designed to use template file to generate the bootstrap shell script user_data.sh

Detected project types: Terraform, Make-based.

This repository was migrated from upstream source github.com/shafiqalibhai/terraform-template-user-data-nfs and is preserved here for archival, reference, or continued local development.

At a glance

  • Default branch: master
  • Visibility: public
  • Size: 48 KB
  • Created: 2026-04-27
  • Last updated: 2026-04-27
  • Stars / Forks / Open issues: 0 / 0 / 0
  • License: Apache-2.0

Languages

Language Bytes Share
Shell 1,518 bytes 44.5%
HCL 1,507 bytes 44.2%
Makefile 388 bytes 11.4%

Repository structure

  • docs/
  • examples/
  • templates/
  • .gitignore (113 B)
  • LICENSE (11,357 B)
  • main.tf (460 B)
  • Makefile (388 B)
  • outputs.tf (137 B)
  • README.md (7,961 B)
  • README.yaml (1,982 B)
  • variables.tf (910 B)

Getting started

Clone the repository:

git clone https://forgejo.deployview.com/ssa/terraform-template-user-data-nfs.git
cd terraform-template-user-data-nfs

Installation

terraform init
terraform plan
terraform apply
make

Usage

Configure variables in a *.tfvars file or via -var flags, then run terraform plan to preview changes.

Original README

The content below is preserved from the previous README. Headings have been demoted so they don't compete with the new top-level sections.

Cloud Posse

terraform-template-user-data-nfs Build Status Latest Release Slack Community

Terraform module designed to use template file to generate the bootstrap shell script user_data.sh


This project is part of our comprehensive "SweetOps" approach towards DevOps.

It's 100% Open Source and licensed under the APACHE2.

Usage

Include this module in your existing terraform code:

module "user_data_nfs" {
  source = "git::https://github.com/cloudposse/terraform-template-user-data-nfs.git?ref=master"
  namespace                  = "${var.namespace}"
  name                       = "${var.name}"
  stage                      = "${var.stage}"
  dir                        = "${var.dir}"
  host                       = "${var.host}"
}

Makefile Targets

Available targets:

  help                                This help screen
  help/all                            Display help for all targets
  lint                                Lint terraform code

Inputs

Name Description Type Default Required
attributes Additional attributes (e.g. policy or role) list <list> no
delimiter Delimiter to be used between name, namespace, stage, etc. string - no
dir Directory mount to string - yes
flavor Flavor depends of OS and init system string debian-systemd no
host NFS server host string - yes
name The Name of the application or solution (e.g. bastion or portal) string - yes
namespace Namespace (e.g. cp or cloudposse) string - yes
stage Stage (e.g. prod, dev, staging) string - yes
tags Additional tags (e.g. map('BusinessUnit','XYZ')) map <map> no

Outputs

Name Description
user_data A rendered content of the shell script

Check out these related projects.

Help

Got a question?

File a GitHub issue, send us an email or join our Slack Community.

Commercial Support

Work directly with our team of DevOps experts via email, slack, and video conferencing.

We provide commercial support for all of our Open Source projects. As a Dedicated Support customer, you have access to our team of subject matter experts at a fraction of the cost of a full-time engineer.

E-Mail

  • Questions. We'll use a Shared Slack channel between your team and ours.
  • Troubleshooting. We'll help you triage why things aren't working.
  • Code Reviews. We'll review your Pull Requests and provide constructive feedback.
  • Bug Fixes. We'll rapidly work to fix any bugs in our projects.
  • Build New Terraform Modules. We'll develop original modules to provision infrastructure.
  • Cloud Architecture. We'll assist with your cloud strategy and design.
  • Implementation. We'll provide hands-on support to implement our reference architectures.

Community Forum

Get access to our Open Source Community Forum on Slack. It's FREE to join for everyone! Our "SweetOps" community is where you get to talk with others who share a similar vision for how to rollout and manage infrastructure. This is the best place to talk shop, ask questions, solicit feedback, and work together as a community to build sweet infrastructure.

Contributing

Bug Reports & Feature Requests

Please use the issue tracker to report any bugs or file feature requests.

Developing

If you are interested in being a contributor and want to get involved in developing this project or help out with our other projects, we would love to hear from you! Shoot us an email.

In general, PRs are welcome. We follow the typical "fork-and-pull" Git workflow.

  1. Fork the repo on GitHub
  2. Clone the project to your own machine
  3. Commit changes to your own branch
  4. Push your work back up to your fork
  5. Submit a Pull Request so that we can review your changes

NOTE: Be sure to merge the latest changes from "upstream" before making a pull request!

Copyright © 2017-2018 Cloud Posse, LLC

License

License

See LICENSE for full details.

Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements.  See the NOTICE file
distributed with this work for additional information
regarding copyright ownership.  The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License.  You may obtain a copy of the License at

  https://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied.  See the License for the
specific language governing permissions and limitations
under the License.

Trademarks

All other trademarks referenced herein are the property of their respective owners.

About

This project is maintained and funded by Cloud Posse, LLC. Like it? Please let us know at hello@cloudposse.com

Cloud Posse

We're a DevOps Professional Services company based in Los Angeles, CA. We love Open Source Software!

We offer paid support on all of our projects.

Check out our other projects, apply for a job, or hire us to help with your cloud strategy and implementation.

Contributors

Igor Rodionov
Igor Rodionov
Sergey Vasilyev
Sergey Vasilyev

Contributing

Contributions are welcome. The typical workflow is:

  1. Open an issue describing the change you'd like to make.
  2. Fork the repository (or create a feature branch if you have write access).
  3. Commit your changes with clear, descriptive messages.
  4. Open a pull request against the master branch.

Please follow the existing code style and include tests or reproduction steps where relevant.

License

This project is licensed under the Apache-2.0 license. See the LICENSE file for the full text.

Repository


This README was generated automatically based on repository metadata, contents, and any prior README content. Edit any section above to add project-specific detail.