Add Application Module

[asteel-gsa]

I set up everything for the module in this branch, however, the main way for me to validate it is to actually deploy the FAC application. Since this is a Django app, it does require an s3 service binding for the staticfiles to go to during bootup. Because of this, I do not want to hardcode in anything as a requirement, as that could vary from project to project.

Without the ability to perform a service binding after the fact, I am not exactly sure we can take this module in just yet. With that being said, so long as the app doesnt require service bindings to start up, or any service bindings for that matter, this should deploy no issue. In that event then the module can be used.

However, at minimum, based on what we do at the FAC, we are looking, minimum, for most running apps:

  service_binding {
    service_instance = cloudfoundry_user_provided_service.clam.id
  }

  service_binding {
    service_instance = var.s3_id
  }

  service_binding {
    service_instance = var.db_id
  }

  service_binding {
    service_instance = var.https_proxy_creds_id
  }

  service_binding {
    service_instance = var.logshipper_id
  }