FAQ | This is a LIVE service | Changelog

Skip to content
Snippets Groups Projects
  1. Mar 09, 2021
  2. Jan 27, 2021
  3. Jan 11, 2021
  4. Jan 08, 2021
  5. Dec 10, 2020
    • Dr Abraham Martin's avatar
      Merge branch 'issue-11-stackdriver-workspace' into 'master' · 0f6fdc14
      Dr Abraham Martin authored
      allow stackdriver host project to differ from monitored project
      
      Closes #11
      
      See merge request !12
      0f6fdc14
    • Dr Rich Wareham's avatar
      allow stackdriver host project to differ from monitored project · d677de02
      Dr Rich Wareham authored
      As noted in #11, we do not support the common case where a single
      Stackdriver workspace hosts multiple projects. Do this by requiring a
      Google provider for the Stackdriver workspace be passed to the module is
      alerting is enabled.
      
      We use a separate provider because the provider used must be able to
      create monitoring resources *in the host project*. In the case of our
      standard deployment, this implies it needs *product admin* credentials.
      
      We no longer need to enable the monitoring service since this service a)
      needs to be enabled in the *host* project and b) the service will have
      been enabled as a necessary side-effect of creating the Stackdriver
      workspace.
      
      Closes #11
      d677de02
  6. Dec 09, 2020
  7. Aug 20, 2020
  8. Aug 19, 2020
  9. Aug 06, 2020
  10. Aug 05, 2020
  11. Aug 04, 2020
  12. Jul 30, 2020
  13. Jul 29, 2020
  14. Jun 16, 2020
  15. Jun 11, 2020
    • Dr Rich Wareham's avatar
      Allow sql_instance_connection_name to be empty · 0753dceb
      Dr Rich Wareham authored
      Sometimes we don't need a SQL instance for the webapp. Allow
      sql_instance_connection_name to be empty and, if so, don't add the Cloud
      SQL connection roles to the service account or add the SQL instance
      annotation to the webapp.
      
      Closes #5
      0753dceb
    • Dr Rich Wareham's avatar
      allow webapp service account id to be customised · 27dd7ccd
      Dr Rich Wareham authored
      As noted in #6, we were hard-coding the service account id used for the
      webapp to "webapp-run". This meant it was impossible to deploy more than
      one webapp in a project.
      
      Form a better default from the "name" variable. For existing deployments
      the service account id will be unchanged if the "name" variable is at
      its default value.
      
      Allow the service account id to be specified explicitly via the
      optional "service_account_id" variable.
      
      Closes #6
      27dd7ccd
  16. May 04, 2020
  17. Apr 17, 2020
  18. Mar 27, 2020
    • Dr Abraham Martin's avatar
      Merge branch 'hotfix-cloud-run-name' into 'master' · 2e650de8
      Dr Abraham Martin authored
      main.tf: don't ignore changes in name
      
      See merge request !4
      2e650de8
    • Dr Rich Wareham's avatar
      main.tf: don't ignore changes in name · b9f6ca5e
      Dr Rich Wareham authored
      Ignoring changes in name means that one can never run terraform
      deployments beyond the initial creation of the webapp service. Terraform
      will always modify a service in-place but try to use the same name which
      negates the point of *setting* the name in the
      google_cloud_run_service.webapp resource.
      
      The downside of this is that one can't then deploy changes without
      deleting and re-creating random_id.webapp_revision_name resource but
      that is at least documented in the README.
      b9f6ca5e
  19. Mar 26, 2020
  20. Mar 25, 2020
Loading