Invoker CLI example

# Byte-compiled / optimized / DLL files

__pycache__/

*.py[cod]

*$py.class

# C extensions

*.so

# Distribution / packaging

.Python

build/

develop-eggs/

dist/

downloads/

eggs/

.eggs/

lib/

lib64/

parts/

sdist/

var/

wheels/

share/python-wheels/

*.egg-info/

.installed.cfg

*.egg

MANIFEST

# PyInstaller

#  Usually these files are written by a python script from a template

#  before PyInstaller builds the exe, so as to inject date/other infos into it.

*.manifest

*.spec

# Installer logs

pip-log.txt

pip-delete-this-directory.txt

# Unit test / coverage reports

htmlcov/

.tox/

.nox/

.coverage

.coverage.*

.cache

nosetests.xml

coverage.xml

*.cover

*.py,cover

.hypothesis/

.pytest_cache/

cover/

# Translations

*.mo

*.pot

# Django stuff:

*.log

local_settings.py

db.sqlite3

db.sqlite3-journal

# Flask stuff:

instance/

.webassets-cache

# Scrapy stuff:

.scrapy

# Sphinx documentation

docs/_build/

# PyBuilder

.pybuilder/

target/

# Jupyter Notebook

.ipynb_checkpoints

# IPython

profile_default/

ipython_config.py

# pyenv

#   For a library or package, you might want to ignore these files since the code is

#   intended to run in multiple environments; otherwise, check them in:

# .python-version

# pipenv

#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.

#   However, in case of collaboration, if having platform-specific dependencies or dependencies

#   having no cross-platform support, pipenv may install dependencies that don't work, or not

#   install all needed dependencies.

#Pipfile.lock

# poetry

#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.

#   This is especially recommended for binary packages to ensure reproducibility, and is more

#   commonly ignored for libraries.

#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control

#poetry.lock

# pdm

#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.

#pdm.lock

#   pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it

#   in version control.

#   https://pdm.fming.dev/#use-with-ide

.pdm.toml

# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm

__pypackages__/

# Celery stuff

celerybeat-schedule

celerybeat.pid

# SageMath parsed files

*.sage.py

# Environments

.env

.venv

env/

venv/

ENV/

env.bak/

venv.bak/

# Spyder project settings

.spyderproject

.spyproject

# Rope project settings

.ropeproject

# mkdocs documentation

/site

# mypy

.mypy_cache/

.dmypy.json

dmypy.json

# Pyre type checker

.pyre/

# pytype static type analyzer

.pytype/

# Cython debug symbols

cython_debug/

# PyCharm

#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can

#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore

#  and can be added to the global gitignore or merged into this file.  For a more nuclear

#  option (not recommended) you can uncomment the following to ignore the entire idea folder.

#.idea/

[[source]]

url = "https://pypi.org/simple"

verify_ssl = true

name = "pypi"

[packages]

pymongo = "==3.12.0"

inject = "==4.3.1"

[dev-packages]

[requires]

python_version = "3.8"

# invoker-cli

# CAPIF_Invoker_GUI

This is the implementation of a CAPIF Invoker 

* This repo is intended to be used as a test method for CAPIF services and services published on CAPIF.

## Getting started

## Prerequisites

Before executing the following code it is necessary to have raised an instance of [CAPIF](https://github.com/Telefonica/CAPIF_Future_Network_Lab.git).

To run Capif Invoker you must ensure to have docker and a docker compose version 2.10 or higher.

To make it easy for you to get started with GitLab, here's a list of recommended next steps.

## Set Up

This repo is designed to be executed from docker, to create the images and raise the instance it is only necessary to execute the following command:

```

./run.sh

Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!

```

## Add your files

- Before executing the run.sh command, note that it supports one parameter, this parameter is the CAPIF hostname, by default this field is 'capifcore'. Modify it if necessary or add the hostname when executing the run.sh command

- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files

- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:

    ```

    ./run.sh <other_hostname>

    ```

cd existing_repo

git remote add origin https://labs.etsi.org/rep/ocf/example-clients/invoker-cli.git

git branch -M main

git push -uf origin main

- It is important to have the following environment variables in the docker-compose file:

    ```

      - CAPIF_HOSTNAME=${CAPIF_HOSTNAME}

      - CAPIF_PORT=8080

      - REGISTER_HOSTNAME=register

      - REGISTER_PORT=8084

      - CAPIF_PORT_HTTPS=443

      - CAPIF_CALLBACK_URL=host.docker.internal

      - CAPIF_CALLBACK_PORT=8086

## Integrate with your tools

    ```

    These environment variables refer to the registration services. By default, these are the ports and names that the CAPIF script uses when launching the different services. If during the deployment of CAPIF you modify these parameters, you must modify them so that they correspond to the new ones.

- [ ] [Set up project integrations](https://labs.etsi.org/rep/ocf/example-clients/invoker-cli/-/settings/integrations)

Now it is only necessary to enter inside the container by executing this command

## Collaborate with your team

- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)

- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)

- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)

- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)

- [ ] [Automatically merge when pipeline succeeds](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)

## Test and Deploy

```

./terminal_to_py_aef.sh

Use the built-in continuous integration in GitLab.

```

- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)

- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing(SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)

- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)

- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)

- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)

Once inside the container you can run the provider command GUI by running

***

```

./python main.py

# Editing this README

```

When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thank you to [makeareadme.com](https://www.makeareadme.com/) for this template.

## Interacting with the GUI

The provider is prepared to make the necessary previous provisions automatically, but if the user is already register, you can remove the user using the command:

```

remove_user

```

## Suggestions for a good README

Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.

and register a new user with

```

register_user

```

## Name

Choose a self-explaining name for your project.

The different .json files that must be saved in CAPIF are also added. To make the necessary provisions you just have to execute the following commands within the GUI

## Description

Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.

```

register_invoker

## Badges

On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.

```

## Visuals

Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.

```

discover_service

## Installation

Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.

```

## Usage

Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.

```

register_security_context <api_name>

## Support

Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.

```

## Roadmap

If you have ideas for releases in the future, it is a good idea to list them in the README.

```

get_security_auth <api_name>

```

## Contributing

State if you are open to contributions and what your requirements are for accepting them.

### What are we doing?

- The previous commands are to register an invoker within CAPIF, discover the services that have been published and if there are any published services, create a security context to use those services.

For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.

*If the first command returns a 401, it means that the token to interact the first time with CAPIF has expired, run the following command

You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.

```

get_auth

```

## Authors and acknowledgment

Show your appreciation to those who have contributed to the project.

## Call Service

```

call_service <api_name>

```

## License

For open source projects, say how it is licensed.

If the previous process has been executed correctly, the call_service command will call the first endpoint of the service that has been discovered.

## Project status

If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.

If you want to call another endpoint or modify the parameters that are sent to the service, you must modify the code directly

#!/bin/bash

docker compose down --rmi all --remove-orphans || true

# sudo rm ./invoker_gui/capif_onboarding/*

# sudo rm ./invoker_gui/demo_values.json && sudo rm ./invoker_gui/ca.crt && sudo rm ./invoker_gui/cert_req.csr && sudo rm ./invoker_gui/dummy.crt && sudo rm ./invoker_gui/private.key && sudo rm ./invoker_gui/ca_service.crt

# sudo rm ./invoker_gui/demo_values.json

# sudo rm ./invoker_gui/ca.crt

# sudo rm ./invoker_gui/cert_req.csr

# sudo rm ./invoker_gui/dummy.crt

# sudo rm ./invoker_gui/private.key

 No newline at end of file

version: '3'

services:

  invoker_gui:

    image: invoker_gui

    hostname: dummy

    container_name: invoker_gui

    build:

      context: ./invoker_gui

    volumes:

      - ./invoker_gui:/usr/src/app

    environment:

      - CAPIF_HOSTNAME=${CAPIF_HOSTNAME}

      - CAPIF_PORT=8080

      - REGISTER_HOSTNAME=register

      - REGISTER_PORT=8084

      - CAPIF_PORT_HTTPS=443

      - CAPIF_CALLBACK_URL=host.docker.internal

      - CAPIF_CALLBACK_PORT=8086

    extra_hosts:

      - host.docker.internal:host-gateway

      - capifcore:host-gateway

      - one_provider_gui:host-gateway

      - register:host-gateway

networks:

  default:

    external:

      name: capif-network

 No newline at end of file