mtncloud-cli 1.0.0 → 1.0.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 639203a2d4abce5fa9f74f710a71dd159f38c775dcd009549aba64fe5de773c9
-  data.tar.gz: d598611f41e31e3546003dd12db8e84be2c4cc5e1a440bb8fb51b78d5f21dc23
+  metadata.gz: b3a5dc76695dc9b45484493d57dc18f76a6421b860734528495d877ac6d19d4a
+  data.tar.gz: e8c2396dc112b8cd25ba5887caf3bbc259a9ab77b04f3f828d546918dbaf111c
 SHA512:
-  metadata.gz: e2b6e6aea6578305035081434b24ce671a43df0ccd0760bf2813a7dbea54c932382d37f002f1ad32ede689bd9f34c956f04d6126b9cb78625b48cfca468a2971
-  data.tar.gz: 0aec3580475e9814d229695f76d89f3f254a7111831367b4f26fb049c695b441e708049a951da5d2938e193359ba30912c9cf9c208e5cd84a6e09fe3a280f9f0
+  metadata.gz: 322918f434dfde44a63ce4e5dbfc430cb0d8a1a78fe41ecaafc67c2c44269012f39f43edbcec799b26e9b5b1236b545eeb5a70602236ce3e0bd61ffe0e723f9e
+  data.tar.gz: bf2e4aaa891fa291376f7c0bd03106ab12fa5ec90b6bf773b9a8a957043a5de02b6f29716b5b008e6c5a8363f65d2a0d8f62499dbac976b5e0ad5c9b21a84983

data/.dockerignore

@@ -1,20 +1,20 @@
-# Keep local and generated files out of the Docker build context.
-# Do NOT add .git here: the gem build uses `git ls-files` to list its files.
-# Only exclude files that are not tracked by git, or the gem build will fail.
-
-# test credentials for the live appliance tests
-test_config.yaml
-
-# built gems and bundler state
-*.gem
-pkg
-.bundle
-Gemfile.lock
-
-# temporary and editor files
-tmp
-coverage
-*.log
-.idea
-.vscode
-.DS_Store
+# Keep local and generated files out of the Docker build context.
+# Do NOT add .git here: the gem build uses `git ls-files` to list its files.
+# Only exclude files that are not tracked by git, or the gem build will fail.
+
+# test credentials for the live appliance tests
+test_config.yaml
+
+# built gems and bundler state
+*.gem
+pkg
+.bundle
+Gemfile.lock
+
+# temporary and editor files
+tmp
+coverage
+*.log
+.idea
+.vscode
+.DS_Store

data/.github/pull_request_template.md

@@ -1,14 +1,14 @@
-## What this changes
-
-<!-- What does this pull request change, and why? -->
-
-## How it was tested
-
-<!-- For example: bundle exec rake test:offline, or commands you ran against an appliance -->
-
-## Checklist
-
-- [ ] `bundle exec rake test:offline` passes
-- [ ] Tests added or updated for the changed behaviour
-- [ ] README updated if installation, configuration or usage changed
-- [ ] Customer-facing text says MTN Cloud, not Morpheus
+## What this changes
+
+<!-- What does this pull request change, and why? -->
+
+## How it was tested
+
+<!-- For example: bundle exec rake test:offline, or commands you ran against an appliance -->
+
+## Checklist
+
+- [ ] `bundle exec rake test:offline` passes
+- [ ] Tests added or updated for the changed behaviour
+- [ ] README updated if installation, configuration or usage changed
+- [ ] Customer-facing text says MTN Cloud, not Morpheus

data/.github/workflows/ci.yml

