Requesting Automatic Aliases for ansible-kz6fittycent

store
1

Greetings,

I am requesting that these aliases for ansible-kz6fittycent be automatically setup.

apps:
  ansible-kz6fittycent:
    command: bin/ansible
  ansible-kz6fittycent-playbook:
    command: bin/ansible-playbook
  ansible-kz6fittycent-galaxy:
    command: bin/ansible-galaxy
  ansible-kz6fittycent-config:
    command: bin/ansible-config
  ansible-kz6fittycent-connection:
    command: bin/ansible-connection
  ansible-kz6fittycent-console:
    command: bin/ansible-console
  ansible-kz6fittycent-doc:
    command: bin/ansible-doc
  ansible-kz6fittycent-inventory:
    command: bin/ansible-inventory
  ansible-kz6fittycent-pull:
    command: bin/ansible-pull
  ansible-kz6fittycent-vault:
    command: bin/ansible-vault

These are required for use with the snap so as to expose the actual commands for users (e.g. ansible-playbook, etc).

Additionally, and maybe this needs to be a separate post, I’d like to request that the following plugs be approved for the snap:

      - system-files
      - personal-files

These are required to allow the snap to leverage default locations, make changes to it’s files (configs and hosts files), and reference .files within /home/$USER, /home/$USER/snap/ansible-kz6fittycent/current (or common), etc/ansible (i.e. etc/ansible/hosts and etc/ansible/ansible.cfg).

@bashfulrobot if you can remember any other files or reasons, please let me know.

I think we’ll have a fairly good snap after these changes are made. Here’s the current yaml:

name: ansible-kz6fittycent 
adopt-info: ansible-kz6fittycent
summary: Ansible is a radically simple IT automation system.
description: |
    Ansible is a radically simple IT automation system. 
    It handles configuration-management, application deployment, cloud provisioning, 
    ad-hoc task-execution, and multinode orchestration -- including trivializing things 
    like zero-downtime rolling updates with load balancers.
    
grade: stable 
confinement: devmode 
base: core18

architectures:
- build-on: amd64

apps:
  ansible-kz6fittycent:
    command: bin/ansible
  ansible-kz6fittycent-playbook:
    command: bin/ansible-playbook
  ansible-kz6fittycent-galaxy:
    command: bin/ansible-galaxy
  ansible-kz6fittycent-config:
    command: bin/ansible-config
  ansible-kz6fittycent-connection:
    command: bin/ansible-connection
  ansible-kz6fittycent-console:
    command: bin/ansible-console
  ansible-kz6fittycent-doc:
    command: bin/ansible-doc
  ansible-kz6fittycent-inventory:
    command: bin/ansible-inventory
  ansible-kz6fittycent-pull:
    command: bin/ansible-pull
  ansible-kz6fittycent-vault:
    command: bin/ansible-vault  
    environment: 
      LC_ALL: C.UTF-8
    plugs:
      - home
      - network
      - mount-observe
      - system-files
      - personal-files
     
parts: 
  ansible-kz6fittycent:
    source: https://github.com/ansible/ansible
    source-type: git
    plugin: python
    python-version: python3
    requirements: [requirements.txt]
    
    override-pull: |
      snapcraftctl pull
      snapcraftctl set-version "$(git describe --tags | sed 's/^v//' | cut -d "-" -f1)"
      
    build-packages:
      - python3
      
    stage-packages:
      - python3
      - python3-jinja2
      - python3-yaml
      - python3-paramiko
      - python3-setuptools
      - python3-cryptography

TIA!

2

We will have to modify the YAML yet. The format for the personal-files, etc., here is incorrect. We will need to define the specific paths/files, etc., in the YAML (unless this has changed since I last read the docs). We have to be very specific to what personal-file, etc., can access. It is more than just requesting access here. :+1:I suspect we may have to do that before the Canonical team addressing and approving the access. (speculated)

1 Like