Data source juju_application

[shipperizer]

Description

Creation of a juju_application data source

The data source can be used in cases where deployment topology is split between different teams but there is still a lot of inter-operation between services

As any data source this prevents hardcoding of values, in this case application names, without validation

Type of change

• Add new resource

Environment

• Juju controller version: 3.5+

• Terraform version: 1.8.2+

QA steps

Manual QA steps should be done to test this PR.

terraform {
  required_providers {
    juju = {
      source  = "juju/juju"
      version = "> 0.14.0"
    }
  }

  required_version = ">= 1.5.0"
}

variable "revision" {
  type = string
}
########################

resource "juju_application" "hydra" {
  model = "test"
  trust = true

  charm {
    name    = "hydra"
    channel = "latest/edge"
    base    = "ubuntu@22.04"
    revision = var.revision
  }
}


### HYDRA dependent ###
data "juju_application" "hydra" {
  model = juju_application.hydra.model
  name  = juju_application.hydra.name
}

[jujubot]

Thanks for opening a pull request! Please follow the instructions here to ensure your pull request is ready for review. Then, a maintainer will review your patch.

@hpidcock @anvial

[jujubot]

Thanks for opening a pull request! Please follow the instructions here to ensure your pull request is ready for review. Then, a maintainer will review your patch.

@hpidcock @anvial

[pik4ez-canonical]

A couple minor comments/documentation adjustments requested. Otherwise LGTM.

[hmlanigan]

I'm confused about to why this is new data source is useful if it no longer contains the trust and units value?

[kian99]

Can we please update the PR description to explain the use case for this data source and update the documentation to also include the potential use cases.