@@ -1,56 +1,56 @@
-# Runs on every pull request and every push to main.
-# main is protected: a pull request can only be merged when every job here passes.
-name: CI
-
-on:
-  pull_request:
-  push:
-    branches: [main]
-
-permissions:
-  contents: read
-
-jobs:
-  test:
-    name: Offline tests (Ruby ${{ matrix.ruby }})
-    runs-on: ubuntu-latest
-    strategy:
-      fail-fast: false
-      matrix:
-        ruby: ["3.3", "3.4", "4.0"]
-    steps:
-      - uses: actions/checkout@v5
-
-      - uses: ruby/setup-ruby@v1
-        with:
-          ruby-version: ${{ matrix.ruby }}
-          bundler-cache: true
-
-      - name: Run offline tests
-        run: bundle exec rake test:offline
-
-  build:
-    name: Build gem
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v5
-
-      - uses: ruby/setup-ruby@v1
-        with:
-          ruby-version: "3.3"
-
-      - name: Build the gem
-        run: gem build mtncloud-cli.gemspec
-
-  # One check for branch protection to require, so the protection rule does not
-  # need to change when the Ruby versions above change.
-  ci-passed:
-    name: CI passed
-    if: always()
-    needs: [test, build]
-    runs-on: ubuntu-latest
-    steps:
-      - name: Fail unless every job passed
-        run: |
-          echo "test: ${{ needs.test.result }}, build: ${{ needs.build.result }}"
-          [ "${{ needs.test.result }}" = "success" ] && [ "${{ needs.build.result }}" = "success" ]
+# Runs on every pull request and every push to main.
+# main is protected: a pull request can only be merged when every job here passes.
+name: CI
+
+on:
+  pull_request:
+  push:
+    branches: [main]
+
+permissions:
+  contents: read
+
+jobs:
+  test:
+    name: Offline tests (Ruby ${{ matrix.ruby }})
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        ruby: ["3.3", "3.4", "4.0"]
+    steps:
+      - uses: actions/checkout@v5
+
+      - uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: ${{ matrix.ruby }}
+          bundler-cache: true
+
+      - name: Run offline tests
+        run: bundle exec rake test:offline
+
+  build:
+    name: Build gem
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v5
+
+      - uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: "3.3"
+
+      - name: Build the gem
+        run: gem build mtncloud-cli.gemspec
+
+  # One check for branch protection to require, so the protection rule does not
+  # need to change when the Ruby versions above change.
+  ci-passed:
+    name: CI passed
+    if: always()
+    needs: [test, build]
+    runs-on: ubuntu-latest
+    steps:
+      - name: Fail unless every job passed
+        run: |
+          echo "test: ${{ needs.test.result }}, build: ${{ needs.build.result }}"
+          [ "${{ needs.test.result }}" = "success" ] && [ "${{ needs.build.result }}" = "success" ]

data/.gitignore

@@ -1,25 +1,25 @@
-*.gem
-*.rbc
-.bundle
-.config
-.yardoc
-Gemfile.lock
-InstalledFiles
-_yardoc
-coverage
-doc/
-lib/bundler/man
-pkg
-rdoc
-spec/reports
-test/tmp
-test/version_tmp
-tmp
-*.bundle
-*.so
-*.o
-*.a
-mkmf.log
-.DS_Store
-.idea
+*.gem
+*.rbc
+.bundle
+.config
+.yardoc
+Gemfile.lock
+InstalledFiles
+_yardoc
+coverage
+doc/
+lib/bundler/man
+pkg
+rdoc
+spec/reports
+test/tmp
+test/version_tmp
+tmp
+*.bundle
+*.so
+*.o
+*.a
+mkmf.log
+.DS_Store
+.idea
 test_config.yaml

data/CLAUDE.md

