David Cassany Viladomat

rancher/elemental-cli#336 could help on making this procedure lighter, since it allows to add a yaml into an existing iso on the fly.

I was wondering if there was a way to add environment variables to the build env from project configuration or something similar, in that case we could define some build...

My idea is to expand the [obs-service-replave_using_env](https://build.opensuse.org/package/show/Virtualization/obs-service-replace_using_env) to support expanding from rpm macros too, so we could eventually have something in services like: ```xml values.yaml image_repo ``` and project configuration...

Ok, I managed to solve this, there was no need to modify any obs-service for that. `replace_using_env` is already capable of doing what I had in mind, probably not in...

I consider this done. The macro setup has been included in the Elemental OBS builds confluence page with a link to this issue for full reference if needed.

A good follow up for this issue could be a two step action point: 1. Further experiment with sharing elemental-system-agent and rancher-system-agent configuration options. Is there a chance that one...

> elemental-operator should be bumped to 1.0.0 for release, no ? Agree, IMHO this applies to rancher/elemental-operator and rancher/elemental repositories. We are also missing elemental-toolkit in the list. In relation...

> would add that the elemental-operator and elemental versions should have the same major version at each stable release. I like the idea > IMO, what would be helpful is...

Ok after the discussion we had last week I think a good criteria to start with could be (applicable for `rancher/elemental` and `rancher/elemental-operator` repositories): * Use semantic versioning * Align...

Yes agree, the milestone was essentially added to avoid touching it before the 2.6.9 release. In fact, my only concern is about running CI refactors while go/no-go tests for a...