Allow charm source to be fetched directly from Git instead of local path

[mateofloreza]

Steps to reproduce

The current module implementation works perfectly — everything deploys as expected.
However, it would be great to have an option to reference the charm source directly from Git instead of using a local relative path.

This would simplify integration with tools like Terragrunt, making it easier to manage module dependencies and versions consistently across environments.

Expected behavior

module "mongodb" {
  source = "git::https://github.com/canonical/mongodb-operator.git//terraform/charm/replica_set?ref=6/edge"

  channel  = var.mongodb.channel
  revision = var.mongodb.revision
  base     = var.mongodb.base

  app_name          = var.mongodb.app_name
  units             = var.mongodb.units
  machines          = var.mongodb.machines
  config            = merge(var.mongodb.config, { "role" : "replication" })
  model             = var.mongodb.model
  constraints       = var.mongodb.constraints
  storage           = var.mongodb.storage
  endpoint_bindings = var.mongodb.endpoint_bindings
  expose            = var.mongodb.expose
}

Actual behavior

module "mongodb" {
  source = "../../charm/replica_set"

  channel  = var.mongodb.channel
  revision = var.mongodb.revision
  base     = var.mongodb.base

  app_name          = var.mongodb.app_name
  units             = var.mongodb.units
  machines          = var.mongodb.machines
  config            = merge(var.mongodb.config, { "role" : "replication" })
  model             = var.mongodb.model
  constraints       = var.mongodb.constraints
  storage           = var.mongodb.storage
  endpoint_bindings = var.mongodb.endpoint_bindings
  expose            = var.mongodb.expose
}

Versions

Operating system: ubuntu 22.04

Juju CLI: 3.6.9

Juju agent: 3.6.9

Charm revision: 229

LXD: 5.21/stable

Log output

Juju debug log:

Additional context

[syncronize-issues-to-jira]

Thank you for reporting your feedback to us!

The internal ticket has been created: https://warthogs.atlassian.net/browse/DPE-8539.

This message was autogenerated

[Gu1nness]

Hello @mateofloreza !
While this would simplify overall usage in production, it would make dev harder if not done properly.

Do you think it would be a good idea to have a variable for that, and a default value to local path ?
That way you could refer the git repo when you want, but for development, it stays usable.

[mateofloreza]

Hello @Gu1nness, I think that approach will work.