@@ -1,24 +1,24 @@
-# MTN Cloud CLI
-
-Ruby gem `mtncloud-cli`. It installs the `mtncloud` command and its alias `mcs`. Code is under `lib/mtncloud/` in the `MtnCloud::` namespace. See CONTRIBUTING.md and the README.
-
-## Git workflow (required)
-
-- Never commit or push to `main`. It is protected, and direct pushes are rejected.
-- For every code or docs change: create a branch from an up-to-date `main` (`feature/`, `fix/`, `docs/` or `chore/` prefix), commit there, push the branch, and open a pull request against `main` with `gh pr create --base main`.
-- Merge only after the **CI passed** check succeeds (`gh pr checks <number> --watch`). Never bypass a failing or pending check.
-- Never force-push to `main` and never delete it.
-
-## Testing
-
-- Run `bundle exec rake test:offline` before opening a pull request. CI runs the same task on Ruby 3.3, 3.4 and 4.0.
-- Tests that `require 'mtncloud_test'` need a live appliance and are not run by CI.
-
-## Naming
-
-- Customer-facing text says MTN Cloud, and commands are shown as `mtncloud`.
-- Keep values the appliance or its API defines unchanged, even though they contain "Morpheus": the `X-Morpheus-Lease` and `X-Morpheus-Token` headers, `MORPHEUS_LEASE_TOKEN`, the `morpheus.yml` fallback, job type codes such as `morpheus.task`, the `morpheus` blueprint and backup provider codes, and Morpheus Hub. `test/branding_test.rb` lists the approved ones.
-
-## Releases
-
-Pushing a `v<version>` tag runs `.github/workflows/release.yml`, which publishes to RubyGems. The tag must match `VERSION` in `lib/mtncloud/cli/version.rb`. Push a release tag only when the user asks for one.
+# MTN Cloud CLI
+
+Ruby gem `mtncloud-cli`. It installs the `mtncloud` command and its alias `mcs`. Code is under `lib/mtncloud/` in the `MtnCloud::` namespace. See CONTRIBUTING.md and the README.
+
+## Git workflow (required)
+
+- Never commit or push to `main`. It is protected, and direct pushes are rejected.
+- For every code or docs change: create a branch from an up-to-date `main` (`feature/`, `fix/`, `docs/` or `chore/` prefix), commit there, push the branch, and open a pull request against `main` with `gh pr create --base main`.
+- Merge only after the **CI passed** check succeeds (`gh pr checks <number> --watch`). Never bypass a failing or pending check.
+- Never force-push to `main` and never delete it.
+
+## Testing
+
+- Run `bundle exec rake test:offline` before opening a pull request. CI runs the same task on Ruby 3.3, 3.4 and 4.0.
+- Tests that `require 'mtncloud_test'` need a live appliance and are not run by CI.
+
+## Naming
+
+- Customer-facing text says MTN Cloud, and commands are shown as `mtncloud`.
+- Keep values the appliance or its API defines unchanged, even though they contain "Morpheus": the `X-Morpheus-Lease` and `X-Morpheus-Token` headers, `MORPHEUS_LEASE_TOKEN`, the `morpheus.yml` fallback, job type codes such as `morpheus.task`, the `morpheus` blueprint and backup provider codes, and Morpheus Hub. `test/branding_test.rb` lists the approved ones.
+
+## Releases
+
+Pushing a `v<version>` tag runs `.github/workflows/release.yml`, which publishes to RubyGems. The tag must match `VERSION` in `lib/mtncloud/cli/version.rb`. Push a release tag only when the user asks for one.

data/CONTRIBUTING.md

