Go to file
Marco Chiappero 03d7a39ead Allow control over IRONIC_EXTERNAL_HTTP_URL via values.yaml
The purpose of this commit is to:
- avoid providing IRONIC_EXTERNAL_HTTP_URL by default, as the Ironic
  startup scripts will be able to derive the value from other variables
- define a new global value under the top values.yaml to generate
  IRONIC_EXTERNAL_HTTP_URL when actually needed
- make sure that the input, which can either be a hostname or an IP
  address, is correctly formatted in case of an IPv6.

This change also allows subsequent cleanups of the whole Configmap
template for Ironic.

Signed-off-by: Marco Chiappero <marco.chiappero@suse.com>
2025-08-06 17:30:26 +00:00
2025-02-20 11:15:35 +01:00
2025-04-30 16:42:54 +02:00
2024-10-22 16:43:48 +02:00
2025-05-07 20:03:45 +03:00
2025-04-30 16:42:54 +02:00
2024-10-22 12:26:29 +02:00
2024-10-22 16:14:46 +02:00
2025-05-15 14:06:32 +02:00
2025-06-10 11:12:08 +02:00
2024-10-22 16:14:46 +02:00
2024-10-22 16:43:48 +02:00
2025-02-24 11:21:52 +01:00
2025-06-09 17:25:39 +03:00
2025-04-30 16:42:54 +02:00
2025-04-30 16:42:54 +02:00
2024-10-17 14:01:57 +02:00
2025-02-24 11:21:52 +01:00
2025-07-24 13:44:12 +02:00
2025-06-09 11:22:25 +03:00
2024-10-22 16:43:48 +02:00
2025-02-24 15:44:23 +01:00

Factory

Contains the definition of the packages built on OBS for the SUSE Edge Solution (WIP)

This repository is linked to an OBS project: https://build.opensuse.org/project/show/isv:SUSE:Edge:Factory Every directory in this repository represents a package in that OBS project, those should be synced automatically from this repository.

Testing a fork or a development branch

You can create a project in your home space in OBS, use the same prjconf as the one of "isv:SUSE:Edge:Factory", and copy the repositories part of the metadata (adjust self references). Then add a scmsync stanza to your metadata like this (adjust repository path and branch):

<scmsync>https://src.opensuse.org/suse-edge/Factory#main</scmsync>

This is done automatically for any PR filed against this repository.

Cutting a release version branch

  1. Do the appropriate git branch command
  2. Change the project path in .obs/common.py file (e.g. from isv:SUSE:Edge:Factory to isv:SUSE:Edge:3.2)
  3. Change the branch reference in .obs/common.py file (e.g. from main to 3.2)
  4. Commit those changes to the new branch and push the new branch
  5. Go take a few cups of coffee/tea/mate/... while waiting for OBS to build everything
  6. Once built do an osc release of the project for it to be copied over in the ToTest section
  7. Hand over to QA to test whatever is in ToTest. (You can continue to work on the base branch if needed meanwhile)
Description
No description provided
Readme 335 MiB
Languages
Shell 33.4%
Dockerfile 23.1%
Smarty 21.9%
Jinja 10.7%
Python 9.6%
Other 1.3%