Hello there, first pf all thank you for making such a great tool. I was wondering how do I apply my own cloud_init script to the maasta wrapper so that when MaaS deploys the commissioned node it will apply the cloud_init script?

I installed python 3.8 on Ubuntu 22.04LTS so that I can try this wrapper but I am currently receiving these errors on my node.

(venv) ryzengrind@shogun:~/Documents/Workspaces/ClusterLab/ansible-playbooks/maasta/examples/single$ ./deploy 

Initializing the backend...

Initializing provider plugins...
- Reusing previous version of suchpuppet/maas from the dependency lock file
- Using previously-installed suchpuppet/maas v3.1.3

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.
maas_instance.docker: Refreshing state... [id=gafn6t]

Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
-/+ destroy and then create replacement

Terraform will perform the following actions:

  # maas_instance.docker is tainted, so must be replaced
-/+ resource "maas_instance" "docker" {
      ~ id                   = "gafn6t" -> (known after apply)
        # (5 unchanged attributes hidden)
    }

Plan: 1 to add, 0 to change, 1 to destroy.

─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────

Note: You didn't use the -out option to save this plan, so Terraform can't guarantee to take exactly these actions if you run "terraform apply" now.
maas_instance.docker: Refreshing state... [id=gafn6t]

Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
-/+ destroy and then create replacement

Terraform will perform the following actions:

  # maas_instance.docker is tainted, so must be replaced
-/+ resource "maas_instance" "docker" {
      ~ id                   = "gafn6t" -> (known after apply)
        # (5 unchanged attributes hidden)
    }

Plan: 1 to add, 0 to change, 1 to destroy.
maas_instance.docker: Destroying... [id=gafn6t]
maas_instance.docker: Still destroying... [id=gafn6t, 10s elapsed]
maas_instance.docker: Destruction complete after 12s
maas_instance.docker: Creating...
maas_instance.docker: Still creating... [10s elapsed]
maas_instance.docker: Still creating... [20s elapsed]
maas_instance.docker: Still creating... [30s elapsed]
maas_instance.docker: Still creating... [40s elapsed]
maas_instance.docker: Still creating... [50s elapsed]
maas_instance.docker: Still creating... [1m0s elapsed]
maas_instance.docker: Still creating... [1m10s elapsed]
maas_instance.docker: Still creating... [1m20s elapsed]
maas_instance.docker: Still creating... [1m30s elapsed]
maas_instance.docker: Still creating... [1m40s elapsed]
maas_instance.docker: Still creating... [1m50s elapsed]
maas_instance.docker: Still creating... [2m0s elapsed]
maas_instance.docker: Still creating... [2m10s elapsed]
maas_instance.docker: Still creating... [2m20s elapsed]
maas_instance.docker: Still creating... [2m30s elapsed]
maas_instance.docker: Still creating... [2m40s elapsed]
maas_instance.docker: Still creating... [2m50s elapsed]
maas_instance.docker: Still creating... [3m0s elapsed]
maas_instance.docker: Still creating... [3m10s elapsed]
maas_instance.docker: Still creating... [3m20s elapsed]
maas_instance.docker: Still creating... [3m30s elapsed]
maas_instance.docker: Still creating... [3m40s elapsed]
maas_instance.docker: Still creating... [3m50s elapsed]
maas_instance.docker: Still creating... [4m0s elapsed]
╷
│ Error: [ERROR] [resourceMAASInstanceCreate] Error waiting for instance (gafn6t) to become deployed: %!s(<nil>)
│ 
│   with maas_instance.docker,
│   on main.tf line 25, in resource "maas_instance" "docker":
│   25: resource "maas_instance" "docker" {
│ 
╵
INFO: Ansible inventory created successfully.

PLAY [docker] ********************************************************************************************************************************************************************

TASK [Gathering Facts] ***********************************************************************************************************************************************************
fatal: [moved-gull.maas]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: ssh: connect to host 192.168.20.235 port 22: Connection timed out", "unreachable": true}

PLAY RECAP ***********************************************************************************************************************************************************************
moved-gull.maas            : ok=0    changed=0    unreachable=1    failed=0    skipped=0    rescued=0    ignored=0 

Kindly advise.

Hi Saied,

First and foremost, thank you for publishing this code. At our company we are looking for better ways to automate infra provisioning, and we bumped into your article about MAASTA and from there into this repo.

I see you are not publishing this package in PyPI. Any specific reason for that? Any chance we are going to see that happening? Thanks!

Cheers

change maasta.py and utils.py in order to add ini inventory output.

it's checked several times with single and multi terraform state and it's been ok.