@@ -1,91 +1,91 @@
-# Contributing to the MTN Cloud CLI
-
-Thank you for helping improve the MTN Cloud CLI. This guide explains how changes get into the project.
-
-## How changes reach main
-
-`main` is protected. Nobody pushes to it directly, including maintainers. Every change goes through a pull request:
-
-1. Update your local `main`:
-
-   ```shell
-   git checkout main
-   git pull
-   ```
-
-2. Create a branch for your change:
-
-   ```shell
-   git checkout -b fix/clusters-get-help
-   ```
-
-   Name the branch after the change, with a prefix: `feature/`, `fix/`, `docs/` or `chore/`.
-
-3. Make your change, run the offline tests (see [Testing](#testing)), and commit.
-4. Push the branch and open a pull request against `main`:
-
-   ```shell
-   git push -u origin fix/clusters-get-help
-   gh pr create --base main
-   ```
-
-5. Wait for the **CI passed** check. It runs the offline tests on Ruby 3.3, 3.4 and 4.0 and builds the gem.
-6. When CI passes, merge the pull request. A pull request cannot be merged while CI is failing or still running.
-
-If CI fails, push more commits to the same branch. CI runs again on every push.
-
-## Setting up
-
-Requirements:
-
-- Ruby 3.3 or newer
-- Bundler 2
-- Git
-
-```shell
-git clone https://github.com/Jose-henry/mtncloud-cli
-cd mtncloud-cli
-bundle install
-```
-
-Run the CLI from your working copy:
-
-```shell
-bundle exec ruby bin/mtncloud --help
-```
-
-See [Development](README.md#development) in the README for the code layout.
-
-## Testing
-
-Run the offline tests before you open a pull request. They don't need an MTN Cloud appliance, and they are the same tests CI runs:
-
-```shell
-bundle exec rake test:offline
-```
-
-Add or update tests for the behaviour you change. A test that doesn't need an appliance must not `require 'mtncloud_test'`, so that `test:offline` and CI run it.
-
-`test/branding_test.rb` fails if any command's help mentions Morpheus, except for values that belong to the appliance, such as the `X-Morpheus-Lease` header. Keep it passing.
-
-The tests that need a live appliance are described in [Testing](README.md#testing) in the README. Run them when you change how the CLI talks to the API.
-
-## Writing changes
-
-- Keep each pull request to one change. Separate refactoring from behaviour changes.
-- Follow the style of the code around your change.
-- Customer-facing text says **MTN Cloud**, and commands are shown as `mtncloud`. Values that the appliance or its API defines keep their names, for example `X-Morpheus-Lease` and `MORPHEUS_LEASE_TOKEN`.
-- Update the README when you change how the CLI is installed, configured or used.
-
-## Commit messages
-
-- Write a short summary line in the imperative mood, for example "Fix clusters get usage on Ruby 3.4".
-- If the reason for the change isn't obvious, explain it in the body.
-
-## Releases
-
-Maintainers publish releases. See [Releasing](README.md#releasing) in the README. The version bump goes through a pull request like any other change, and the version tag is pushed after that pull request is merged.
-
-## License
-
-By contributing, you agree that your contributions are licensed under the project's [MIT license](LICENSE.txt).
+# Contributing to the MTN Cloud CLI
+
+Thank you for helping improve the MTN Cloud CLI. This guide explains how changes get into the project.
+
+## How changes reach main
+
+`main` is protected. Nobody pushes to it directly, including maintainers. Every change goes through a pull request:
+
+1. Update your local `main`:
+
+   ```shell
+   git checkout main
+   git pull
+   ```
+
+2. Create a branch for your change:
+
+   ```shell
+   git checkout -b fix/clusters-get-help
+   ```
+
+   Name the branch after the change, with a prefix: `feature/`, `fix/`, `docs/` or `chore/`.
+
+3. Make your change, run the offline tests (see [Testing](#testing)), and commit.
+4. Push the branch and open a pull request against `main`:
+
+   ```shell
+   git push -u origin fix/clusters-get-help
+   gh pr create --base main
+   ```
+
+5. Wait for the **CI passed** check. It runs the offline tests on Ruby 3.3, 3.4 and 4.0 and builds the gem.
+6. When CI passes, merge the pull request. A pull request cannot be merged while CI is failing or still running.
+
+If CI fails, push more commits to the same branch. CI runs again on every push.
+
+## Setting up
+
+Requirements:
+
+- Ruby 3.3 or newer
+- Bundler 2
+- Git
+
+```shell
+git clone https://github.com/Jose-henry/mtncloud-cli
+cd mtncloud-cli
+bundle install
+```
+
+Run the CLI from your working copy:
+
+```shell
+bundle exec ruby bin/mtncloud --help
+```
+
+See [Development](README.md#development) in the README for the code layout.
+
+## Testing
+
+Run the offline tests before you open a pull request. They don't need an MTN Cloud appliance, and they are the same tests CI runs:
+
+```shell
+bundle exec rake test:offline
+```
+
+Add or update tests for the behaviour you change. A test that doesn't need an appliance must not `require 'mtncloud_test'`, so that `test:offline` and CI run it.
+
+`test/branding_test.rb` fails if any command's help mentions Morpheus, except for values that belong to the appliance, such as the `X-Morpheus-Lease` header. Keep it passing.
+
+The tests that need a live appliance are described in [Testing](README.md#testing) in the README. Run them when you change how the CLI talks to the API.
+
+## Writing changes
+
+- Keep each pull request to one change. Separate refactoring from behaviour changes.
+- Follow the style of the code around your change.
+- Customer-facing text says **MTN Cloud**, and commands are shown as `mtncloud`. Values that the appliance or its API defines keep their names, for example `X-Morpheus-Lease` and `MORPHEUS_LEASE_TOKEN`.
+- Update the README when you change how the CLI is installed, configured or used.
+
+## Commit messages
+
+- Write a short summary line in the imperative mood, for example "Fix clusters get usage on Ruby 3.4".
+- If the reason for the change isn't obvious, explain it in the body.
+
+## Releases
+
+Maintainers publish releases. See [Releasing](README.md#releasing) in the README. The version bump goes through a pull request like any other change, and the version tag is pushed after that pull request is merged.
+
+## License
+
+By contributing, you agree that your contributions are licensed under the project's [MIT license](LICENSE.txt).

data/Dockerfile

@@ -1,19 +1,19 @@
-# Stage 1: build the mtncloud-cli gem from this repository.
-# The gemspec lists its files with `git ls-files`, so this stage needs the .git
-# directory in the build context. Only files tracked by git go into the gem.
-FROM ruby:3.3 AS build
-WORKDIR /src
-COPY . .
-RUN gem build mtncloud-cli.gemspec -o /mtncloud-cli.gem
-
-# Stage 2: install the gem into a clean image.
-# Only the built .gem is copied from stage 1, so nothing else from the build
-# context (local files such as test_config.yaml, or the .git directory)
-# ends up in the final image.
-FROM ruby:3.3
-COPY --from=build /mtncloud-cli.gem /tmp/mtncloud-cli.gem
-RUN gem install /tmp/mtncloud-cli.gem --no-document \
- && rm /tmp/mtncloud-cli.gem
-
-WORKDIR /root
-ENTRYPOINT ["mtncloud"]
+# Stage 1: build the mtncloud-cli gem from this repository.
+# The gemspec lists its files with `git ls-files`, so this stage needs the .git
+# directory in the build context. Only files tracked by git go into the gem.
+FROM ruby:3.3 AS build
+WORKDIR /src
+COPY . .
+RUN gem build mtncloud-cli.gemspec -o /mtncloud-cli.gem
+
+# Stage 2: install the gem into a clean image.
+# Only the built .gem is copied from stage 1, so nothing else from the build
+# context (local files such as test_config.yaml, or the .git directory)
+# ends up in the final image.
+FROM ruby:3.3
+COPY --from=build /mtncloud-cli.gem /tmp/mtncloud-cli.gem
+RUN gem install /tmp/mtncloud-cli.gem --no-document \
+ && rm /tmp/mtncloud-cli.gem
+
+WORKDIR /root
+ENTRYPOINT ["mtncloud"]

data/Gemfile

@@ -1,4 +1,4 @@
-source 'https://rubygems.org'
-
-# Specify your gem's dependencies in mtncloud-cli.gemspec
-gemspec
+source 'https://rubygems.org'
+
+# Specify your gem's dependencies in mtncloud-cli.gemspec
+gemspec