launchpad-reviewers team mailing list archive

[Guruprasad <mp+461232@xxxxxxxxxxxxxxxxxx>]

Review: Approve



Diff comments:

> diff --git a/lp-fetch-service/README.md b/lp-fetch-service/README.md
> new file mode 100644
> index 0000000..65e09cb
> --- /dev/null
> +++ b/lp-fetch-service/README.md
> @@ -0,0 +1,21 @@
> +# Launchpad fetch service
> +
> +This spec deploys Launchpad's fetch service.
> +
> +You can run it locally using Juju's LXD support and Mojo. First, configure
> +your environment:
> +
> +    export MOJO_ROOT="$HOME/.local/share/mojo"
> +    export MOJO_PROJECT=mojo-lp-fetch-service
> +    export MOJO_WORKSPACE=devel
> +    export MOJO_SERIES=jammy
> +    export MOJO_SPEC=git+https://git.launchpad.net/~launchpad/launchpad-mojo-specs/+git/private

This wouldn't work with a private repository like the target of this MP. A pattern I have seen used in these cases is to specify the local filesystem path to the specs repository. For example, `MOJO_SPEC=/home/stg-vbuilder/spec`.

> +    export MOJO_STAGE=lp-fetch-service/devel
> +
> +Then run the spec using Mojo:
> +
> +    mojo project-new -c containerless
> +    mojo workspace-new
> +    mojo run
> +
> +You must have python3-yaml installed.
> diff --git a/lp-fetch-service/bundle.yaml b/lp-fetch-service/bundle.yaml
> new file mode 100644
> index 0000000..2811116
> --- /dev/null
> +++ b/lp-fetch-service/bundle.yaml
> @@ -0,0 +1,22 @@
> +{%- if stage_name == "production" %}
> +{%-   set devel = False %}
> +{%- elif stage_name == "staging" %}
> +{%-   set devel = False %}
> +{%- else %}
> +{%-   set devel = True %}
> +{%- endif -%}
> +
> +series: jammy
> +applications:
> +{%- if devel or stage_name == "staging" %}

Afaik, qastaging has working builders but staging doesn't. Are we looking to deploy this on staging in spite of that? If yes, let us also include qastaging.

> +  fetch-service:
> +    {#- While the fetch-service charm and snap are not public, we are deploying
> +        a locally built charm. The lines below should be replaced with the path
> +        to charmhub, channel and revision number once the charm and snap are
> +        public. Currently, this expects the charm and snap to be copied to the
> +        path where the bundle.yaml is rendered, in the mojo project folder (eg.
> +        .../mojo/lp-fetch-service/jammy/devel/charms/lp-fetch-service/). #}
> +    charm: "./fetch-service_ubuntu-22.04-amd64.charm"
> +    resources:
> +      snap: "./fetch-service.snap"
> +{%- endif %}
> diff --git a/lp-fetch-service/verify b/lp-fetch-service/verify
> new file mode 100755
> index 0000000..df9e6ef
> --- /dev/null
> +++ b/lp-fetch-service/verify
> @@ -0,0 +1,8 @@
> +#! /bin/sh
> +set -e
> +
> +TOP="${0%/*}"
> +
> +export EXTRA_SKIP_CHECKS="check_swap${EXTRA_SKIP_CHECKS:+|${EXTRA_SKIP_CHECKS}}"

Is there a reason why we want to disable the `check_swap` check?

> +
> +exec "$TOP/utils/verify"


-- 
https://code.launchpad.net/~ines-almeida/launchpad-mojo-specs/+git/private/+merge/461232
Your team Launchpad code reviewers is subscribed to branch ~launchpad/launchpad-mojo-specs/+git/private:master.